First off, I must apologize and say. Yes, I know there are all ready two other posts just this week on 'Did I kill my phone, Is it dead etc.'
So, to make a long story short.
After much research, I started at the ppcgeeks.com forums, then ppckitchen.org and finally made my way over here. I decided it was time to start working on updating my phone.
First off; I downloaded the wrong link and flashed the Olipro 1.20 boot loader on the phone, instead of the 2.4x version that is being used now. No big deal, I then got into boot loader mode and went to flash a stock rom to fix the issue. The rom had an error in the middle and reset. Then my phone reset. It went back into boot loader mode and then after using titan_exitbl.exe it booted to the standard HTC screen. After a moment now at this screen it will display the HTC logo and No Radio in red. After much reading I found that I could simply flash my 512mb MicroSD card, and did. And I placed the TITAIMG.nbh file on the root. (that is the only thing on the card) to upgrade the radio. But now when I try to restart into boot loader mode (power, camera, reset) it only resets and does not go into boot loader mode. I can perform a hard reset and go through the prompts there, but after it completes it simply brings me back to the HTC logo, and No Radio.
There is no connection via Active sync, nor through the USB, so I can not use mtty to edit anything on the boot loader end.
I have done quite a bit of reading and I figure this probably has been asked before, but is there a way to get my phone to get back to boot loader mode so I can load at least a stock rom onto it?
I don't know a whole lot about troubleshooting phones considering I have only had mine for a few weeks. However I have worked for Geek Squad for 3 years so troubleshooting is kind of in my nature.
Have you tried putting it in bootloader mode without your SD card in there? If there is something wrong with the .nbh you have on it and it keeps trying to load it when in bootloader, that could be your problem. I would remove the SD card and try bootloader, at which point you should be able to flash via usb.
Worth a shot at least.
Flash a new bootloader like 2.47 via sd. Then start loading radio and rom from there.
flipzmode said:
I don't know a whole lot about troubleshooting phones considering I have only had mine for a few weeks. However I have worked for Geek Squad for 3 years so troubleshooting is kind of in my nature.
Have you tried putting it in bootloader mode without your SD card in there? If there is something wrong with the .nbh you have on it and it keeps trying to load it when in bootloader, that could be your problem. I would remove the SD card and try bootloader, at which point you should be able to flash via usb.
Worth a shot at least.
Click to expand...
Click to collapse
Yes I have tried with and without the SD card in the phone. I have also tried with and without the phone connected to a USB cable.
I cannot flash anything to the phone because i cannot establish a connection to the phone via ActiveSync.
Did you try what I suggested? Can you get to just the bootloader screen? Hold power and camera then push reset at same time for bootloader.
drewcam888 said:
Did you try what I suggested? Can you get to just the bootloader screen? Hold power and camera then push reset at same time for bootloader.
Click to expand...
Click to collapse
That is the problem. I have tried that. power, camera, and reset. And any combination of other button, SD card in/out, USB in/out, and anything else i can think of...
The bootloader screen will Not come up.
What can the phone do? Kinda sounds like it might be bricked.
drewcam888 said:
What can the phone do? Kinda sounds like it might be bricked.
Click to expand...
Click to collapse
I know, I hope it is not. This is my phone for work, and my boss is pretty pissed that I might have just bricked a phone he just paid for.
It will turn on from the power button, i can reset it normally with the reset push switch. (it then returns to the HTC logo, and No Radio in red). I can also do the 'bootloader' reset, but this does not bring it to the bootloader, it simply acts as a standard reset. I can also do a 'hard' reset, both of the select keys, and the reset switch. It will then boot into the 'do you want to hard reset your phone' prompt, and it will let me go through those steps that would normally hard reset the phone. After the reboot when that is finished it again goes to the HTC logo and No Radio. So, with that, I sure hope that some part of the bootloader is in tack.
Thank you for your help so far.
Are you sure you are holding both the camera and power button at the same time and then pushing reset button while still holding?
psycopyro182 said:
Yes I have tried with and without the SD card in the phone. I have also tried with and without the phone connected to a USB cable.
I cannot flash anything to the phone because i cannot establish a connection to the phone via ActiveSync.
Click to expand...
Click to collapse
From what it sounds like, you're trying to run the bootloader with and without the SD card in. The problem is, it sounds like you don't have a working file actually on the SD card. It also seems that since you cannot make an ActiveSync connection, you aren't able to transfer files to and from the card.
Do you have a microSD card reader?
Check this out: http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
Particularly Section II.2.A. That may fix your problem.
Hope this helps!
Oh and if it doesn't something you said about your boss having 'just' paid for your phone. If its new enough... w-a-r-r-a-n-t-y!
He can't follow those suggestions on the wiki exactly because he cant get a usb connection. But I agree he needs to load the 2.47 on his card using a adapter then try bootloader again.
Did you try EnterBL.exe?
DustinEarnhardt said:
From what it sounds like, you're trying to run the bootloader with and without the SD card in.
Oh and if it doesn't something you said about your boss having 'just' paid for your phone. If its new enough... w-a-r-r-a-n-t-y!
Click to expand...
Click to collapse
I cannot even get the bootloader to come up. Yes I know that I am pressing both buttons and hitting Reset.
And as for Warranty, Will they warranty a phone that has the updated bootloader on it? I know there is a utility to Re-flash your phone to stock, but well, i cant even get mine to do anything at this point. I dont want sprint to tell me that they will not warranty it because I have 'tampered' with it, or 'voided the warranty'.
bitserve said:
Did you try EnterBL.exe?
Click to expand...
Click to collapse
I did not know there was such a tool.
A direct link would be great. That sound like what i need to get out of this mess.
Heres the deal, if you can't get it to go to bootloader, the carrier probably can't either....
I think the enter_BL only works if active sync works, but I could be wrong.
I've never seen a phone yet, or heard of one for that matter that boots as far as yours does yet doesn't go to a bootloader screen when reset properly. It does sound pretty messed up.
More than likely, if you go into the store and say "Hey this is messed up because I tried to update the bootloader on it" you'll get some pretty quizzical looks. They'll more than likely take your phone in the back, not do a thing with it, and then issue you a replacement (if they have one in stock) or mail you one as soon as possible.
It does sound like you may have created a brick, but luckily this one is replaceable. Consider it a "lesson learned" for the next one.
(My apologies if I offend any VZW store employees. I sure there is a rare breed of highly competent and capable technicians out there, but I have yet to meet one in my area.)
Boots Up?
Does your phone boot all the way up where you can explore your SD card on your phone? If you can PM me and I may have a solution for you if your bootloader allows you to flash by SD card.
Brick = New Phone
DustinEarnhardt said:
More than likely, if you go into the store and say "Hey this is messed up because I tried to update the bootloader on it" you'll get some pretty quizzical looks. They'll more than likely take your phone in the back, not do a thing with it, and then issue you a replacement (if they have one in stock) or mail you one as soon as possible.
It does sound like you may have created a brick, but luckily this one is replaceable. Consider it a "lesson learned" for the next one.
one in my area.)
Click to expand...
Click to collapse
So, I walked into the store, and simply said. "I have insurance, what do I need to tell you in order to get the phone fixed." "what do you mean?" "Well i have my phone here, it is totally bricked, the bootloader is toast, and there is no radio or rom, and it will not connect to activesync. So, if i need to come back and tell you my phone is stolen i can."
"Um ok? bricked? bootloader?... Here, let me see it"
(Lucky for me my company had just purchased about a dozen phones from this store, and the techs were happy to work with me)
The tech took the phone in back, and he and another tech looked at it, tried to hard reset, tried the enter bootloader key press. tried to plug it in. Then they both scratched their heads with a completly dumbfounded look on their faces. One of them walked to the closet, grabbed a new phone and brought it to me and said. "Congrats, this is the most screwed up phone I have seen come in here. Here is a brand new one, We will have to send this one back to corporate."
So, now shiny new phone in hand.
I can say simply "Lesson Learned"
Thanks for all of your help guys.
Related
My phone was working fine for sometime with DCD 3.1.2, SPL 2.40 and radio 3.39.10. Last week it starting randomly resetting when I would slide open the keyboard. Not always, but quite annoying. The past few days it started getting stuck in the bootloader on initial start. I would reset it, remove the battery, etc. Still it would go to the bootloader. I even tried the exitbl utility and although it sends the data and executes the reset, it still goes back to the bootloader. Screen says:
TITA100 MFG
SPL-2.40.Olipro
CPLD-9
I figured it was a bug with the rom or whatnot, so I (microsd) reflashed it with the latest official Sprint rom. It still goes into the bootloader. If I hit the reset button enough times, it will occasionally boot up. No idea what's goin on here. Don't understand how it could be random either.
Any ideas?
do you have the wire that you plug in for headphones?
it's the headphone/ USB plug?
if so plug it in and just push the soft reset button
it should work
Ok, that worked like a charm, thanks!
Question is it still enters the bootloader when I reset or turn off/on the phone without the adapter. Should I reflash the bootloader?
i have found no info pointing towards what is doing it. i've re-flashed with no luck
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
I've got the exact same situation as you guys... Just wanted to chime in on it.
cpujunky said:
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
i think i read on another forum that you can not flash off the memory card for a bootloader.. but i do not know
Try a hard-reset and then flash to another pre-built or Kitchen built ROM that uses the 2.40 bootloader.
You must boot into the WinMo OS and get connected with Activesynch to program a bootloader. At least none of us have yet managed to figure another way to do it.
Is there a way to flash the bootloader off just the memory card? Can I copy the Hard_MFG_SPL_2.40_RUU_signed.nbh file to a card and rename it?
Figure it's worth a try.
Click to expand...
Click to collapse
Do NOT, I repeat do NOT attempt to update the SPL with the memory card. The unlockers are developed to first load a temporary bootloader, then flash with an RUU once using the temporary. You will mess up your phone.
Thanks... I was having the same problem that the OP was having until I found this thread. It seems like headphone adapters other than the Sprint one works. Also, if you're stuck in the bootloader, there is no reason to flash any roms because it will have no effect at all.
Also, as an alternative, you can take out the battery for a couple hours.
By the way, I'm running dcd 3.1.2 and radio 3.37
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Thinking,,,,,
I stopped where you see in my signature as everything works for me, but I wonder if maybe you flash back to stock, relock, put it back exactly as you started if that would straighten it out. If it still fails stock then some nice new defect has been found. If it works then go forward but only as far as I did ans see if it is stable as with mine,,,,,maybe somthing in the new ROMs???????
cpujunky said:
So we know that flashing a new ROM doesn't work, and flashing different radios doesn't work. We also know the headphone adapter will get you to boot up normally, so no stuck buttons or anything. This has to be a bootloader bug or phone defect or bent usb pins or something. Has anyone tried relocking the phone? I can't express how annoying it is to carry around a headphone adapter in case you need to reboot.
Click to expand...
Click to collapse
i have relocked also. i've think i've done everything except rip the phone apart and look at the usb pins
This is not a rom issue, it's a bootloader issue. I've flashed, tested, and used all released roms and non-released (internally tested) roms numerous times on several different titans and have never seen this issue. I'm not doubting the existence of the issue, but the rom will have nothing to do with the device being stuck in the bootloader.
My guess is that something went wrong while unlocking or it's a hardware defect on a certain batch of these phones.
there was some talk over at ppcgeeks about there being something about relocking and flashing and something... however. my phone worked great and then one day it just started and nothing changed on the phone for like 3-4 weeks and then it started going to bootloader
This weekend I replaced the stock bootloader on my VZW XV6800 with SPL-2.40.Olipro; upgraded radio to 3.39.10; installed dcd's Titan 3.1.2. All went well, phone was doing fine for a couple days.
Today the battery died, nothing unusual. I plugged in AC power and turned on the phone and the bootloader displayed. Did a soft reset 2 or 3 times, no change. Disconnected AC, popped out the battery, let it sit while I search and found this thread.
I used a can o' air to blast out the USB/power port on the phone. Put in the battery, powered the phone, and the OS loaded just fine. Soft reset the phone and again could only get to the bootloader. Poppped out the battery again, found my USB/headphone adapter, connected it, returned the battery and powered the phone, and the OS loaded just fine.
This is a long way of saying I'm experiencing the same that's been reported in this thread. Is there a fix for this issue? It seems like an issue with the device to me. Was there any confirmation that there was a "bad batch" of phones and is a hardware issue with the XV6800?
I am also experiencing this same problem.
I flashed to 3.1.2, then to 3.2.0 today...nothing changed. It still loads the bootloader when i do any kind of a reset without the usb or the headphones plugged in.
The only odd thing that i can comment on during my experience is that my USB cable failed on me and I had to replace it. Seems odd, but perhaps that can shed some light on the problem.
Did anyone find a solution to this problem? Is it a hardware issue?
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
Can you install the Rom "The base .5". I assume so if you can get to cwm. I had this problem when flashing this Rom The first time. It did the same thing with the LG logo then go black. If that happens just reboot to cwm(May take awhile) and reflash "the base" again. That should allow it to boot the phone fully so you can at least use it till you can get all the way back to stock. I hope this helps. I have to crash now tho. I'll check back in the morning to see how it's going.
Sent from my UNLOCKED LG-E970 using xda premium
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
The recovery won't generate a md5 sum (known bug). You have to generate it yourself. Connect your phone to adb and go to #4 in the FAQ here.http://forum.xda-developers.com/showthread.php?t=2006946
Note that there is no way to tell of the backup is corrupt since you are generating a valid code regardless of integrity.
Sent from my LG-E970 using xda premium
Murasakiii said:
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Click to expand...
Click to collapse
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Cat Rancher said:
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Click to expand...
Click to collapse
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
adfurgerson said:
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
Click to expand...
Click to collapse
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
You need to go to the IRC channel to grab the new version of lgnpst and the correct files.
Sent from my LG-E970 using xda premium
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other Didnecessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
Did you get your phone straightened out?
adfurgerson said:
Did you get your phone straightened out?
Click to expand...
Click to collapse
I'm traveling for work and on a work computer, so the IRC channel is blocked. Of course. I'm heading home tomorrow so hopefully I can get everything back to normal when i get on my home computer. (not having a phone sucks)
Do you all think it would be worth putting the base .5 on my sd card and flashing that, or do you think that wouldnt work? .4 is on there now from my original flash, but that won't work. Just curious.
Well is your phone up and running?
I would think it wouldn't cause harm to try and flash .5 onto it, your phone shouldn't get bricked from it.
i agree with Murasakiii
should be fine to run .5
DraginMagik said:
i agree with Murasakiii
should be fine to run .5
Click to expand...
Click to collapse
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
i'd say the device started having issues with the USB. unable to see the device when plugged into the computer and the device won't take a charge. don't hear of too many authentic "bricking's" anymore...it can almost always be resurrected. but if the device won't take a charge your time to resolution is rather limited. good luck.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
Before you leave to go to the store hook it up to a set up jumper cables and then attach the other end to your car battery. Then just tell them when you tried to charge it that it started smoking and wont turn on any more.
The only lie you have to tell them is it happened on the stock charger.
Im on the same boat. Tried going back to stock for a warranty return, and i ended up bricking the phone. Im able to get it to download mode and was able to run the lg tool but it keeps failing on me. And when it does complete it still wont load. Im going to try to make my self a powerd usb cable too see if i can get it to work. Have like 2 or 3 days to try to figure it out. Or elese im out 550 bucks.
Sent from my LG-E970 using xda app-developers app
Other option is just telling them you clicked install for the ota update it rebooted and never came back on. They just wipe them at the repair center anyway if they get them to boot up.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
It took 12 hrs to get a clean download of the stock ROM (AT&T internet sucks in my area). The entire time the screen on my phone was on with the LG splash screen displayed. By the time I got the ROM ready for flash, the battery was dead. I was however able to plug in to the USB on my computer and get enough juice to get into download mode. Ran LGNPST (v2.2.3) and the stock ROM installed with no prob. You might try plugging it in then trying to get into download mode.
EDIT: now that I think about it. You need to have it plugged in to the USB before download mode anyway, so you won't be doing anything different than you already did.
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
oceanisbleu said:
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
Click to expand...
Click to collapse
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
goliath714 said:
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
Click to expand...
Click to collapse
Yes of course I tried, the phone has been absolutely unresponsive. No amount of button holding is going to fix QHSUSB_DLOAD
Correct me if I'm wrong but http://forum.xda-developers.com/showthread.php?t=1948485 is the only known solution for QHSUSB_DLOAD due to firmware issue (I'm pretty sure this is what happened) or Jtag.
Here's the kicker, the files in that thread are no longer there so as it stands phone's just a Brick.
So for now I'm giving up on it and going samsung.
When I have the energy I may try working on the second one I have which turns out wasn't bricked instead the power button is unusable 90% of the time, but for now that's going to be left out of commission. Ultimately I need a backup because sprint techs seem to only operate on a 3 day basis when it comes to physical repairs therefore I plan to revive the second phone just to keep it as plan-b.
May all be user error but frankly what takes me minutes with a samsung seems to take days on the past couple of HTC phones I've had, so the ranting aspect of my post is merely in these regards and that only and out of frustration, this sucks because I'd take HTC build quality over samsung any day. I've been an HTC faithful since their first windows phone (5 years ago or so).
I know I have to fix the power button on the second phone but have any idea why it fails halfway through a factory RUU?
that's where I left off with it, it's S-On Unlocked running TWRP 2.8.0.1 I was trying to return it to full stock so I can have a go with facepalm S-Off procedure.
Did you relock the bootloader prior to attempting to run the RUU?
Magnum_Enforcer said:
Did you relock the bootloader prior to attempting to run the RUU?
Click to expand...
Click to collapse
out of 3 different RUUs I donwloaded only one worked, bootloader was relocked, ran RUU, Error 132 "Signature Error"
the one that did work the installer said finished, phone reboots but goes right back to bootloader where it says "Relocked" & "Security Warning" won't do anything else.
I was playing with it, wanted to root it and boot into twpr, but before i could do any of that, i was stuck in recovery mode! First time i restarted it into recovery to figure out how to get into twpr, i got to this screen, entered my pin 3362 and proceded to next menues, didnt find what i wanted so i selected enter to recovery again, phone restarted got to this screen again, but now my touch screen isn't working! I cant type anything! And i cant get past it! I can sthut it down, restart it, go to fast boot mode, but everything leads me to this recovery screen again where my touchscreen isnt working and i cant type my pin or anything!
DAMN THESE CHINESE SOFTWARE ENGINEERS.... i will give my phone back using warranty claim, hopefuly those morons wont fix it and ill just get a new one.... but maybe they will just give me big .I. because i live in corrupt country where law means nothing, so i wanna try my luck here.... anyone have any idea how to fix this?
I'm a newby in this things, once i menaged to unbrick my old chinese phone elephone P something, it took days of googleing trials and errors, but i menaged to install new android version which wasnt supported by my elephone.... but microphone didnt work tho xD So yall need to explain things to me in details coz im pretty noobish, but i can menage....
Man... this sucks so much..... how bad could these engineers be, i cant be first person this happened to, and this is surely a bug that isnt fixed, and i kept my phone up to date.
Happens to me as well. You can still use the volume keys to navigate around; however, you may not be able to go back once you select something. Unfortunately the only way I got around it was by installing a diff recovery, either twrp or the pixel experience recovery kronflux uses.
Don't use twrp on this phone.
Seriously. Do not.
Also, that's not recovery. That's your bootloader menu and only works through using your volume keys and the power button.
(Side note, warranty won't cover a modified device and attempting to turn in a device that's been altered can hurt later attempts at using your warranty for legit concerns.)
ninjasinabag said:
Don't use twrp on this phone.
Seriously. Do not.
Also, that's not recovery. That's your bootloader menu and only works through using your volume keys and the power button.
(Side note, warranty won't cover a modified device and attempting to turn in a device that's been altered can hurt later attempts at using your warranty for legit concerns.)
Click to expand...
Click to collapse
There are 2 pictures, second one is bootloader, yes i navigate using volume buttons, first one is recovery that asks me for password, which i can't type, because ''screen'' stopped working, and i cant get pass these screens. Did you even read my post or just saw it with left eye and decided to type a comment so i have to repeat what i allready said?
Anyways, i returned phone under warranty, and i didnt get to root it with twpr even tho that was what i was trying to do, but phone bugged out on me beforehand. Hopefully they wont give me any problems because i did ''install'' twpr in os, but that probably means nothing as it doesnt really do anything at that point.
I was following tutorials i found for this specific phone, probably bullcrap generic articles, i wont try to root it again because it seems like a problem, **** oneplus....
But, if they dispute my claim and ask for money, they wont get any, i will ask them to return the phone to me and i will manually flash it completely or whatever, and get it working. I was refraining from doing so because its under warranty and i didn't want to **** it up.