Related
I just got my E4GT a couple weeks ago...all of a sudden, it started going to hell. The touchscreen stopped working pretty much completely, it won't charge and won't acknowledge the USB cable at all, so I can't connect to Odin or flash a stock firmware, or use a usb jig.
It's a hardware issue, I know but can I still take it in? What are the chances they'll say I can't return it because I rooted it? All of the employees at my sprint store seem pretty clueless...is it worth a try just to see if they can fix/replace it?
I really don't want to pay 100 bucks for a new phone just because I rooted it -__-
Also, my parents are REALLY, REALLY pissed.
Thanks, for the love of god, help me.
I have to go on a trip in 3 days and I NEED my phone.
Isnt this same post in General?
One post in one section is all you really need...
Sent from my SPH-D710 using xda premium
First you say it's a hardware issue then you blame root. You should just take it back for a replacement. And never root again unless you know what you're doing.
Sent from the future.
I've posted this message before in the og epic forum: my grandfather always told me, of you can't afford to replace it, you have no business messing with it. Don't get started modding unless you are willing to buy another phone.
And I agree with the other guy, its either your flash issue or hardware. Not both.
Sent from my SPH-D710 using XDA App
Your screwed
Sent from my SPH-D710 using XDA App
I saw a video that someone posted here today. Let me try and find it, it's hella funny and it reminds me of you.
Here you go
http://forum.xda-developers.com/showthread.php?p=19597685#post19597685
If the battery is dead resulting in a phone that won't power on... there is no solution that can be offered here besides finding a cable that works to charge it.
If you bought this phone "a couple weeks ago" I'm going to bet we are past your window for returns, and if you modified your phone and don't know how to fix it, or can't do a simple troubleshoot of the USB cable/port... yes, you are completely screwed for the timeline you have setup.
Bring it to a sprint store, ask if you can test to see if their charger will charge your phone. If it does, its the cable and you can go buy a new one (better one) and all the other problems are probably moot.
If it doesn't charge, then its hardware issue on your phone (or an issue with something you did that we cannot reverse without the phone gaining power plus being able to be in download mode,) and you already know what I'm going to say.
SocialReject said:
First you say it's a hardware issue then you blame root. You should just take it back for a replacement. And never root again unless you know what you're doing.
Sent from the future.
Click to expand...
Click to collapse
This. Don't root your phone if you don't have the means or the willingness to deal with it if you bust it!
Hi, when i open my gamepad slightly my screen will flash black, and if i hold it in a certain positionbit will stay black until moved.
This also happens sometimes when picking up my phone
Is it a loose cable or something?
Should i get it replaced?
Rooted stock R800i, .42
Thanks
Probably the ribbon cable inside the slider. It's a known defective part.
Sent from a Galaxy far, far away..
So i could claim it on my warranty?
I got this problem too. But mine worse, sometimes when I wanna type a message the screen goes black, or the screen's light go like disco light, keep blinking at the home page and camera. I sent to Sony Centre to claim warranty but after few days they returned me and told me it was a software problem. Could this be kernel problem?
Yeah, sometimes just touching the screen can do it
I want to unroot before i cant see anything haha
Ive noticed that its just the backlight that goes off, if i make it go black and look at the screen in light i can still see the things there
Im going to request a replacement regardless, starting to annoy me
I tried to reinstall stock firmware but no use. Still the same. I'm gonna tear everything apart and take a look at the ribbon.
Sent from my R800i using xda premium
jeff7424 said:
I tried to reinstall stock firmware but no use. Still the same. I'm gonna tear everything apart and take a look at the ribbon.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
DO NOT I repeat, DO NOT take it apart!!
Once you do that your warranty is void permanently and no way to hide it! I can guarantee it's not your software. Revert it to absolute perfect stock and show them it still happens. I'm positive it's the hardware, NOT software.
If they don't wanna fix it after factory restoring, threaten to call head office about it because you already know it's hardware error and they are refusing.
And also mention that many people on the internet are aware that the slider cable is faulty, many have replaced it and fixed the same problem you have.
I'm thinking of mailing them, and requesting they have a recall because more and more people are having the same problem.
Sent from a Galaxy far, far away..
Ok, the screen only flashes black on SYSTEM APPS. The installed apps dont have this issue
Seems to have happened after i rooted
Any new ideas?
Okay. Thanks captain. I will follow your orders.
Ok, so ive tried to claim on my warrenty. They said they were gunna send a packet out to return the phone for repair. This was a few weeks ago. Within this time i have called them up 3 extra times stating i havnt recieved the pack.
Is this easy enough to fix myself as im bored of waiting for them and im doubting im ever going to recieve any repair
Thanks
Sent from my R800i using XDA
Have you tried flashing a fresh stock firmware?
Sent from a Galaxy far, far away
Yeah, used se repair thing
Problem still there
Sent from my R800i using XDA
http://www.youtube.com/watch?v=fQXH5GAf9UA&feature=youtube_gdata_player
Thats a video of my problem
Notice when it goes closer, when the screen goes black you can still see the homescreen
Sent from my R800i using XDA
Hey E4GT peeps;
So listen to this quick little story, and then let me know if I'm correct in my assumption:
I used to have JellyBean on my phone, not CM10, but Sbrissen's amazing ROM... well I decided to go back to stock everything and upgrade to ICS that way/etc... don't ask me why 'cause I don't know yet. lol. Well I did it, and I believe I used the One-Touch-Stock option to do it all. Well I went back to stock, everything was kind of weird... Android system felt laggy, and crashed, I was on ICS at that point btw, it was Stock FF18 I believe. Well anyways, I tried to do a few things, and suddenly things got worse... my battery stopped charging up completely... I would get the "Voltage too high" bs @ around 23% battery life. Well suddenly tonight the phone just shut off... and won't charge anymore. It won't turn on, and when I plug it into my PC or the wall charger, it still does nothing. All I get is a soft blinking blue light... not a solid red light (aka charging light)... well I tried to just let it sit on the charger for a few hours, and I left it off the charger for a few hours and still no success.
So I'm wondering... Do you think this is a Brick?
Do this you should be good.
http://www.youtube.com/watch?v=_vmEmheJnyg&feature=youtube_gdata_player
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 02:29 AM ---------- Previous post was at 02:26 AM ----------
Okay I didn't finish reading to the end of your post I'm pretty sure your phone is a brick but someone more qualified should chime in. I believe there might be a way to fix it but I'm not sure how or what its called. I'm assuming you pulled the battery and have tried to boot into recovery or download mode?
Sent from my Nexus 7 using xda app-developers app
GiantJay said:
Do this you should be good.
http://www.youtube.com/watch?v=_vmEmheJnyg&feature=youtube_gdata_player
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 02:29 AM ---------- Previous post was at 02:26 AM ----------
Okay I didn't finish reading to the end of your post I'm pretty sure your phone is a brick but someone more qualified should chime in. I believe there might be a way to fix it but I'm not sure how or what its called. I'm assuming you pulled the battery and have tried to boot into recovery or download mode?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I pulled battery, tried to boot in both recovery/download mode... Right now I can't even get it to turn on. Occasionally I get the blue light that flashes every like 4 seconds. Phone doesn't show up in Odin at all.
Are you sure your battery is good? Because nothing that you've posted that you did should have resulted in a brick... I'm not very familiar with the "voltage too high" issue, I know there are threads about it though, you may want to take a look at the solutions offered there as your issue seems to be much more related to power than any traditional cause of a brick...
Sent from my SPH-D710 using Tapatalk 2
cp320703 said:
Are you sure your battery is good? Because nothing that you've posted that you did should have resulted in a brick... I'm not very familiar with the "voltage too high" issue, I know there are threads about it though, you may want to take a look at the solutions offered there as your issue seems to be much more related to power than any traditional cause of a brick...
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
That's actually something I thought might be the issue. I'm going to the Sprint Store in like 5-6 hours and we'll see what the real issue is. I only jhope for a brick so that way they can replace my device, since I've dropped this one a few too many times and you can see the wear and tear.
Doesn't sound like a brick to me... Probably a battery as stated.
Sent from my SAMSUNG-SGH-I717 using xda premium
jasKaos said:
That's actually something I thought might be the issue. I'm going to the Sprint Store in like 5-6 hours and we'll see what the real issue is. I only jhope for a brick so that way they can replace my device, since I've dropped this one a few too many times and you can see the wear and tear.
Click to expand...
Click to collapse
My guess is either bootloader or something physically wrong with the phone. Anything happen to it lately - get wet, dropped, etc?
Flashing blue is the battery. I've had this happen 3 times now.
Yeah solid blue is the brick. Blinking blue is likely the battery
sent from my BAD A$$ Epic touch
Sounds like the charging/communication port is nit reading the charger. Mine has been acting weird lately. Sometimes I have to plug it in, unplug it a few times. After a few times I get it to read and it starts charging. My phone was a refurbished replacement.
Sent from my SPH-D710 using Tapatalk 2
Yea not a brick.. What ur saying sounds like the battery.. Solid blue is a brick.. Could also b the bootloader like someone suggested almost like stuck in a bootloop but instead of showing splash it just keeps trying to reboot itself
Sent from my SPH-D710 using xda app-developers app
Thanks for the responses, it's currently sitting at the Sprint Store for repairs... I'm actually going to leave to go get it in like 40 minutes... If it's the battery, that's fine, cause they can easily get it working fast, which is good, because I need the phone for business/work.
Hate to sound negative, but mine was doing pretty much the same thing and it was definitely bricked. I took it to the sprint store and the tech scratched his head and said he's never seen one not be able to get into download mode. He then replaced the screen. Obviously didn't help. Mine had a solid blue light for a while, then as the battery wore down, the blue light flashed, but very very dim. I was hoping it was the battery too, but the rep at the front counter switched the battery for me before it even went to the tech. Anyway, good luck! Hopefully you're situation turn out better than mine!
mine did the same thing while I was on vacation so I wasn't flashing it was the charging port. Try bending the little port down a little
Sent from my SPH-D710 using Tapatalk 2
So I am back from the Sprint Store (and feeding my son), and basically it was the charging port... they said it has corrosion on it... from moisture... and I had to file a claim through asurion. How lame. The guy at the store was pretty dumb as he had no clue what was really wrong with it and couldn't even explain basic things... none the less, the tech guy assured me it was just the charging port itself, one of the prongs on it were damaged beyond repair, but since it was 'corrosion' they can't do anything about it. I need to shell out $100 to get a new one sent now.
Woot. At least I will be able to take better care of my replacement and not get it roughed up like this one, haha.
jasKaos said:
So I am back from the Sprint Store (and feeding my son), and basically it was the charging port... they said it has corrosion on it... from moisture... and I had to file a claim through asurion. How lame. The guy at the store was pretty dumb as he had no clue what was really wrong with it and couldn't even explain basic things... none the less, the tech guy assured me it was just the charging port itself, one of the prongs on it were damaged beyond repair, but since it was 'corrosion' they can't do anything about it. I need to shell out $100 to get a new one sent now.
Woot. At least I will be able to take better care of my replacement and not get it roughed up like this one, haha.
Click to expand...
Click to collapse
Take that to another store. That is some BS. I know sprint techs can replace the port, well at least on my OG EVO they could.
Sent from my SPH-D710 using xda premium
locoboi187 said:
Take that to another store. That is some BS. I know sprint techs can replace the port, well at least on my OG EVO they could.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Man, I've never had a sprint tech fix anything for me. The most I've gotten from them is the card for how to get a replacement phone.
That's why I don't brick phones. The only time I go see Sprint is when something physical happens, even then, they don't fix it.
Sent from my SPH-D710 using xda app-developers app
jasKaos said:
So I am back from the Sprint Store (and feeding my son), and basically it was the charging port... they said it has corrosion on it... from moisture... and I had to file a claim through asurion. How lame. The guy at the store was pretty dumb as he had no clue what was really wrong with it and couldn't even explain basic things... none the less, the tech guy assured me it was just the charging port itself, one of the prongs on it were damaged beyond repair, but since it was 'corrosion' they can't do anything about it. I need to shell out $100 to get a new one sent now.
Woot. At least I will be able to take better care of my replacement and not get it roughed up like this one, haha.
Click to expand...
Click to collapse
That's funny... When I actually did brick my phone the sprint tech said exactly the same thing. It's funny because I also left the store while they were going to do the repair. I was also told to pay $100 dollars because of "corrosion" on the board where the charging port is.... coincidence? Did you happen to go to the store in Mesa, AZ near Fiesta mall?
I don't see how "corrosion" on the USB port is preventing a charge, a good cleaning should fix that, I mean its not like a whole pin would have spontaneously rusted off. I also would suggest taking it to another store
Sent from my SPH-D710 using Tapatalk 2
i had a problem with the charging port on mine, and they replaced it free of charge, if they tried to charge me 100 i would be pissed
My back cover keeps popping off near the volume button. I can push it back in but it seems like it wants to keep popping off. Only in that one area, no where else.
Is anyone else having this issue?
Mine does that. I just called sprint cause I gotfrom telesales and they are sending me replacement.i called two days after I received it they considered it damaged in arrival but the back is so flimsy and I fear it might happen again
Sent from my SPH-L900 using Tapatalk 2
Yeah, mine's doing that too. It's really annoying so I'm glad sprint might replace it without issue. Now I'm trying to decide if it's worth the hassle...
Sent from my SPH-L900 using xda app-developers app
I am surprised that the same area is affected. I would encourage you to call and at least report it so it would get on there"known problem"list . I described it in details to the representativeand told them the phone is brand new and I have no intention to go to a store to have it checked
Sent from my SPH-L900 using Tapatalk 2
i had that problem but i took it off and put that section back on first. I dont remember where on the phone it was but it was bugging me. I havent had a problem since, but that was only yesterday
I remember mine did that when I first got it. Not sure what I did to stop it, maybe what the last poster did. Ive had a case on mine though.
BDawgTrap said:
i had that problem but i took it off and put that section back on first. I dont remember where on the phone it was but it was bugging me. I havent had a problem since, but that was only yesterday
Click to expand...
Click to collapse
+1
Sent from my SPH-L900 using xda app-developers app
Same issue here. Got a replacement cover from Samsung coming. If it doesn't fix the issue Sprint agreed to replace my phone. I have had mine since release day but filed a formal exchange request before the 14 day period was over explaining my situation and Samsung's proposed resolution. I suggest anyone nearing their 14 day expiration to consider doing the same. I want to avoid a replacement if possible because I already set up everything exactly the way I want it, but if the new cover does nothing the phone is going back. FYI, tried a few local Sprint stores and nobody had a phone in stock to let me test the cover swap. Went to Best Buy and although they had none left the guy said he has seen this issue in a lot of the Note 2s already. He even said the 1st gen Notes suffered from a similar manufacturing defect.
Sent from my SPH-L900 using Tapatalk 2
I had this issue on the opposite side. It ended up being the hook/snap. I used my car key to push down the edges around the hook and boom it works like it should. I'm not sure it that will fix everyone's but it worked for me. Also the sprint store wouldn't need a regular cover. The flip cover replaces the back so it should work as well.
Sent from my SPH-L900 using Tapatalk 2
Yes. PITA too.
Think QA from Sprint and/or Samsung belongs to or reads XDA?
I have this issue too. The hook seems to have cracked..
Same thing here since day one.
Sent from my SPH-L900 using xda premium
i don't have the problem since i bought the samsung cover, but i believe the old touch pro 2 had that problem. to fix it we had to put a folded up piece odf paper under the case over the battery. it helped the cover keep its shape. the flexjng caused the cover to pop off. maybe it'll work for this phone too.
TNTRMSKD said:
Same issue here. Got a replacement cover from Samsung coming. If it doesn't fix the issue Sprint agreed to replace my phone. I have had mine since release day but filed a formal exchange request before the 14 day period was over explaining my situation and Samsung's proposed resolution. I suggest anyone nearing their 14 day expiration to consider doing the same. I want to avoid a replacement if possible because I already set up everything exactly the way I want it, but if the new cover does nothing the phone is going back. FYI, tried a few local Sprint stores and nobody had a phone in stock to let me test the cover swap. Went to Best Buy and although they had none left the guy said he has seen this issue in a lot of the Note 2s already. He even said the 1st gen Notes suffered from a similar manufacturing defect.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
are you getting the cover under warranty or did you buy it?
Warranty. They're sending me a new cover free of charge and a return UPS label to give them back my old one (wonder what they're gonna do with it, lol).
---------- Post added at 04:26 PM ---------- Previous post was at 04:23 PM ----------
I've never had that issue on my TP2, but if I recall correctly the cover on that phone wasn't nearly as flimsy and soft as the one on the Note2.
Problem SOLVED!
Guys...the back cover is very poorly designed. When I picked up my GN2 on release day at the sprint store, the girl handed me the demo model so I could see it. I noticied immediately that the back cover was loose by the volume keys. Pulled it off, saw broken hook immediately. I then insisted that I would put the back cover on myself on mine when they took it out of the box, and I never had that issue again. Unlike the GS3 which I upgraded from, which had snaps all around, this one has snaps, and also tabs on the bottom and a hook by the volume keys, which means if you put it on the same way as an S3, YOU WILL BREAK THE HOOKS/TABS! You can't just push it on. Not the users fault, as Samsung made this both extremely difficult to do, and provided no clear instructions on installation/removal. I use multiple batteries and therefore remove it about once per day, and I've had the phone since release day. Unfortunately, without redesigning the actual phone housing itself, I fear it will be impossible for Samsung to fix this by just redesigning the cover. If yours isn't broken yet, just follow my video on proper installation and removal of the back cover. If yours already broke, grab an in-warranty replacement from Samsung and follow my instructions from now on, otherwise this will keep happening. Below is a link to a quick how-to video I made.
http://www.youtube.com/watch?v=mPktGCU995M
Nice video, will try that method when my cover gets here.
Sent from my SPH-L900 using Tapatalk 2
TNTRMSKD said:
Warranty. They're sending me a new cover free of charge and a return UPS label to give them back my old one (wonder what they're gonna do with it, lol).
---------- Post added at 04:26 PM ---------- Previous post was at 04:23 PM ----------
I've never had that issue on my TP2, but if I recall correctly the cover on that phone wasn't nearly as flimsy and soft as the one on the Note2.
Click to expand...
Click to collapse
Did you call sprint or assurion?
Neither, I called Samsung directly.
Sent from my SPH-L900 using Tapatalk 2
TNTRMSKD said:
Neither, I called Samsung directly.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Do you have their number? Thanks.
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