Related
My friend is running CM 7 on his Tmobile G2.
He was describing that yesterday was acting weird with market downloads.
Here is what he he emailed me on what happened.
the phone was acting normal throughout my day until the evening towards the night, i noticed it failed to finish downloading the update for google earth along with google maps. the phone was fine, and then i pulled it out of my pocket a few times and saw multiple times that it was randomly turned off. i would turn it back on and it would still give me the same issue. when i got home and plugged it in to charge, it would boot and then get to the main home screen telling me that google maps is downloading to update. however the update would be frozen, and a few seconds later the phone would freeze altogether, forcing me to turn it off by pulling out the battery. this happened about 4 times, and now has reached the point that it has become a brick and refuses to turn on or show the charging light
any suggestions on what might be wrong with the phone? Thanks in advance. Im running Cm7 on my phone and never experienced this issue.
same happend to me 3days ago, phone running then freezed... bootloop after batterypull... recovery worked for 2 times but had problems with flashing new rom/backing up -> errors with cache partition...
after 4hours of letting it stay off -> it wont turn on again und wont charge (no LED)
tried it with another dz battery+charger... no change... i wrote htc and they answered within 1hr that i have to send it in without battery...
i guess its a known problem (or why wouldnt they want to have me sending in charger+battery .. if its a power-on problem..)
there are semibrick threads here and in other forums.. but they all don't suffer from the power on problem... so i guess i did the right thing sending it in
edit: never had heat issues, never had random reboots, no overclock, no indication of an update from any app did any harm to my phone, running cm7 for 3 weeks without any problems, no hboot flash, no radio flash ... nothing that would indicate a risk of brick (according to guides & forum threads)... first htc that ever failed for me ;(
Thanks for the reply. I will forward it to my friend. I think he is going to try to exchange it at the store and if it all fails we are going to try HTC.
have any of you tried to boot into recovery? did you have eng-hboot on your devices? go to #g2root
its complete dead as in dead... no LED light, no turn on, no hboot mode (or what its called when you press vol+power key).... i dont have a g2 but a unbranded european dz.. hboot and radio was never touched by me
Similar thing happened to me. My phone kept frozing on me running cm7..was fine for a week though.
So I booted into recovery..wiped cache,factory reset flashed another rom got bunch of erros recovery thing rebooted stuck i n htc logo for like 20min yanked out battery rebooted and it never rebooted back. No hboot,no nothing.
My light indicator still worked though but no hboot or anything.. got a new one now have to send the old one back to tmobile but I'm scared that they're gonna charge me for removing void stickers.
Even though I checked twice that removing void sticker won't avoid warranty according to tmobile customer chat sevice..
So I'm thinking about swiping out the sticker that contains serial number and such on back of our phone with the old one and tell them the new one came without a void sticker lolol
Sorry I got way off topic rofl..
Sent from my HTC Vision using Tapatalk
We went to the store today and exchanged it for another g2. The guy didnt ask any questions and exchanged it happily for a new one.
This very same thing happened to me today. Updated to CM 7.0.3 from 7.0.1 and the phone was freezing when installing items from the market. Pulled the battery and the phone was stuck on the boot animation. Pulled the battery again, and now it will not start at all. No charging light, no nothing. Had more than 50% charge, and now it seems entirely unresponsive. I can't use the power w/ volume button technique either, because the phone does not respond.
Seems like somehow I have bricked the phone, or the phone just coincidentally died just after updating to CM 7.0.3? (seems unlikely)
just a short update on my case:
i got the mobile back from HTC repairs.
they exchanged my "mainboard" (changed IMEI) under warranty.
i don't know what emmc chip i had before cause it died so fast, but my usb deviceIDs changed completely and are now simmilar to the ones in the cm wiki.
my current emmc is now:
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
SEM04G
Click to expand...
Click to collapse
might help ppl.
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Mr_Pistachios said:
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Click to expand...
Click to collapse
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
another Xperia Play Problem
Hi I am a noob also.
I am having a similar problem. Today I was trying to install the wifi module since it wasn't installed on the gin2Jellybean rom, i tried to flash the phone using the Flashtool (turned the cellphone off and pluged it in again while holding the back button) then the window disappeared and nothing happened. So I tried again, but first I took out the battery and put it in again and tried to flash again and now nothing is happening, Doesn't turn on, Flashtool doesn't do anything and when I try plugging it the laptop does the sound of an unrecognized device. The phone doesn't vibrate or anything when I press the power button.
Just realized that I tried flashing my cell phone using the x10 BLRelock.ftf crap.. is there anyway I can fix this?
Please Help.
Thank you.
216Monster said:
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
Click to expand...
Click to collapse
Flashtool and fastboot doesn't detect my phone. So yea .
Mr_Pistachios said:
Flashtool and fastboot doesn't detect my phone. So yea .
Click to expand...
Click to collapse
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
216Monster said:
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Mr_Pistachios said:
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Click to expand...
Click to collapse
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Mr_Pistachios said:
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Click to expand...
Click to collapse
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Mr_Pistachios said:
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Click to expand...
Click to collapse
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Mr_Pistachios said:
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Click to expand...
Click to collapse
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Mr_Pistachios said:
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Click to expand...
Click to collapse
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Made sure to on my phone with the sim card in this time
Never gonna off my phone ever again (Hope it doesn't run out of batt LOL)
One thing to note is this really weird fluctuation in my phone's battery levels. Maybe my battery is going nuts? Attached is the screenshot.
Made sure to on my phone with the sim card in this time
The epic fluctuation may provide clues as to why my phone's behaving like so.
As you can see from the third dip, I was charging my phone. And then after switching it off, it wouldn't turn on. After a day, and countless times of trying to wake it up, you can see that the battery level has dropped sharply. Weird.
The first dip happened a few days ago(not able to turn on) on 1st Feb. The second dip happened on the 4th, while the third happened on the 5th, today These drops in battery levels happened when my phone couldn't turn on.
Qhsusb_dload
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
extrem3hunt said:
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
Click to expand...
Click to collapse
Does plugging the phone into the computer while holding the back button work?
Mr_Pistachios said:
Does plugging the phone into the computer while holding the back button work?
Click to expand...
Click to collapse
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Even if it finds the driver, it wouldn't help you, cos QHSUSB_DLOAD means that the phone can't find the rom, and kernel or whatever. (I think) Its like a computer without an operating system. QHSUSB_DLOAD = Qualcomm Highspeed USB Download Mode, which means its waiting for the manufacturer to flash the rom and shyt, and therefore, your phone is bricked. (Dead brick, i think?)
For me, i think there's something wrong with the connections in my motherboard, resulting in the phone not being able to find the rom and stuff.
Maybe there's no hope for you.........
In short, I think your phone's bricked forever.... Most probably.
any fix bricked play
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
QSHUSB_Dload Fix
tommyforest123 said:
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
Click to expand...
Click to collapse
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
extrem3hunt said:
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
Click to expand...
Click to collapse
Well, okay, imma give it a try, tnks.
Before flashing your "bricked" device, try this!
Mr_Pistachios said:
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Click to expand...
Click to collapse
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
proteusgr said:
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
Click to expand...
Click to collapse
HAHAHAHA LOL.
Glad it worked out for you
My guess is that there's something loose inside, and repeatedly trying to do that may help.
I think it's something to do with Sony's build quality, or maybe because the phone sustained hard knocks and stuff. (Probably just wear and tear)
Aledranssimo didn't reply me, so yea. T.T
This issue is probably an intermittent one I guess. I've since moved on and gotten a new phone (Lumia 520)
Hello,
Today, while I was using my phone, it restarted itself and has been stuck at a boot loop almost entirely since then. It has successfully booted up 2-3 times but will usually restart itself within 30-45 seconds of booting and then will be stuck in a boot loop again. When it has started up its usually after it has been bootlooping for a while. I have an H811 , I'm rooted and using xTreme Rom v2.0. I have had occasional random reboots here and there before but the phone always booted right up again without any issues. I haven't done anything with root/recovery since early September.
I've tried doing a factory hard reset without any luck. My phone booted up after I tried the hard reset and it was like the reset didn't happen. I can't boot into TWRP. I can boot into download mode and I tried to reset using kdz. It got to 100% but the the phone restarts and is back in the boot loop (then the lg flash tool gets an error and force quits). I've tried removing my sd and sim cards, I've tried swapping to a different battery, I've tried leaving the battyer out and letting the phone cool down. Nothing is working. I have noticed that when the phone is going to boot up correctly the full LG animation plays. When the phone is going to boot loop I only get a static LG Powered by android image.
Since I tried and failed to reset to stock using kdz, the phone no longer boots up past the LG screen. I've redownloaded the kdz file and tried to reset again with the same results. When I have it in download mode Windows recognizes the phone but it says there's an issue with the MTP driver. I've reinstalled the drivers and I still get that the MTP function isn't working correctly.
Any suggestions?
Hey man u r just having my problem. There is a thread already for this http://forum.xda-developers.com/showthread.php?t=3233160
Did u do CSE flash? If not, try to connect via adb.
Sent from my LG-H815 using Tapatalk
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
IrieBro said:
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Click to expand...
Click to collapse
Yah mine was also on charge while it happened. But it was on LG provided charger.
nipun1110 said:
Hey man u r just having my problem. There is a thread already for this http://forum.xda-developers.com/showthread.php?t=3233160
Did u do CSE flash? If not, try to connect via adb.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll try reposting this there. I did use CSE flash. Oddly enough it booted up once this morning for about a minute then got stuck and rebooted. Now its back in the boot loop.
IrieBro said:
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Click to expand...
Click to collapse
Sounds like the boot loop issue is a decent sized one- quite a few others, from different variants, having all having a similar issue. For me I was walking with my phone checking facebook when it restarted and got stuck. I definitely notice the LED issue too. I'm not on jump but will likely go into T-Mobile today and see what they tell me.
HappyPessimist said:
Sounds like the boot loop issue is a decent sized one- quite a few others, from different variants, having all having a similar issue. For me I was walking with my phone checking facebook when it restarted and got stuck. I definitely notice the LED issue too. I'm not on jump but will likely go into T-Mobile today and see what they tell me.
Click to expand...
Click to collapse
They will give u a replacement. that's all. but noone will say what's causing it.
Sent from my LG-H815 using Tapatalk
HappyPessimist said:
Thanks. I'll try reposting this there. I did use CSE flash. Oddly enough it booted up once this morning for about a minute then got stuck and rebooted. Now its back in the boot loop.
Click to expand...
Click to collapse
Exactly what happened to me. now after CSE flash of KDZ, it won't start at all. just boot looping. also after hard reset.
Hello everybody,
Yesterday I was on my phone and when I went home using the navigation gesture the phone all of a sudden rebooted, and I thought "Okay, it's just a one time error". When the cellphone booted again it showed the logo and then black screen and a WhiteLED on, it seemed bricked, so I reset the whole phone and it was alive again. However, once again today the same thing happened, no root, no mods, all stock. Has this happened to anybody else ? Do you guys think it's a hardware matter or just software ?
P.S: Happened when I was on Open Beta 10 and this time on OOS 5.1.3. Can't boot into the system nor Recovery, fastboot is fine.
*Update: Phone is now completely dead, won't even turn on
Thanks.
100% sure its motherboard fault
EugenStanis said:
100% sure its motherboard fault
Click to expand...
Click to collapse
Me too, I remember having an LG G4 back in the day that wouldn't pass 6 months without having to change the mobo, it might be a similar case.
Hi all!
My father's Oneplus 3 (A3003, 64gb) died a few days ago while he was waiting for his new oneplus 6 (if only it died after migrating... sigh), and i'm trying to troubleshoot it.
The display went dark after a night, no led, nothing. He plugged it to a computer, and a device called HS-USB Qdloader 9008 appeared in the device manager.
I thought it was bricked, so we followed the unbrick stepps (even the full package).
Nothing happened on the display after reboot, black screen after a short vibration, then a few minutes later another vibration, and so on...
I let it alone for a few days then tried again to see what was happening, and went again with the unbrick process. This time it completed successfully and i was able to see something on the display, but very very dim!
It booted to the stock OOS, then it rebooted right after arriving on the OOBE, and it froze while booting after that.
Again i let it alone for a few hours, and tried again, outside in the cold. This time it "worked", with the very very dim display though, i could barely see what was happening on the screen, but i was able to set it up including wifi and play store, and i could do a benchmark using geekbench successfully (score was on par with other OP3).
I went inside and tried again a few hours later, and it froze right after launching the benchmark, rebooted and froze during boot. Then i could do nothing to make it boot again (while it was warm anyway).
tl;dr : It only "works" when it is cold, and the display is barely readable. I'm thinking it could be the motherboard or the display, but would a display issue cause the reboots when getting warm? Seems weird to me!
i attached pictures of the failing OP3 next to my OP3T to highlight the display issue, the "band" visible on the 1st picture is not visible to the bare eye, only on camera and it "moves", no idea why this happens.
EDIT : i was able to unlock it while it was "working", if it is of any importance...
Blubster said:
Hi all!
My father's Oneplus 3 (A3003, 64gb) died a few days ago while he was waiting for his new oneplus 6 (if only it died after migrating... sigh), and i'm trying to troubleshoot it.
The display went dark after a night, no led, nothing. He plugged it to a computer, and a device called HS-USB Qdloader 9008 appeared in the device manager.
I thought it was bricked, so we followed the unbrick stepps (even the full package).
Nothing happened on the display after reboot, black screen after a short vibration, then a few minutes later another vibration, and so on...
I let it alone for a few days then tried again to see what was happening, and went again with the unbrick process. This time it completed successfully and i was able to see something on the display, but very very dim!
It booted to the stock OOS, then it rebooted right after arriving on the OOBE, and it froze while booting after that.
Again i let it alone for a few hours, and tried again, outside in the cold. This time it "worked", with the very very dim display though, i could barely see what was happening on the screen, but i was able to set it up including wifi and play store, and i could do a benchmark using geekbench successfully (score was on par with other OP3).
I went inside and tried again a few hours later, and it froze right after launching the benchmark, rebooted and froze during boot. Then i could do nothing to make it boot again (while it was warm anyway).
tl;dr : It only "works" when it is cold, and the display is barely readable. I'm thinking it could be the motherboard or the display, but would a display issue cause the reboots when getting warm? Seems weird to me!
i attached pictures of the failing OP3 next to my OP3T to highlight the display issue, the "band" visible on the 1st picture is not visible to the bare eye, only on camera and it "moves", no idea why this happens.
EDIT : i was able to unlock it while it was "working", if it is of any importance...
Click to expand...
Click to collapse
Looks like a Display issue. It is possible that it triggers the booting issue, though I am not sure about the "hot & cold" issue. May be a loose connection. Did it suffer a fall in the past? If you are upto it, check some videos on opening the phone and check and clean the connections. It may help.
tnsmani said:
Looks like a Display issue. It is possible that it triggers the booting issue, though I am not sure about the "hot & cold" issue. May be a loose connection. Did it suffer a fall in the past? If you are upto it, check some videos on opening the phone and check and clean the connections. It may help.
Click to expand...
Click to collapse
Thanks for your answer, i just looked at the requirements to open it, and i need a T2 screwdriver, which i do not have yet, the smallest i have is a T3 unfortunately.
I think it did fall a few times, but no issue right after at least. It may have loosen the connections though, you're right...
Blubster said:
Hi all!
My father's Oneplus 3 (A3003, 64gb) died a few days ago while he was waiting for his new oneplus 6 (if only it died after migrating... sigh), and i'm trying to troubleshoot it.
The display went dark after a night, no led, nothing. He plugged it to a computer, and a device called HS-USB Qdloader 9008 appeared in the device manager.
I thought it was bricked, so we followed the unbrick stepps (even the full package).
Nothing happened on the display after reboot, black screen after a short vibration, then a few minutes later another vibration, and so on...
I let it alone for a few days then tried again to see what was happening, and went again with the unbrick process. This time it completed successfully and i was able to see something on the display, but very very dim!
It booted to the stock OOS, then it rebooted right after arriving on the OOBE, and it froze while booting after that.
Again i let it alone for a few hours, and tried again, outside in the cold. This time it "worked", with the very very dim display though, i could barely see what was happening on the screen, but i was able to set it up including wifi and play store, and i could do a benchmark using geekbench successfully (score was on par with other OP3).
I went inside and tried again a few hours later, and it froze right after launching the benchmark, rebooted and froze during boot. Then i could do nothing to make it boot again (while it was warm anyway).
tl;dr : It only "works" when it is cold, and the display is barely readable. I'm thinking it could be the motherboard or the display, but would a display issue cause the reboots when getting warm? Seems weird to me!
i attached pictures of the failing OP3 next to my OP3T to highlight the display issue, the "band" visible on the 1st picture is not visible to the bare eye, only on camera and it "moves", no idea why this happens.
EDIT : i was able to unlock it while it was "working", if it is of any importance...
Click to expand...
Click to collapse
You just need to Flash Latest OOS
this type of issue was happened to me 2 months ago, i successfully recovered display by Hard bricked method
first of all i used Qualcomm hard bricked method to get my 1+3t to working condition (display was as you showed in picture) with Qualcomm Tool's Old builtin firmware
then i I flashed OOS 5.0.4 and its all done with Bright Display. I did not opened the phone.
Hayatzada said:
You just need to Flash Latest OOS
this type of issue was happened to me 2 months ago, i successfully recovered display by Hard bricked method
first of all i used Qualcomm hard bricked method to get my 1+3t to working condition (display was as you showed in picture) with Qualcomm Tool's Old builtin firmware
then i I flashed OOS 5.0.4 and its all done with Bright Display. I did not opened the phone.
Click to expand...
Click to collapse
Thanks ! I sideloaded oos 5.0.8 and now the display is fine !
It still freezes when getting warm every time, if I put it outside in the cold i can do benchmarks without issues, but as soon as I try the same inside it freezes. Since I already unbricked it, it seems hardware related but outside of the motherboard, what could be the reason ? Can the battery be responsable for that ?
The freeze happens very quickly inside, it does not get hot, barely warm at the top of the screen.
as far as my idea is concern you have another 1+3/t, to confirm battery issue swap your motherboard or battery with the other one, it'll confirm the battery. other than battery issue check lose connections/rust and thermal issue, if got any clean connection strips then reconnect. my 1+3t never got hot from any side ever.
Hayatzada said:
as far as my idea is concern you have another 1+3/t, to confirm battery issue swap your motherboard or battery with the other one, it'll confirm the battery. other than battery issue check lose connections/rust and thermal issue, if got any clean connection strips then reconnect. my 1+3t never got hot from any side ever.
Click to expand...
Click to collapse
Yes i'll do that, i just need to find the famous torx t2 to open it.
Thanks for your help!
Blubster said:
Yes i'll do that, i just need to find the famous torx t2 to open it.
Thanks for your help!
Click to expand...
Click to collapse
welcome