Related
Earlier today my ATT Tilt was having trouble synching to my office system; it would charge, but it would not be recognized by Active Sync. I had been planning to flash the new HardSPL tonight anyway, so I thought I'd check different cables on the home system while I looked to update the SPL.
When I got it home, none of the cables or other systems would change the basic problem: the unit would charge, but the device would not be recognized. I tried soft resetting it, but that did not help. I thought I'd try taking the battery out, then try a hard reset.
After taking the battery out, the system went straight to the tricolor boot loader, with "serial" underneath. The micro SD card it had in it wasn't formatted for FAT32 and didn't have an image on it, so it just stuck there.
I removed the microSD card.
I then tried plugging in the USB cable (which does change the screen from serial to USB), but attempting to flash a ROM still fails, as the USB connection still seems to be dead for that. Hard reset does not change this; it goes straight to tricolor.
It didn't seem to be charging on the usb or on the charger (no yellow light), so I also I removed the battery so as not to waste any remaining charge.
My current theory is to get another SD card in the morning, format it with FAT32 and see if it will flash a rom. Any other, better ideas?
Since I had the (v1) HardSPL on it with one of Dutty's ROMs, I am a
bit afraid to send it in for warranty replacement repair, at least until
I can restore it. But if I can't get anything to it, it's going to be a bear
to get through the diagnostic update to restore the original rom.
If I am missing anything obvious to try here, I'll glad take the noob points, but I'm stuck for better ideas.
Thanks for any thoughts.
Mtty doesn't work
Meant to mention that mtty.exe doesn't work through USB.
No Joy with sd card, hmm
So, I re-formatted the SD card, put an image on it, and it was recognized. It loaded the radio and OS, gave a success message and stayed on the white screen. I did a soft-reset, according to the "Flashing with SD cards" instructions, and it returned me to the boot loader and offered to re-run the install. I did that (why not, I guess?), and it did the same thing.
This had been Hard SPL'ed, but I'm trying a return to the stock ATT rom now. Any other thoughts much appreciated.
<edited>Same thing happens with the stock ATT rom. If I load it via SD card, it reports success, but a reset returns to the tri-color screen if the SD card is taken out and to the "loading" screen if it is not.
Hey there,
It seems I have a similar problem as you. A few days ago, I wanted to install this rom:
http://forum.xda-developers.com/showthread.php?t=392245
There was a hardSPL with it. Copied it to my device, ran it (went into tricolor mode, so that's good). From there, I wanted it to flash it, but my laptop didn't recognize my Kaiser anymore. Soft-resetted the thing, went back into windows mobile.. good. Bu from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
moos said:
Hey there,
But from that point, my laptop didn't recognize my Kaiser anymore, it just charges the damn thing..
EDIT:
Laptop now recognizes my phone.. when updating, the screen freezes on the white screen with the percentage bar (how many % is done flashing the romd)
damn.
Click to expand...
Click to collapse
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
I have had some issues with getting usb to recognize in the tricolor screen. In my latest spl flash, it took about five trys to get it to work, you have to be persistent some times.
Anyways the steps to get it recognized are as follows:
1. I plugged the phone in, (with the os booted, you can't do this obviously) and waited for activesync.
2. Went into bootloader mode, in the tricolor screen it said I had USB, but I was never able to flash.
3. Disconnect the usb while in tricolor, and wait about 15 sec and plug it back in.
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Speaking_On said:
That does sound bad, too. When you were getting the tri-color screen were you still showing the old SPL or the new one?
And what, if anything, changed when the Laptop went from charging to not recognizing the phone?
Click to expand...
Click to collapse
At this point, the tricolor screen is showin the following:
KAIS130
SPL-1.JUMPSPL
CPLD-8
I already got my laptop to recognize my phone, just gave it a reset. I'll update as soon as my phone is over 50% of charge.
i had the same problem with my usb port...
I have just been flashing roms from microSD but I am stuck with radio from hell with no way to change it without usb connection
i also wanted to flash a new spl but have read that it is not recommended to do so from sd card.
not sure if its a hardware or software problem, in either case, it is a problem with the phone, i have tried it on many different computers with many different cables and i also tested my brothers tilt which is detected by each computer immediately.
rcm_rx7 said:
4. I waited for about a minute, the tricolor screen never showed USB on it again, however it worked.
Im hoping that will help you a bit, just try to unplug and plug the usb back in. Good luck.
edit: is it showing olipro 1.00 or similar in the tricolor screen? That would be HardSPL if it is.
Click to expand...
Click to collapse
Thanks for your message. The phone is showing olipro (I had flashed it with HardSPL before all this started; I was getting ready to update it to the new HardSPL for WM6.1 ROMs). I've tried a couple of different cables and the usb seems truly gone. I have had problems with it being a bit sensitive in the past, so I think the pins have just shorted at this point.
All else has failed...
GSLEON3 said:
Use task Manager to make sure that there is not a current session of activesync running on device before plugging in. If there is kill it & try again.
I have recently had very good luck in helping others with this situation, but it is a detailed process best done over IM & takes at least 45 minutes to an hour to complete. I have a bit of a reputation for saving Kaisers. At any rate, try a few of the suggestions above, then if all else fails PM me & I'll see when I have some time.
Click to expand...
Click to collapse
Thanks for the message. There aren't two activesync sessions running on the XP system, and there are none on the phone (as it is stuck in bootloader, there is no way to get to its task manager).
After calling in to ATT and finding a fairly knowledgable tech (Ben, no last name given), it sounds like the original problem was that the mini usb slots has bent pins which caused a short. Somehow, when I removed and re-installed the battery, that short went from preventing a synch to toasting the OS. My first Tilt had a red-light of death on first charge, so I pretty much believe that something in the electronics connecting the usb/charger and battery is delicate on Kaisers.
They're going to send out a warranty replacement tomorrow, and the RMA packaging for returning this unit. I guess I'll just cross my fingers that they don't boot it and notice that it isn't a stock SPL. Given that it's being written up as a hardware issue (as it is), hopefully they won't.
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
I think I got it..
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Theoretically, yes
rcm_rx7 said:
What could they do after you get the new one? Charge you for it? Guess you never know with ATT.
Since your sending it back anyways, why not try to flash the SPL from the microSD? You might be able to revert it back to the stock ATT spl, then no worries right!
Click to expand...
Click to collapse
I did try flashing the SPL from the microSD, several times and using the stock ATT SPL was one of the choices. It reverted back to tri-color boot mode.
Theoretically, yes, they could demand payment. I've heard of them doing that if a customer said that a unit hadn't been wet, but they found that it had when they did diagnostics. Down from that, they could terminate the warranty or shut off service. Now that T-mobile is getting higher speed, that's not the threat it once was, but still.
The battery is now also empty (since it had no way of charging), so I am hoping they won't even bother.
Glad to hear it!
moos said:
This is what I did. I followed the following steps from the first post:
http://forum.xda-developers.com/showthread.php?t=354061
Then I did the same thing, but I used the rom I wanted to flash. Now the first time it got stuck @ 17%.. but on the second time, I succesfully flashed my rom. Hope this helps!
Click to expand...
Click to collapse
Glad to hear it worked for you! I couldn't get my system even close to that functional to get there, but it's good to know that you were able to get through.
kaiser usb dead
I have the same prblem as your USB is gone cannot move from tricolor screen. Cannot even flash from sd card. Check my signature for the link of my thread it explains everything that happened to it.
hello,
i'm interssested to buy it. can you send me your mail at [email protected]
Hey guys...I recently upgraded my SDA to WM6 without any problems using Kar Hoe's guide. The only thing I noticed was that I couldn't connect to the internet via GPRS/EDGE (only WIFI). So I found a radio ROM last night and forgot to format BINFS before I installed it. It said it was successful of course but now I'm stuck in the bootloader. Here's the horrible part: The phone goes in USB mode for the bootloader, but won't connect to ActiveSync so I can't reflash it or anything! I really liked this phone and can't really afford another one at this time. I'd appreciate any help I can get.
Thanks. I'll be working until 5 but will check back after that!
p.s.: When I installed WM6 previously, I DID app unlock it and make it SuperCID.
-velcro
try mtty and and kar hoe`s guide
to Profy_X
Thanks for the quick response! I've downloaded mtty (similar to Tera Term huh?). Is it possible to copy the ROM image to the mini SD card in order to flash it? I have the original one for my phone and I tried copying the NBF file to the card via a card reader I have by Vakoss but windows won't recognize it. (due to its format right?)
I know I have too many questions but I need my phone. http://forum.xda-developers.com/images/smilies/confused.gif
Thanks again!
I have the same problem and really looking for a solution.
The phone enters bootloader mode after pressing the camera button and inserting the usb cable. However activesync or anything else does not recognize the device. mtty and teraterm cannot connect to the device.
When I hard reset or turn off/on the phone, it keeps resetting itself after a couple seconds of booting.
Any ideas what I can try?
I fixed it...
I tried everything! I ended up extracting this fileTor_TMOUS_10140_191916_10900_SHIP.exe with winrar and running the RomUpdateUtility. Even though ActiveSync wasn't working I went through with it. It randomly worked though! So then I just followed Kar Hoe's guide for installing wm6. Now the only thing is that it will turn off randomly unless it's plugged in. And it's not the battery though. lol 0_o
To Burkay: If mtty or teraterm can't recognize your phone then the only thing you can do is copy the original ROM to your memory card and then flash it directly from the phone through bootloader....or at least that's the only way I can see since USB's out.
After an unsuccessful rom flash, phone always stuck to bootloader screen, it happened 2 or 3 times on my phone. In these cases ActiveSync couldnot recognized my phone (thru USB). But I always successfully reflash my phone just running RomUpdateUtility connecting thru USB. How come so complex in your cases, I just wonder
unforsakenrule said:
To Burkay: If mtty or teraterm can't recognize your phone then the only thing you can do is copy the original ROM to your memory card and then flash it directly from the phone through bootloader....or at least that's the only way I can see since USB's out.
Click to expand...
Click to collapse
I agree. I just don't know how to flash from an SDCard. Do you have a tutorial?
burkay said:
I agree. I just don't know how to flash from an SDCard. Do you have a tutorial?
Click to expand...
Click to collapse
I don't...but if I find one I'll def let you know
thacen said:
After an unsuccessful rom flash, phone always stuck to bootloader screen, it happened 2 or 3 times on my phone. In these cases ActiveSync couldnot recognized my phone (thru USB). But I always successfully reflash my phone just running RomUpdateUtility connecting thru USB. How come so complex in your cases, I just wonder
Click to expand...
Click to collapse
Well...It might just be my battery after all (current surge or something). Because I tried 2 different wm6.1 roms and now am using Nitro's wm6 rom, and the same thing would happen on all of them (but less on Nitro's). It looks like if I do something demanding then it turns off after a minute or so. And there's no warning at all. It seems to try to turn back on, but fails. After that, the only way to start it is if I plug in the charger.
I'm going to order another battery from ebay and we'll see what happens I guess.
I hope it works!
@unforsakenrule: When i flashed, normally it takes hardly 10min, how your battery discharge so quickly. I tried most of rom found here now I stick to Kamikadze's 6.1 pro, it is quite cool and I don't want to back to STD.
Sometimes, flashing did not success and I tried again but I am always sure to be fully charged before start. If it stuck in bootloader charging is not easy. I sometimes use some crude method on my other phone, just connecting terminals of charger to battery directly using some wires, but it is really dangerous
thacen said:
@unforsakenrule: When i flashed, normally it takes hardly 10min, how your battery discharge so quickly. I tried most of rom found here now I stick to Kamikadze's 6.1 pro, it is quite cool and I don't want to back to STD.
Sometimes, flashing did not success and I tried again but I am always sure to be fully charged before start. If it stuck in bootloader charging is not easy. I sometimes use some crude method on my other phone, just connecting terminals of charger to battery directly using some wires, but it is really dangerous
Click to expand...
Click to collapse
That's pretty hardcore man! I'll try that ROM out and see what happens. In the meantime, I'm still waiting for a battery I bout on ebay. Thanks!
I received my new battery today~
No more problems since I got my new battery. The old one was a Sanyo and apparently had issues. The new one's a Celxpert. I'm now running wm6.1 Pro and it IS tight. Thanks for your responses guys!
-unforsakenrule
I just got this phone not 2 months ago and out of no where it just died!
I was running the recent Energy ROM on it and have been since it came out. Today it ran just fine as always and just a few minitus ago I went to check it and I could not get the screen to turn on. I pulled the batter out and then went to turn it back on, I would vibrate like it was going to start up and a few seconds it would go black and vibrate again. It did this over and over till I finaly tried a hard reset. I was able to get into the hard reset and it said that it compleated and I hit power up to boot. But then the screen got fuzzy and would not boot, so I pulled the battery again and now I can't get it to start at all! No power, nothing! Even with the power cord pluged in it doesn't do anything, not even light up showing that it's being charged!!
What should I do, or check?
Not knowing particulars I would double check the water intrusion labels and make sure they were both white still. Check your gold battery connectors and make sure those look good. Also check your charger and the USB plug to make sure that it is clean of debris and shiny.
Then I would charge the phone for 4 to 8 hours without attempting any boot ups just to make sure it was fully charged.
I have had 'wonky' issues with the phone being too low of a charge and not booting properly. Sorry I can't be of more help.
I will hook it up to a charge tonight and see if that does anything, but it was atleast at 60% eairlyer and as far as I know should be no reason that it should have discarged that quiclky. Also all the markers look just as they did out of the box. Thanks for the advice!
Your ROM might have gotten corrupted. Try a reflash by booting in bootloader mode.
How? It won't turn on?
wingman1487 said:
How? It won't turn on?
Click to expand...
Click to collapse
Try pulling out the battery (and no USB plugged in) then hold the volume down or up button (I don't remeber which) and hit the power button just once while holding the volume button and if you get to boot loader mode you can go from there. Otherwise I'm afraid you are out of luck.
So with no battery I can get to boot loader mode?
Anyways, in or out, nothing. How does my phone just brick itself? I didn't do anything to it!?
If you could do a hard reset, then you can get into bootloader. Just press and hold volume down and then soft reset. If you have to do, a hard reset first, then go into bootloader when the screen says to press volume up to boot up. Once in bootloader, either flash a rom of your sd card if you know how to or off the usb connection.
What radio do you have, and did you change radios recently? I'd recommend using what nrg says (1.14.25.05) with his rom.
I was able to do a hard reset and now nothing is happening. I cant get it to power up, can't get into boot loader, nothing. It is acting like it is bricked... but I haven't added new software, no new ROM... I just don't understand.
Just pull the battery and let it sit overnight. I've read that that can help.
Oh, yeah, what radio are you using? I ask because there was another poster with a similar problem on that rom. He was using a 1.12.xx.xx radio (I think .25.19), and it appeared to have issues with the included rilphone (1.14.25.05). If you haven't flashed a radio and are using a stock fuze radio, this could well be your problem.
Humm the radio was the most recnet one by HTC. The on that the Energy ROM flashes with stock (not the one he suggests, I never got to flashing that one onto the phone) I'll let it sit tongith and report back in the morning/afternoon.
wingman1487 said:
I just got this phone not 2 months ago and out of no where it just died!
I was running the recent Energy ROM on it and have been since it came out. Today it ran just fine as always and just a few minitus ago I went to check it and I could not get the screen to turn on..
Click to expand...
Click to collapse
Same thing happened to me few minutes ago. Thats ****ing weird. Hope I still get this working or I have most expensive piece of junk in my hand.
I also have newest Energy ROM and stock Radio. I had just wrote sms few minutes before, heard that got new sms and tried to turn on screen, but it just stays black.
edit. By using Pocket Controller-PRO I can see that phone is working "normally". Even touch screen is working, but screen is just blank. Keyboard is also dead. Have to take this to repair
nolla said:
Same thing happened to me few minutes ago. Thats ****ing weird. Hope I still get this working or I have most expensive piece of junk in my hand.
I also have newest Energy ROM and stock Radio. I had just wrote sms few minutes before, heard that got new sms and tried to turn on screen, but it just stays black.
edit. By using Pocket Controller-PRO I can see that phone is working "normally". Even touch screen is working, but screen is just blank. Keyboard is also dead. Have to take this to repair
Click to expand...
Click to collapse
Well, flash it back to stock and then have it repaired or replaced. You don't need the screen working on the phone to flash it.
To post an update, I pulled the battery and left it all night like that with no resolve. Right now I have my buddy (the one I bought the phone from) on the phone with cingular to see if there is anyway we can get them to replace the phone since it is only 2 months old or so.
Ok! Get an iPhone now
raydm said:
Ok! Get an iPhone now
Click to expand...
Click to collapse
HAHAHAHA Ya that is somthing that isn't going to happen.
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
ryaske said:
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
Click to expand...
Click to collapse
I run any radio I like on my phone and I never got this issue. Sounds like a hardware issue and it just happened to match that the two persons flashed the same ROM without changing the radio to the recommended one because, frankly, I just flash any I want and I haven't gotten that problem yet (mind you I flash sometimes 5 times a day.)
ryaske said:
so two people having this problem .. one of them didnt update (downgrade) their radio to the one recommended.
I have a new fuze, just installed Energy Rom.. and went to check my phone version. It was 1.14.25.35 ... NOT the one that was recommended. So I downgraded the phone to 1.14.25.05 immediately
I would be interested to know if the other person was also running 1.14.25.35 and didnt bother to downgrade as recommended.
Other than that ... tons of people are using this ROM and afaik you are the only two to get a black screen like that. Both of you were able to communicate iwth the phone through a remote program? Or only one?
Click to expand...
Click to collapse
You're probably fine with that radio; you can always install the rilphone.dll for it.
This is the thread I was thinking of. Now that I re-read it, the OP didn't specify the rom, but since everyone is on NRG rom, I guess I just assumed that was what it was. Either way, the 1.12 radio seemed to not get along with the cooked in 1.14 rilphone. Or, it could've just been bad luck on the radio flash.
Just wondering how often are people experiencing this problem when the phone become completely unresponsive (unable to turn on, unable to detect, no light when charged).
I had this problem and never had it resolved and just sent the phone back for repair. It seems more and more people are posting they have this problem. Is this a ROM problem or does the HTC phone just get fried? Mine happened after I installed Revolution 6.6.2..it rebooted fine...and reinstalled apps with titanium..then all of a sudden a long tone while I was on phone and the phone unresponsive, turned off...and never turned on again.
Anyone with same problem...would appreciate your experience..and maybe we can figure out why it's happening. And I mean...the phone is just dead...no bootloop, no adb...nothing.
I ''had'' rooted Sensation Juopunutbear S-OFF,I filled the battery full...and install AOKP ROM Everything is working fine....After resetting the phone,
He did not respond...do not want to boot,does not want to even turn on,I tried everything from taking the battery to charge...no signs.....
when connecting phone to computer,sound is heard...and requires some drivers QHSUSB_DLOAD
removing battery sim sdcard and connect to power outlet and tried to switch it on-nothing...not react
is still under warranty....9 months old
I asked no one knows why it happened
I sent it to the service and I hope will not notice that he S-OFF and ROOTED :\
there are still a lot of people this problem here http://forum.xda-developers.com/showthread.php?t=1618683
Hmmm..at least yours is detected on computer. Mine was completely unresponsive...nothing worked. Some had similar problem as mine when not even the computer detects it.
IT seems to be happening quite often..and I am not sure if it's a ROM problem....but it seems it's not only from a specifice ROM.
I had one just like the op except it was stock with s-off, no custom rom yet. I turned it off and it never came back, so got a new one!
From another similar thread:
Charge your phone for 20 minutes. If you're using a Sense ROM, disable fast boot in Settings>Power. Fastboot doesn't actually power off your device, just puts it into sleep, like in Windows. This means the battery drains, even while it's "off".
On this forum, we see it atleast once a week. Something was going totally fine, no biggy, then suddenly it won't turn on, seemingly won't charge, no LEDs, not recognized by PC, etc etc.
The odds are low that it'll happen to you, but more so than other phones.
sshede said:
On this forum, we see it atleast once a week. Something was going totally fine, no biggy, then suddenly it won't turn on, seemingly won't charge, no LEDs, not recognized by PC, etc etc.
The odds are low that it'll happen to you, but more so than other phones.
Click to expand...
Click to collapse
But is this related to hardware issue or a custom ROM / firmware problem? My question is....should I try to root and do the same thing again if my phone get replaced?
If it's related to custom ROM/firmware pb...maybe it needs to be looked at? Especially when everything is running fine like many people report...
Well it would be nice if ALL of these occurrences were logged into a single thread and each user listed their firmware, rom, and kernel (which I'm most interested in)...
well i got the same problem . while playing a game phone got stuck and automatically turned off with some sound . now its desnt turning on and cant charge it coz led doesnt working ( what should i do?? going to use a another battery . if not :s idk (
Experience Senseless
HTC sensation XE with beats audio
Unlocked -Revolutionary
Pyramid Pvt S-off
Hboot 1.27.0000
Radio 11.22.3504.07_m
CID 11111111
Hi to all,
I'm in a similar situation, yesterday I updated the 4ext recovery the beta (sorry dont know what version it is) and it worked fine on the phone.
Until I thought hmm, I try [ROM][04/26/12] Virtuous Inquisition v4.0.2 :: AOSP-Experience Senseless ICS (4.0.3). I was going through the software and I've done a format on the microSD card though virtuous, and done a REBOOT on the phone, no Reboot at all. By the way while running the OS lights for the Home, Menu, Back and Search weren't truned on.
Now my phone wont turn on (although I can hear the USB being connected to my windows7 X32 bit PC). When connected to Pc or power outlet there is no indication of my phone is charged or being recharged, no light indicator.
Ok, so what if I tried using ADB commands to see if my phone still beeing detected.
I used ADB under Administrator
adb devices
*daemon not running. starting it now on port 5037 *
*daemon started successfully*
List of devices attached ( although i dont get the model number of the phone)
fastboot reboot
waiting for device
fastboot reboot-bootloader
waiting for device
fastboot flash recovery recovery.img
waiting for device
Ok no luck. Now tried to do install with the RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R_Radio_11.69.3504.00U_11.22.3504.07_M_release_251961_signed.exe
Runed under Admin again, so still no luck, all I get was an Error[170] usb connection Error. So the utility rom still could not detect the phone.
By the way when the phone is off, then I press volume down and power button, my phone is AOSP-Experience Senseless indeed, can't switch nothing on.
All well see what happens.
Yes..I think it's good to have a thread about this problem...maybe some more experienced DEVs can see why this is happening especially if this is occuring because of ROM/firmware or more hardware problems.
I am waiting for my phone to be sent to HTC and see what they say..hope they'll fix/replace one!
Battery, Brick or Senseless
By any chance, did anyone tried to use some friends or family they have the same phone, and use their battery. Maybe battery needs replacing?
Hopefully I can here someone says that I'm right, battery problem.
Also I'm looking at other websites to see whats the alternative to our situation.
Or maybe its just a brick, I will wait and see the Developers of this thread
http://forum.xda-developers.com/showthread.php?t=1522351
[Release coming next week. With a surprise!] Sensation Unbricking Project
hopefully will have a solution I feel lost without my phone, AOSP-Experience Senseless these two days.
God bless them hope they can do it.
barascus said:
By any chance, did anyone tried to use some friends or family they have the same phone, and use their battery. Maybe battery needs replacing?
Hopefully I can here someone says that I'm right, battery problem.
Also I'm looking at other websites to see whats the alternative to our situation.
Or maybe its just a brick, I will wait and see the Developers of this thread
http://forum.xda-developers.com/showthread.php?t=1522351
[Release coming next week. With a surprise!] Sensation Unbricking Project
hopefully will have a solution I feel lost without my phone, AOSP-Experience Senseless these two days.
God bless them hope they can do it.
Click to expand...
Click to collapse
For some it could be battery problems....but I think most of the ones reported it's not. As with mine..the battery was fully charged 100% when it happened...I think it was actually plugged in even.
The thread is for bricked phone that had this driver thing when it plugs into the computer...but if the phone is completely unresponsive...it's not goign to work!
I kept my phone charged for few hours, although my battery was full as well, the phone remained cold.
i had a similar problem last week on 04/19... battery was charging over night... at morning i turned the alarm off and after that the phone was dead... i sented it to support and now i have a new board inside and totaly new problems...locked bootloader and an unkown H-BOOT version (1.29.0000)
i also tried my battery in a other phone with no problems.
i had revolutionary 6.3. on it
Hello,
When connected to a PC, it is showing up as "QHSUSB_BULK". I only have official software from AT&T OTA, and phone is not rooted.
From my reading online, it means hard brick..... I cant get into recovery,download modes or anything at all now..... definitely not motherboard since the phone turned on over the weekend, when battery was almost zero and had to connect to charger to completely turn on.....
Tried downgrading to kitkat from lollipop because a continuous restarts.
Currently, neither fastboot nor ADB recognises this phone or I cant use LG flash tool to install official kitkat onto it. I have tried looking at various forums and couldnt find this exact situation of phone not turning on at all. Also phone is not showing up in disk partitions as well
Can someone tell me how to fix this phone, having this issue from almost 3 weeks now.
I got a same problem, In my case, I changed the battery then fixed the problem
ANy help guys...This G2 forum is too quite
Any help people.... Its been more than a month now
If you cannot get into DOWNLOAD or fastboot then you will have to open the device up and short out the 2 circuits. I just had the same thing happen to me when I ended up putting mismatched boot files on the system. It is time consuming and a pain but really not that hard. MAKE sure you have the right tools. I bought some off amazon before doing.