Develop Bugs

I need help

Owner of international Note 2.
This morning I found my phone dead. I cannot start it either through power button or other combination of buttons. I took out the battery and back in. Through ADB no luck it doesn't even register that I plugged in the phone.
From time to time the first led on the right of the camera blinks (I think it's one of the sensors).
Can anyone through an idea what I can do to recover my phone?
Sent from my Nexus 7 using XDA Premium HD app

daniel_cassian said:
Owner of international Note 2.
This morning I found my phone dead. I cannot start it either through power button or other combination of buttons. I took out the battery and back in. Through ADB no luck it doesn't even register that I plugged in the phone.
From time to time the first led on the right of the camera blinks (I think it's one of the sensors).
Can anyone through an idea what I can do to recover my phone?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
have you rooted your phone ? .. can you go to recovery ? download mode ?

My phone was rooted. I had MIUI on it. I was on the same ROM for 2 weeks, so it can't be the ROM. I cannot access the phone in any way possible

Unfortunately looks like its SDS ( sudden death syndrome ) . Was your phone on 4.1.1 or 4.1.2 firmware? Its supposed that 4.1.2 has sds fix. Anyway if its sds so only option is to replace motherboard.
Sent from my GT-N7100 using xda premium

T511 said:
Unfortunately looks like its SDS ( sudden death syndrome ) . Was your phone on 4.1.1 or 4.1.2 firmware? Its supposed that 4.1.2 has sds fix. Anyway if its sds so only option is to replace motherboard.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Agree with T511.. One of my frns S3 also had SDS n like he mentioned, motherboard had to be changed... if you have warranty n bill they will do it free.. doesnt matter if its rooted.. they cant check either..

It seems so. I've read for the last hour about it. What i don't know is: if i go to service, will they detect i was rooted and on custom rom? If so... can they refuse my service completely (After all SDS is not ROM related) or at least they can service me but with charges (which i presume it will be allot, but after all less then a new phone)?

daniel_cassian said:
It seems so. I've read for the last hour about it. What i don't know is: if i go to service, will they detect i was rooted and on custom rom? If so... can they refuse my service completely (After all SDS is not ROM related) or at least they can service me but with charges (which i presume it will be allot, but after all less then a new phone)?
Click to expand...
Click to collapse
Even they cant access it pal.. so they wont come to know.. just take it to service.. they will surely do it free if its under warranty..
but your data cant be revived.. hope you had a backup of contacts and msgs.. (5 mins'm waiting to post this .. as i've just started postin after a decent learning)

I had everything on my card. Titanium Backup few days ago....so i won't lose anything important. I just hope that the service will do it without arguing. I am under contract to Vodafone since november 2012. But in my country service or service period are words which are still foreign to distributors or sellers in general

[Q] Phone randomly died , won't start again

So I put my phone on charge and went to sleep, the next morning the phone's battery lamp shined green as usual when the phone was fully charged. Only it had turned itself off and it wouldn't start it again.
I haven't contacted my provider yet because i am unsure whether the warranty will cover it since I rooted it the day before, have not installed anything yet though.
I have tried removing the battery for a couple of hours without any result, I have also tried different combinations of holding down buttons without any result either.
Can it be as simple as the battery broke? How can i check if that is the case without any other battery or voltmeter etc?
Has anyone else had this problem?
I am running 4.1.2 on my 7105, flashed from ODIN about a month ago.

Please provide some details to answer you better
Do you able to put device in download mode? What you can read in download mode rt upper corner?
Which method you have used to root? Have you flashed any cwm? If yes link here which one.
Have you tried flashing? If yes what was outcome?
Sent from my GT-N7100 using xda premium

dr.ketan said:
Please provide some details to answer you better
Do you able to put device in download mode? What you can read in download mode rt upper corner?
Which method you have used to root? Have you flashed any cwm? If yes link here which one.
Have you tried flashing? If yes what was outcome?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
No i am not able to get into download mode since absolutely nothing happens when i press any button, just like as if there was no battery in the phone.
I used CF-Auto-Root-t0lte-gtn7105 to root but I don't think that this is the source of the problem since the phone died two days after i rooted.
As I said I am using the 4.1.2 official version which i flashed using odin, that was over like 2-3 months ago so I dont remember exactly which one I used but I believe it was this one: http://forum.xda-developers.com/showthread.php?t=2027586
Here is the thread i used to root: http://forum.xda-developers.com/showthread.php?t=1933542

Firmware you have linked which you believe to flashed is doubtfully patched for sds.
On N7100 same released in dec 12 and within few days it was withheld, may be it was not properly patched. Later release in 2013 are sds patched.
Do you remember it was somewhat leggy/freezing before this happened?
Though symptoms mimics sds, have you tried to reboot to recovery?
Sent from my GT-N7100 using xda premium

dr.ketan said:
Firmware you have linked which you believe to flashed is doubtfully patched for sds.
On N7100 same released in dec 12 and within few days it was withheld, may be it was not properly patched. Later release in 2013 are sds patched.
Do you remember it was somewhat leggy/freezing before this happened?
Though symptoms mimics sds, have you tried to reboot to recovery?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
No freezes or anything but the day before i rooted i remember it restarted itself whilst in my pocket, was sitting still so don't think i accidentally pressed the off button, but can't know for sure.
Cant enter recovery or anything since absolutely nothing happens when i hold down up/home/power, neither if I hold down/home/power or any other combination. Absolutely no response from the phone, just as there was no battery in the phone but i can assure you that there is. Nothing happens when I connect the charger either. No lights no nothing!

If possible try to manage for different battery to just confirm it is not battery issue, and remove battery from device for a day meanwhile and try to boot after that, if no result then it's likely sds and should consult service station.
Sent from my GT-N7100 using xda premium

I didn't think sds affected n7105 that's why I swapped both of my s3's for mine I'm pooping it now. S4 here I come
Sent from my GT-N7105 using xda app-developers app

Hi,
Is the N7105 got the same eMMC chip 0xf1 and 0xf7 as the N7100?

thedadio said:
I didn't think sds affected n7105 that's why I swapped both of my s3's for mine I'm pooping it now. S4 here I come
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
ppn7 said:
Hi,
Is the N7105 got the same eMMC chip 0xf1 and 0xf7 as the N7100?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Download it and check. If it says "No, Sane chip" you're fine.

happened to me too!
exactly the same **** happened to me too i don't know what happened, i didn't root it or did anything to it. it just randomly turned itself off and didn't start up again. then suddenly it happened to load the battery again and i was able to boot it, but here the ****ed up part came... it showed me the samsung startup logo and everything but then weird green vertical stripes(like the matrix) appeared and nothing more happened. few reboots after, same problem as in the beginning, it's not starting up again. help me please

I've got Sudden Death Syndrome... now what?

I've got all the symptoms for SDS and I downloaded the eMMC check app which says I have an insane chip. I'm on the current firmware (4.1.2), so that didn't fix it for me.
How can I contact Samsung about this issue? I bought this phone from an Amazon seller.

This app only detects your hardware. It means that even if you apply a fix this app always tells you that you are insafe...
If you have an official firmware released since February, 2013 you are SAFE.
Why do you think that you have all the symptoms of SDS?

I have similar problems with my GT-N7100 which I bought from Newegg.com last November (British unit). The phone often freezes, reboots and I believe once turned itself off. Those symptoms happen several times a day and I consider this phone to be unusable at this time.
There is no US warranty and I have no clue whether anything can be done and by whom. Is this phone reparable? If yes, which outfit can do it?

Memphis_ said:
This app only detects your hardware. It means that even if you apply a fix this app always tells you that you are insafe...
If you have an official firmware released since February, 2013 you are SAFE.
Why do you think that you have all the symptoms of SDS?
Click to expand...
Click to collapse
Thanks for the response.
My phone is 6 months old now. It freezes and must be rebooted very often now, usually a matter of minutes. This even happens in safe mode.
I am running Perseus - alpha32 kernel, which I believe should include Samsung's SDS fix

WCF said:
Thanks for the response.
My phone is 6 months old now. It freezes and must be rebooted very often now, usually a matter of minutes. This even happens in safe mode.
I am running Perseus - alpha32 kernel, which I believe should include Samsung's SDS fix
Click to expand...
Click to collapse
Yeah Perseus kernel has the SDS's fix since January, 2013 so without being sure I don't think the SDS can arrive if you have this protection.
A clean installation of your system may solves your problem.
You can also try to update your firmware via OTA or Odin flash.

Memphis_ said:
This app only detects your hardware. It means that even if you apply a fix this app always tells you that you are insafe...
If you have an official firmware released since February, 2013 you are SAFE.
Why do you think that you have all the symptoms of SDS?
Click to expand...
Click to collapse
I saw that i have an insane chip and then your comment calmed me down :good:

If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.

tuxonhtc said:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
Click to expand...
Click to collapse
How do you replace the motherboard? Who does it - would you know of a contact?
Thanks.

tuxonhtc said:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
Click to expand...
Click to collapse
Yes, it still has the SDS symptoms with Perseus alpha-32. I updated to Perseus alpha-36 today, but the symptoms persisted even in safe mode. I've done a factory reset and everything is okay for now, but I'm worried that it will definitely be back. I suppose I should sent it off to Samsung just to be sure?

Reuven007 said:
How do you replace the motherboard? Who does it - would you know of a contact?
Thanks.
Click to expand...
Click to collapse
By using your warranty.

WCF said:
Yes, it still has the SDS symptoms with Perseus alpha-32. I updated to Perseus alpha-36 today, but the symptoms persisted even in safe mode. I've done a factory reset and everything is okay for now, but I'm worried that it will definitely be back. I suppose I should sent it off to Samsung just to be sure?
Click to expand...
Click to collapse
Let it die then. Don't try too hard to prolong SDS. It's still under warranty right? You should get a replacement easily.

WCF said:
Yes, it still has the SDS symptoms with Perseus alpha-32. I updated to Perseus alpha-36 today, but the symptoms persisted even in safe mode. I've done a factory reset and everything is okay for now, but I'm worried that it will definitely be back. I suppose I should sent it off to Samsung just to be sure?
Click to expand...
Click to collapse
What symptoms have you got - if you 're flashing ROMS/Kernels then how can it be SDS. As I understand it SDS means that your phone is a brick. Just because it's freezing or rebooting doesn't mean it's SDS - could be many things

tuxonhtc said:
If you use Perseus, reckon you're safe. Does it still exhibit SDS symptoms? I wouldn't worry, you'd be better off letting it die and getting the motherboard replaced anyways.
Click to expand...
Click to collapse
eladwf said:
By using your warranty.
Click to expand...
Click to collapse
Unfortunately my phone is an international version, purchased last November from newegg.com with 90 day warranty. So I need an independent technician or lab to fix it and I have no clue where to start.

Reuven007 said:
Unfortunately my phone is an international version, purchased last November from newegg.com with 90 day warranty. So I need an independent technician or lab to fix it and I have no clue where to start.
Click to expand...
Click to collapse
16gb or 32 gb

Rampant reboots and freezes are also symptoms of a badly coded app, a faulty memory card, a bug in a custom kernel, a bug in a custom rom, a dying sim card, malware, a bad flash.. You get the point
Sent from my GT-N7100 using Tapatalk 2

Apologies for alarming terminology. Here is the definition of SDS I've gone by:
The Sudden Death Syndrome (SDS) issue is caused by a buggy firmware (low level machine code) on the emmc of devices, specifically, a 16GB VTU00M chip with firmware revision 0xf1. The phone dies when trying to write data to an affected block. Samsung has issued a temporary fix to avoid sudden death but this is not a permanent solution. It causes a device freeze or lock-up when attempting to write to an affected block. For devices which have undergone a lot of writes before the fix, the users experience persistant freezing which may last from 2min to even an hour.
Click to expand...
Click to collapse
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.

WCF said:
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
Click to expand...
Click to collapse
My GT-N7100 16GB phone fits exactly the SDS definition. Since I have no warranty, what could be done to fix this problem? It's only 6 months old phone...

WCF said:
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
Click to expand...
Click to collapse
Exactly! According to this definition, your phone is not showing symptoms of SDS but merely demonstrating that the fix is kicking into action. Don't you think its weird calling it a "Sudden" Death Syndrome and then thinking it should have symptoms. The irony -_-
Sent from my GT-N7100 using xda app-developers app

WCF said:
Apologies for alarming terminology. Here is the definition of SDS I've gone by:
My issues seem consistent with that description. I've ruled out software bugs by trying safe mode.
Click to expand...
Click to collapse
Since you said it seemed ok after a factory reset, I was thinking it might be something else. Not saying it's absolutely not sds, but as bushako said, it seems as it might as well be the protection kicking in, it has happened a couple of times for me too.
What you could try, is taking a look at last_kmsg immediately after booting after you get a freeze. If the log has no alarms or anything out of the ordinary, chances are it's the fix kicking in and blocking the bad commands sent to eMMC.
Sent from my GT-N7100 using Tapatalk 2

bushako said:
Exactly! According to this definition, your phone is not showing symptoms of SDS but merely demonstrating that the fix is kicking into action. Don't you think its weird calling it a "Sudden" Death Syndrome and then thinking it should have symptoms. The irony -_-
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I see what you are saying. But if the prevention for SDS makes the phone unusable, isn't this just a lesser of two evils? Wouldn't this inevitably happen again and I would be better off sending this for warranty?

[Q] Brand New Note 3 problem

Hi guys, I have a weird problem and I need your advice.
My brand new galaxy Note 3 Sm-N900T is having screen blackouts....
Its like after the screen timeout the screen goes off and then when I press the power button it doesn't go back on again.
Or if I turn the screen off it doesn't go back on again... the buttons are working the sounds are on, I can answer calls and everything but the screen is black.
If I play with it (pressing power or home buttons) for a while it comes back on. Sometimes the phone restarts (rarely, I think because i press power button).
I have tried everything from playing with settings to wiping the cache and resetting the phone few times.
It looks like its a software issue to me, or maybe sensor.. but i think that when power button is pressed the screen should turn on regardless of sensors.
I do have the custom S-Case but I had the issue even before I got that.
Now.. I have few choices :
1. Go to t-Mobile and get a replacement.. probably refurbished, not a fact that the problem will away because I heard of lots of people having this issue ...
I of course do not want to do that.. I have this phone for less than a month.
2. Wait for KitKat....
3. install some kind of custom rom and see if problem goes away.
If anyone can help, Id really appreciate it.

I would do an exchange.. you paid good money for it and a defect is a defect, I wouldn't depend on a 3rd party patch for this
Sent from my SM-N900T using Tapatalk

?
go to the store for change this defective note.

This may be jelly bean bug... Lots and lots of people report the same problem...
If I replace my piece I will probably get a refurbished one with a great chance of having this or some kind of another problem......

Keda_P said:
This may be jelly bean bug... Lots and lots of people report the same problem...
If I replace my piece I will probably get a refurbished one with a great chance of having this or some kind of another problem......
Click to expand...
Click to collapse
sucks man.
I know on my htc onei have the purple camera problem but everything else was fine. they had to send me 2 replacements because the first one had a yellow screen and worse camera then mines.
Tmobile doesnt even check there replacement. Most of the time there phones that people traded in. And all they do with those is a power on check.
Now if you just got the phone and within the 14 exchange you can take it to the store and get a brand new one.

Had it for more than 2 weeks now.. since i was always playing with it i did not notice the problem .. (the screen was always on).
I called Samsung and Tmobile. I told tmobile that samsung said i have a defective phone. so Tmobile is sending me a "Like new" phone meaning that someone returned it within 14 days. I get to check it and if i dont like it i will just send them their phone back. and suddenly mine doesnt do the problem for 30 minutes lol.. maybe it got scared. Personally i think that KitKat would fix it.

Any force closes? I had this problem too untill I stopped using the crapy My Magazine bloatware, which was also sometimes force closing...
Sent from my SM-N900T using Tapatalk

No, no force closes, but one time it was funny, a little bit of status bar appeared from the bottom and on top it was a little bit cutoff.... like someone slid the screen up few pixels.
And whatever was cut just came from the bottom. Its weird... for $700 phone it should be flawless... I hope they dont send me crap phone and i hope they dont send my phone to someone else.
How can i get rid of it to see if that was the problem?

My phone works perfect and I had if since the first week they came out. .. It's not a jellybean thing you phone has a problem. ..
Sent from my SM-N900T using XDA Premium 4 mobile app

djtheraven said:
My phone works perfect and I had if since the first week they came out. .. It's not a jellybean thing you phone has a problem. ..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I figured id try to reflash (not data reset, but reflash via Kies) so far so good no problem.
The whole thing looks like soft prob, not hard.
If it comes back Ill let you know. This could be a nice fix if works.

I'm in nyc, and my local store called the warrenty center and got me a brand new SGS2 one time. It still had all the blue plastic in the sim card and sd card slots, and plastic on the screen. So I'm know they can request it, just depends on your store if they are willing.
Sent from my SM-N900T using Tapatalk

Keda_P said:
I figured id try to reflash (not data reset, but reflash via Kies) so far so good no problem.
The whole thing looks like soft prob, not hard.
If it comes back Ill let you know. This could be a nice fix if works.
Click to expand...
Click to collapse
My sgs2 had problems out of the box. After I installed custom ROM they went away. It does happen. Restored stock via Odin, still no problems. Sometimes the software doesn't flash correctly from the manufacturer.
Sent from the phablet of the year!

noobtoob said:
My sgs2 had problems out of the box. After I installed custom ROM they went away. It does happen. Restored stock via Odin, still no problems. Sometimes the software doesn't flash correctly from the manufacturer.
Sent from the phablet of the year!
Click to expand...
Click to collapse
Well, I dont know what to think anymore... Looks like the problem persists but happens so rare that without the past I wouldnt notice it.
This makes me believe that with KitKat it will probably disappear. If soft changes cause this to go away or be less it means (to me) that the phone is not defective. New phone is still on the way, to bad I did not purchase it at local store... I did it online, so there is no one to yell at.
It will arrive on Feb 6th so I have plenty of time to test my phone, with some luck KitKat will roll out during this time and then I will be able to definitely see. And if new phone is cool I have the option of exchange anyway .
Thank you all for your help, keep posting, its an interesting issue.

:/
Phone went worse and worse everyday ... now the S-Pen "Air Command" doesnt pop up, several weird disfunctions...
Waiting for the replacement.

[Q] Nexus 7 Hardbrick! QHSUSB

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