Related
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Sent from my SGH-T989 using Tapatalk 2
LuniZ916 said:
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Click to expand...
Click to collapse
Same thing happen to me the dreaded QHSUSB error when I bricked my exhibit2. I know how you feel.
Sent from my SGH-T989 using XDA Premium App
Lol. I bricked mt very first phone (the T989) the very first day i got it. I got it replaced for free with that 14 day gap thing that Tmo has. Got lucky. Ive never had a bad flash since.
Sent from my SGH-T989 using xda app-developers app
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Stupid kies mini hard bricked my trusty vibrant... Luckily, t-mobile replaced it for free, but it was the horrible exhibit 1.
supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Yeah most people went through regular warranty exchanges, but from what the OP was explaining he's a very honest person and would have said that he rooted the phone therefore he would not be able to exchange it.
That's good that he's honest, but it would have been a lot easier to just do that and get the phone next day because TMobile is just going to send that phone back to Samsung and they'll do the exact same thing they're doing to his phone now
Sent from my SGH-T989 using xda app-developers app
This sounds exactly like something I would! Especially buying parts thinking I could fix it!!
I feel so at home on xda!!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
U could a saved a ton of time and money by just saying ur phone stopped working. Cuz technically it did
Sent from my SGH-T989 using xda app-developers app
LOOOOOOL this made my day^^
I have my phone till two years now and i bricked it once by disconnecting by mistake while unlocking bootloader (yes i fell with my phone in the hand and lukily it only disconnected and didnt pull my laptop with it.
I had it fixed in a half hour^^
Greets
Sent from my Xperia X10 using xda app-developers app
Good to know thanks
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
My very first device was the Mytouch 3G on T-Mobile. Back then, it was maybe the 2nd Android phone to have even existed at that point.
Me, never being satisfied with anything stock and coming from a heavily modified blackberry, wanted to tweak the hell out of it.
Back then, it took a LOT more to root and flash, ESPECIALLY HTC Devices. There were no custom tools yet to root, and the only easy part was using CWM. You HAD to use adb commands to exploit to get root and even get CWM on the device at that point, but only AFTER downgrading it back to Android 1.5, but after that it was easy.
(I couldn't believe how fast and easy it was to root and flash on the T989 after having HTC devices up until last year)
Anyways, I somehow managed to get it CWM to boot (you had to boot into normal recovery after replacing update.zip with a CWM zip, and then flash the new update.zip file back then) and went to flash a ROM, and instead I flashed a zip, but the wrong ROM was uploaded by the OP, and what I had flashed as for the G1. It was literally only uploaded for all of maybe 2 minutes before he pulled the post down and uploaded the correct version.
I was the ONLY one who downloaded and flashed it within that 2 minute window.
Needless to say, I hated my life.
Now the funny part:
I was so paranoid back then about not letting T-Mobile know that I was rooted, that I literally bought a BRAND NEW Mytouch 3G (because you couldn't even find broken ones on ebay yet) and sold the broken one, which I bought the day before mind you, for $20. I wish I would have known that, back then, there were no counters on the MT3G. T-Mobile would have never known as it wouldn't boot.
:crying:
Flash forward to today, and IDGAF.
Hi guys. Haven't been here in a while. My daughter is now saying her cap. glide is randomly shutting itself down- not related to low battery. It happened 3 times in one week. When she powered it up the battery was fine. The phone is about 9 months old. I think it has a 12 month warranty. At least on the samsung site it says 12 months. We got it from ATT with contract renewal.
I read that the regular Captivate had this problem. Did it flow over into the glide? Haven't found anything about it. I assume ATT will replace with a refurb if anything.
sashusmom said:
Hi guys. Haven't been here in a while. My daughter is now saying her cap. glide is randomly shutting itself down- not related to low battery. It happened 3 times in one week. When she powered it up the battery was fine. The phone is about 9 months old. I think it has a 12 month warranty. At least on the samsung site it says 12 months. We got it from ATT with contract renewal.
I read that the regular Captivate had this problem. Did it flow over into the glide? Haven't found anything about it. I assume ATT will replace with a refurb if anything.
Click to expand...
Click to collapse
I use mine pretty heavy and havent noticed any problem i assume that you are running the phone completely stock and if so i would suggest that you download samsung kies from samsungs site and run it then plug the phone in and it will ask you if you want to update the phone it may run better on the newest firmware that there is other wise i would download avgs free antivirus app and run it to see if there are any apps that might be to blame i would post links but to avoid spam i am not allowed
og anarchy said:
I use mine pretty heavy and havent noticed any problem i assume that you are running the phone completely stock and if so i would suggest that you download samsung kies from samsungs site and run it then plug the phone in and it will ask you if you want to update the phone it may run better on the newest firmware that there is other wise i would download avgs free antivirus app and run it to see if there are any apps that might be to blame i would post links but to avoid spam i am not allowed
Click to expand...
Click to collapse
Thanks for your response. Yes, it is stock rom, but I have it rooted with CWM recovery on it. I don't think kies can update it due to CWM. And it's in another state. LOL. But good to know you don't have the issue. As for running antivirus, my daughter does not even know what that is- she barely runs it on her computer. If I ever get my hands on it I will try your suggestion for AV.
Could be a battery issue... mine did the same, and when I took out the battery it was slightly swollen.
Thanks for that. I'll have her check it out.:fingers-crossed:
Interested in your solution
My wife's Captivate Glide just started having random shutdowns last week. I came over looking for a "return to stock" thread hoping that putting a new OS might help when I saw this thread. I've been reading xda on the GalaxyII boards since getting mine last year so have some familarity with xda. Wife prefers to not update OS so I want to avoid ICS. She had AVG installed and I added Lookout to scan with it also and can't seem to find an issue with those. The problem for her mainly manifest itself when she has the internet turned on. The phone will basically act like the battery is critical and do a shutdown even if it is over 50 percent. power up with the cord in and it still shows good charge. If I find something that works I'll post it here also.
I have random shutdowns/boot cycles too. I've narrowed it to a hardware issue. I was running rooted stock rom, but also ran liquidsmooth and now on aokp rom, and its still happens.
I posted a topic a couple weeks ago, asked if anyone has any experience replacing the power button..its not that it sticks, but if pressed the wrong way in the wrong spot, the phone goes into endless boot mode, with the samsung logo up for about three sec, then black, then samsung logo, then black.
The timing is rarely the same. There's no debris or gunk. Its not battery. Its not overclock issue. Its something to do with the phyical power button.
Can I diasble power button using key remapping?
Sent from my SGH-I927 using xda premium
Having the same problems with my Glide, and I really do think it's a hardware issue since my battery looks fine. After reading many threads here and elsewhere, I'm resigned to the fact that it can't be fixed, but more suggestions are welcome.
My daughter has had this phone for almost a year and it just started happening to hers. She is very hard on her phone. 5000 texts/month with alot of drops. She just might have abused it to near death. lol.
Random Boot
Hello guys;
I think I'm having same or very similar issue.
My phone is randomly shutting down; some times is in cyclic restarts.
Did you guys came up with a solution to this problem?
Thanks
sashusmom said:
My daughter has had this phone for almost a year and it just started happening to hers. She is very hard on her phone. 5000 texts/month with alot of drops. She just might have abused it to near death. lol.
Click to expand...
Click to collapse
5000 texts per month?
Does your daughter know how to speak or is she only familiar with written language?
If you're on a stock rom, it's almost certainly a bad battery.
Battery voltage will drop when it's hot or if it's damaged. When you turn it back on, the phone says you still have plenty of power left.
What the phone is really doing is making a guess about how much battery life it has left.
It knows the voltage. Now, if you know the voltage a battery is producing with no load, you can get sort of an idea of how much more life you can get out of it. The phone keeps track of this (roughly) and tries to guess. It's also not going to let the battery drop too far down below 3.6 volts, it will shut it off for safety, because if you truly completely discharge a lithium battery, you can't charge it. (there are tricks to get them going again, but it's bad for them.)
And a damaged battery can have plenty of volts, but once you put it under load it will drop sharply. The phone will power down to protect the battery, or it just won't be able to stay on any longer.
Anyway, pull your battery. Make sure it isn't bulging. Pick up a spare off of ebay for $10 and see if it is better.
Or if it's under warranty, just take it in.
davidpartay said:
5000 texts per month?
Does your daughter know how to speak or is she only familiar with written language?
Click to expand...
Click to collapse
Lol.... Sometimes it's only 3 thousand. But you are right. The art of communication is being lost on this generation of kids who rely on computers, tablets, and smartphones. Instead of calling, they text about everything.
My daughter is graduating:victory: with a double major- Theatre and speech (performance) so we know she can talk and sing and psychology with ambitions to get a masters in dance therapy to work with autistic kids.... If broadway does not work out Any directors or producers out there need new talent?? :fingers-crossed:
epsalmond said:
If you're on a stock rom, it's almost certainly a bad battery.
Battery voltage will drop when it's hot or if it's damaged. When you turn it back on, the phone says you still have plenty of power left.
What the phone is really doing is making a guess about how much battery life it has left.
It knows the voltage. Now, if you know the voltage a battery is producing with no load, you can get sort of an idea of how much more life you can get out of it. The phone keeps track of this (roughly) and tries to guess. It's also not going to let the battery drop too far down below 3.6 volts, it will shut it off for safety, because if you truly completely discharge a lithium battery, you can't charge it. (there are tricks to get them going again, but it's bad for them.)
And a damaged battery can have plenty of volts, but once you put it under load it will drop sharply. The phone will power down to protect the battery, or it just won't be able to stay on any longer.
Anyway, pull your battery. Make sure it isn't bulging. Pick up a spare off of ebay for $10 and see if it is better.
Or if it's under warranty, just take it in.
Click to expand...
Click to collapse
Very informative. Thank you. She did pull the battery and it was fine. It is about a year old. I got her 2 replacements and she just doesn't use them. I will suggest that she switches to a new one- although they are almost a year old too, but unused- I charged them up once before i gave them to her.
phone saga continues!!!
:silly: Well, my daughter being sooooo poor that she couldn't buy herself a BOX of tissues(cough-cough), she was pulling toilet paper from the dorm bathroom and plop! OOps!! Her phone fell into the drink! (toilet bowl!!)
She knew enough to pull the battery and used a blowdryer to start the dry out process, and put it into a bag of rice. Didn't leave it in long enough and tried to power on- did a little dance, and it died. I thought she fried it, but she put it in rice again- battery pulled and slid in the open position.
2 days later she called us on it- (today) and it seems to be working!!!:victory:
So, Rice saved the day again! :silly::good::highfive::fingers-crossed:
We'll see how long it lasts. I bought a cheap go phone last nite on att for $21 as a temporary replacement. Maybe it won't be needed.
Help!!
Hard to believe my glide is begining to give problems. After flashing a stock kernel on spike55 jb 4.2 rom,i started getting random app crashings. So i sought to revert by flashing back the original jb ROM,but it got worse. Now i was uable to get network and my baseband version displayed unknown also i had random reboots.
At this junction, i realised i had to revert to stock. So i got a stock ICS rom from sammobile, flashed it via odin and whala! Problem seemed solved. So i flashed CWMR and reflashed jb 4.2.
Afterward, all seemed well not until the random reboots came back. So here i was thinking about my phone being tired of all the flashing and wanting to be on stock. I went back to stock, but the random reboots still lingers.
Though i have a feeling the problem is with my power rocker cos only a little tap pops up the power menu.
At this junction, i dunno what to do. I'll be very grateful if i can get any real assistance from anyone. Thanks a bunch in anticipation.
So I thought I'd post again. Daughter home for good. Started complaining about her battery again. I found her 2 spare batteries that were never used. Had her make the switch.
Then I looked at the removed battery. It was slightly swollen. You had to look straight down to tell. Looking at it flat, it seemed to be fine. But put it on end and it had a slight bulge. So it was a battery going bad. We caught it before the phone was damaged.
Sent from my Nexus 7 using Tapatalk 4
Hello!!! Back again My daughter ran on macadam and her unprotected cap. glide plopped out of her sweatshirt pocket and hit hard. A small hairline crack in the screen, but it pretty much killed the digital panel. She had it for 18 months and for her, that's a record. But she loved the phone.
We just got a new one unlocked one off amazon for $138. No contract renewal for her.
If anyone is still reading this thread, her OS is 2.3.5 or 6. Is it worth updating to ics? We don't have kies installed so it will be a job to get everything installed, get drivers working, etc. She will be happy with GB. Last time I made the change to swap external and internal sd cards and she had no problems.
So is ICS worth the effort? Battery life? Can the sd swap trick work? Any advice will be appreciated. Presently it is new and stock.
sashusmom said:
So is ICS worth the effort?
Click to expand...
Click to collapse
..it might even have come with ICS, the UI differences to GB are very slim.. Can't say more because stock roms are far inferior to the beast called P.A.C.man ROM :laugh: :good:
Really depends if she is tech savy and will explore the depths of customizability and usage... If so, http://pacman.basketbuild.com/index.php?dir=main/i927/nightly/ is the next place to go
Nightly builds 'been broken for 10 days now but should be fixed soon by awesome @kick buttowski :good:
And on a rooted phone, Titanium Backup can import/export SMSs and contacts supposedly even over to a different rom. (Still struggling a bit getting all my contacts ported from the sony xperia system, but..)
Oh by the way, one of them plastic hard cases is about 5$ on the bay
...It's not water proof though
eMPee584 said:
..it might even have come with ICS, the UI differences to GB are very slim.. Can't say more because stock roms are far inferior to the beast called P.A.C.man ROM :laugh: :good:
Really depends if she is tech savy and will explore the depths of customizability and usage... If so, http://pacman.basketbuild.com/index.php?dir=main/i927/nightly/ is the next place to go
Nightly builds 'been broken for 10 days now but should be fixed soon by awesome @kick buttowski :good:
And on a rooted phone, Titanium Backup can import/export SMSs and contacts supposedly even over to a different rom. (Still struggling a bit getting all my contacts ported from the sony xperia system, but..)
Oh by the way, one of them plastic hard cases is about 5$ on the bay
...It's not water proof though
Click to expand...
Click to collapse
Nice to see people are still using this phone. As far as the case- I must have bought 5 of them for her. She didn't want them on her phone. Now that she paid for her own replacement, she may rethink that one! lol. She is not tech saavy at all, so custom builds are not her thing. I didn't even do the mods on this phone that I did on her original. Thanks for your input. OH, it's still GB.
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app
In not an expert at unlocking phones or anything but I think my phone has the bootloader issue. At times it freeze and then either stays frozen for a bit 5 - 10 min or so it then reboots itself, it I'll rest the phone to get it unfrozen. It is doing it multiple times a day and becoming more and more frequent.
Does this mean that I'm getting closer and closer to complete failure, and I need to back up everything in the phone and get replacement.
The warranty from Google is over. Bought October 2015. I may have extended warranty through my credit card. What would all of the experts on this suggest?
I would love any and all help and suggestions.
Sent from my Nexus 5X using Tapatalk
Well Surprise surprise. Google said they would replace. I'll send it back and set of the phone they send didn't have the same problem. Can I get a wahoo! Happy dance.
Sent from my Nexus 5X using Tapatalk
If you send it for repair, will your personal data get wiped or do they send it back all intact?
KTroopA said:
If you send it for repair, will your personal data get wiped or do they send it back all intact?
Click to expand...
Click to collapse
They will probably replace motherboard, so internal storage will not be the same.
gingus7 said:
In not an expert at unlocking phones or anything but I think my phone has the bootloader issue. At times it freeze and then either stays frozen for a bit 5 - 10 min or so it then reboots itself, it I'll rest the phone to get it unfrozen. It is doing it multiple times a day and becoming more and more frequent.
Does this mean that I'm getting closer and closer to complete failure, and I need to back up everything in the phone and get replacement.
The warranty from Google is over. Bought October 2015. I may have extended warranty through my credit card. What would all of the experts on this suggest?
I would love any and all help and suggestions.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I had the same issue, though my phone is dead. I had actually gotten it to where I could ADB the firmware, and it eventually got pretty far into the 4 colored circles until it started bootlooping. Now, it is completely dead.
I had just backed up my photos, but I did lose other app data that I had not backed up recently. Not a whole lot since most apps now backup online these days. But if I get a replacement LG phone, I will always backup on a schedule.
There was an XDA article where LG has a class action against it for the G4 for using solder that doesn't hold up to the heat or heating/cooling cycles. The 5X was added to that lawsuit as well as other phones in April.
This is the first phone that has actually died on me since I dropped a Nokia 8320 into water. I even have my Motorola V600, Razr, BB 8320, and more recent phones that all still work. It amazes me that LG hasn't figured out how to fix this problem since it seems to affect a lot of their models.
Been using my 5x for 18 months or so, standard Android 7.1, etc. Pulled it out of my pocket a couple hours ago and it is totally dead! Had about 75% battery when last used.
I'm unable to get any response out of it, no charging indicator, power + volume keys doesn't work. Just totally dead.
Any ideas? Will Google replace it for a fee? I'm on a trip for another few days and will really miss it -- hope I don't need it for something important.
Sent from my SM-T700 using Tapatalk
Same happened to me while ago. But still no luck with this. To fix I believe I need access to boot menu which I couldn't
Update: For some reason, I was able to get into the initial screen that you get by holding power and volume down. However, none of the three options work from there. All I get is a Google logo for several second and return to darkness.
Sent from my SM-T700 using Tapatalk
You can read about Nexus 5X bootloop on this forum. Its a hardware problem.
Sent from my Nexus 5X using Tapatalk
shut_down said:
You can read about Nexus 5X bootloop on this forum. Its a hardware problem.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Aargh! I was afraid that might be the problem.
Sent from my SM-T700 using Tapatalk
rochrunner said:
Aargh! I was afraid that might be the problem.
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
my nexus 5x is going to die . i opdate it too android 8 and work with telegram . then it turn off and is not turn on . after 1 day when press power key the notification light is turn on. i cant go to recovery or downloaD mod . please help me
Mine did this exact thing and it was the bootloop problem, though it didn't bootloop. It acted like yours did.
Your best hope if you're going on a trip soon, is try the method that turns off the big cores. If you don't have an unlocked bootloader, try putting it in the freezer or an ice bath, and maybe it'll boot long enough to unlock the bootloader. Mine would get into recovery using that method so I could wipe the cache and adb the OTA. It also tried to boot longer, but never would boot.
All the phones act differently and you may get lucky.
Mine never booted until I used a hairdryer on the motherboard. But it immediately froze after booting. Then actually did start bootlooping. Only using a heatgun got it to boot where I could pull my data off of it. But it died relatively quickly. Then I got it to act normal for 9 hours after using a heatgun at higher temp. After that I could heatgun it again and get it to boot, but it would very quickly die again. The fix that turns off the big cores was not out then, so I don't know if it would have fixed it.
Voicebox said:
Mine did this exact thing and it was the bootloop problem, though it didn't bootloop. It acted like yours did.
Your best hope if you're going on a trip soon, is try the method that turns off the big cores. If you don't have an unlocked bootloader, try putting it in the freezer or an ice bath, and maybe it'll boot long enough to unlock the bootloader. Mine would get into recovery using that method so I could wipe the cache and adb the OTA. It also tried to boot longer, but never would boot.
All the phones act differently and you may get lucky.
Mine never booted until I used a hairdryer on the motherboard. But it immediately froze after booting. Then actually did start bootlooping. Only using a heatgun got it to boot where I could pull my data off of it. But it died relatively quickly. Then I got it to act normal for 9 hours after using a heatgun at higher temp. After that I could heatgun it again and get it to boot, but it would very quickly die again. The fix that turns off the big cores was not out then, so I don't know if it would have fixed it.
Click to expand...
Click to collapse
I was on a trip when it happened, but miraculously survived without access to Google Maps, SMS, FB, etc. Returning home, I was very impressed with Google support. I put in for a callback on my home phone, received a call in less than a minute, and they are replacing my phone (with a refurb) free as a "warranty extension" (phone about 18 mos. old). So I should be back in business in a couple days. In the meantime, I'm finding it kinda liberating to not have to be carrying the phone around, remembering to put it on the charger, etc.
rochrunner said:
I was on a trip when it happened, but miraculously survived without access to Google Maps, SMS, FB, etc. Returning home, I was very impressed with Google support. I put in for a callback on my home phone, received a call in less than a minute, and they are replacing my phone (with a refurb) free as a "warranty extension" (phone about 18 mos. old). So I should be back in business in a couple days. In the meantime, I'm finding it kinda liberating to not have to be carrying the phone around, remembering to put it on the charger, etc.
Click to expand...
Click to collapse
Yeah, they replaced mine at 14 or 15 months in. By then it was such an issue that the tech guy didn't even bother making me do all the troubleshooting steps before he said he was handing me off to the guy to set up the replacement.
Mine just did this to me. It's my second 5X and this time nearly 6 months elapsed before it died so I couldn't use the Amazon return process (my first one started bootlooping in less than 2 weeks).
Had the phone 100% charged, slipped it into my pocket, took it out during lunch and it refused to boot. Can't even get into recovery.
I'll put it into my freezer tonight to see if I can at least get it to boot long enough for me to retrieve a few photos that I hadn't backed up in the cloud.
I wonder if my frequent use of the phone as a car GPS contributed to this. My friend's 5X has not crapped out on him since he bought it in 2015...
Google Pixel, here I come!
Edit: Freezer worked, and in fact the phone is still alive, but I'm not cancelling my Pixel order regardless
machoman1337 said:
Mine just did this to me. It's my second 5X and this time nearly 6 months elapsed before it died so I couldn't use the Amazon return process (my first one started bootlooping in less than 2 weeks).
Had the phone 100% charged, slipped it into my pocket, took it out during lunch and it refused to boot. Can't even get into recovery.
I'll put it into my freezer tonight to see if I can at least get it to boot long enough for me to retrieve a few photos that I hadn't backed up in the cloud.
I wonder if my frequent use of the phone as a car GPS contributed to this. My friend's 5X has not crapped out on him since he bought it in 2015...
Google Pixel, here I come!
Edit: Freezer worked, and in fact the phone is still alive, but I'm not cancelling my Pixel order regardless
Click to expand...
Click to collapse
hi, i got the dead nexus5x too
How long you putted in the freezer?
After freezing event, phones works as usual? or it worked a few ours, than dead?
Thank you.
maltinbay said:
hi, i got the dead nexus5x too
How long you putted in the freezer?
After freezing event, phones works as usual? or it worked a few ours, than dead?
Thank you.
Click to expand...
Click to collapse
1 hour. It works as usual. Hasn't died since I took it out, but I'm not getting my hopes up.
hey guys - I'm troubleshooting this device for a lady friend - this exact thing just happened to her haha she's running all stock everything, I was able to get to the default bootloader/choose recovery etc screen but when I selected recovery, like you all, it just bootlooped a couple times, then played the entire boot animation, then died again...
if I do this freezer thing, can the wug's toolkit aid me in flashing some custom stuff to make it a little easier to mess around with? i.e. put on kernel adiutor and turn off the big cores like someone mentioned?? anyone know the thread where I could root purely from bootloader screen + computer? the toolkit seems to require normal access to the OS to function, right?
thanks in advance
machoman1337 said:
Mine just did this to me. It's my second 5X and this time nearly 6 months elapsed before it died so I couldn't use the Amazon return process (my first one started bootlooping in less than 2 weeks).
Had the phone 100% charged, slipped it into my pocket, took it out during lunch and it refused to boot. Can't even get into recovery.
I'll put it into my freezer tonight to see if I can at least get it to boot long enough for me to retrieve a few photos that I hadn't backed up in the cloud.
I wonder if my frequent use of the phone as a car GPS contributed to this. My friend's 5X has not crapped out on him since he bought it in 2015...
Google Pixel, here I come!
Edit: Freezer worked, and in fact the phone is still alive, but I'm not cancelling my Pixel order regardless
Click to expand...
Click to collapse
WTF!!!!!!! My ****ing dad's nexus died! WTFFFFFFFFFFFFFFFF!!!!! **** YOUR UGLY BODY!!!
purplepenguin said:
hey guys - I'm troubleshooting this device for a lady friend - this exact thing just happened to her haha she's running all stock everything, I was able to get to the default bootloader/choose recovery etc screen but when I selected recovery, like you all, it just bootlooped a couple times, then played the entire boot animation, then died again...
if I do this freezer thing, can the wug's toolkit aid me in flashing some custom stuff to make it a little easier to mess around with? i.e. put on kernel adiutor and turn off the big cores like someone mentioned?? anyone know the thread where I could root purely from bootloader screen + computer? the toolkit seems to require normal access to the OS to function, right?
thanks in advance
Click to expand...
Click to collapse
I believe you should be able to get the phone to stay alive long enough to do everything you mentioned, after a freezer treatment.
In my case, the phone has actually stayed alive continuously after the freezer treatment but I'm not getting my hopes up.
Alex Wood said:
WTF!!!!!!! My ****ing dad's nexus died! WTFFFFFFFFFFFFFFFF!!!!! **** YOUR UGLY BODY!!!
Click to expand...
Click to collapse
lolwut?
Same things happened to my phone...it was 50% charged and all of sudden... The phone went off...still trying to find out....
Just happened to me.
Phone died while in standby on my desk, black screen and no luck booting or anything. I was assuming the worst, it's been only 1 year since i bought it.
I dig out my screwdrivers kit, removed the back cover and disconnected the battery. After a few minutes i reconnected it and the phone was alive and kickin' again. No bootlop whatsoever.
Now it's working fine, i hope it keep doing that for long time. @machoman1337 yours is still fine or died again?
Thanks
.bucch said:
Just happened to me.
Phone died while in standby on my desk, black screen and no luck booting or anything. I was assuming the worst, it's been only 1 year since i bought it.
I dig out my screwdrivers kit, removed the back cover and disconnected the battery. After a few minutes i reconnected it and the phone was alive and kickin' again. No bootlop whatsoever.
Now it's working fine, i hope it keep doing that for long time. @machoman1337 yours is still fine or died again?
Thanks
Click to expand...
Click to collapse
I bought a Pixel so I haven't tested my 5X since my black-screen happened. It's still in my drawer.
machoman1337 said:
I bought a Pixel so I haven't tested my 5X since my black-screen happened. It's still in my drawer.
Click to expand...
Click to collapse
Oh, I see. Thanks anyway.
I'll see for myself.
there's a nexus 5x extinction in progress
there we'll be no nexus 5x alive in a while
having nothing but rubbish in your hand after 2-3 years is not a pleasure and this is a shame for lg