Develop Bugs

Official HTC EVO Random Reboot Thread

From searching, it looks like tons of people are having random reboot issues with the HTC EVO. Let's make one thread to put everything so maybe we can figure this out.
Side note, it looks like the HTC desire has the same issue:
http://forum.xda-developers.com/showthread.php?t=676402&highlight=rebooting
So post what you've tried that hasn't worked.
If you think you have a solution, share

One thing I've noticed is it seems heat related.
I've installed temperatures monitors and it seems around 32 degrees Celcius is around when it reboots. It will reboot loop usually. This can be cured by pulling the battery and waiting for it to cool down, or just put it in the freezer for 4-5 minutes.
I've tried underclocking it with the screen dimmed way down, and running it without the back cover and it still overheats.
For me, the problem came out of nowhere. I had the device for over a month with heavy usage and no problems. My current GUESS is it must be a physical problem. Not enough thermal grease or something...
It looks like the HTC Desire users may be getting replacement motherboards to fix their issue.
Does the HTC EVO and Desire share parts?
From other threads it looks like:
Root or Stock - Doesn't matter
Radio version - Doesn't matter
Rom version - Doesn't matter
GPS Fix - Doesn't matter
GPS turned off - Doesn't matter
3G data, 4G data turned off - Doesn't matter
Hard Reset - Doesn't matter

Found this on the HTC Desire reboot thread:
Latest test list for HTC Desire RR (Random Reboot) problems:
-All phones with s/n HT03 to HT07 can get this problem (Minor problem from SH09 so far)
-Starts around 1.5 to 3 months after use
-Reboots get worse over time
-Firmware and android version doesn’t matter which you have
-Force apps2sd doesn’t matter if you use it or not
-PVT1 or PVT3 or whatever doesn’t matter
-Screen type, doesn't matter if you have AMOLED or SLCD
-There seems to be an antenna/radio/simcard issue also
-Overheating causes reboots too
-Reboot is not always temp related
-SD card size doesn’t seem to matter
-Having apps on SD or not doesn’t matter
-Size of files on SD doesn’t matter
-Rooted or not doesn’t matter
-Motherboard changed after repair doesn't always fix it
-Sim locked or not doesn't matter
-Provider doesn't matter(vodafone, kpn/hi, T-mobile etc all got it)
-Most likely hardware issue, sense flashing won’t fix it, yet changing motherboard will
-Restarting doesn't fix it
-Factory resetting doesn't fix it
-Changing/buying new battery Doesn’t fix it
-Using app killers or shutting down some services yourself doesn't help
-Leaving all settings on default doesn't fix it
-Plugged into car charger in the past doesn’t matter
-Hboot version probably doesn't matter (still not fully tested)
-Having a phone cover or not doesn’t matter
Click to expand...
Click to collapse

wifes phone has been doing it very bad...one that has never been rooted...
was going to root it and try new rom but seems to be a hardware issue.
any other comments on this subject?

My stock rooted Rom just rebooted for the first time today. I really don't rememebr what I was doing st the time....but this has never happened before. I assume there's no event log to check.
Sent from my PC36100 using XDA App

I had been facing this with increasing frequency. I got the phone on launch day, and the problem started over the last month, getting worse all the time. I agree with the OP that there does not seem to be any obvious cause -- sometimes it is heat related, sometimes not. Any time I push the phone (run psx4droid, or navigation + anything else), and sometimes even with lighter usage, like on a phone call. Unrooting did nothing to stop the problem.
After extensive searching, I found three possible causes: bad battery (I tried a new one and the problem continued, but this seems a good starting place), bad memory blocks, or bad processor.
I was unable to find any solution to this problem. I took my phone to Sprint today, and they told me that their tests didn't show a problem. Then I made it happen in front of them (launch navigation to anywhere, then a couple more apps, then boom, reboot) a couple times (really, after the first time, letting it turn back on pretty much caused it to happen again).
After that, they agreed to replace it. I do have the TEP, but they assumed that the problem was hardware related so I don't know if you have to have it for them to replace it.
Strangely, they gave me a white one as a replacement.
I haven't had any problems with the new (well, re-manufactured) one, and I hope it stays that way, but I guess only time will tell.

I'm currently experiencing the problem as well, funny thing is every time it happens, the phone is NOT in use, simply sitting on table or desktop in standby. This happens about once every two days.
Currently running rooted evio2 1.3.1

Wow, I was about to start this thread, when I saw this. I guess I was like 10 minutes late. Either way, i believe something messed with the hardware. My little bro cracked my screen badly, so I am getting a new evo anyway, but will I be able to get one free bcuz of this? This is really a terrible problem. Somebody needs to de-assemble their precious evo and see if there is an obvious problem. thanks a bunch. Subscribing.

same here.
happens mostly when on the charger and i am using it at the same time. so heat related seems likely.

can anyone get a logcat of it happening?

I called sprint support and they said it's defective to return it.
Taking it in for replacement today.

Sprint replaced mine for $35 [a refurb]. That's the end of that.
But now, I can only use the speaker to hear my callers. Gotta go back and get another!

My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk

thlinx said:
My guess is the new update could be putting a lot of strain on the battery but who knows? I haven't experienced it but maybe its because I'm using the extended mah 3500 seido battery.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.

.jond said:
No, I've got the 3500mAh Seido battery too.
I don't think it's strain since mine has gotten worse. AKA the amount of usage it take to make the phone reboot has gone from hours of use to minutes.
Click to expand...
Click to collapse
Actually I just had a reboot lol.
Sent from my PC36100 using Tapatalk

Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.

I bought my EVO on launch day (HW Version 002), and have not had any problems until around Oct 13.
I took the phone on a trip to Orlando, and as soon as I got off the plane and turned on the phone, the problems started happening. It has been happening ever since, even since I returned home.
I bought my phone at Best Buy, and have had their Geek Squad send it back to try to fix it. I also added the complaints about screen separation to the workorder so that they would be more likely to replace the device. Hopefully, this fixes the issue.
I also think it is heat related, but I don't know why it is just now becoming an issue. Just to make sure the folks at BB could see the issue happening, I put the phone in front of my car's heater for a few minutes, then started up Google Earth, and was able to make the phone start boot looping while I walked into the store.
I tried hard reset, soft reset, update prl, underclocking, GPS Reset, new battery, new SD Card, and none of those things worked. I wonder if the removal of the 30 fps limit in the last update caused some type of heat damage?

I just had a reboot last night while trying to look at a picture I'd just taken in the Camera app on CM6.0.0. Only the 2nd or 3rd time it's happened. Still annoying though. Hope it doesn't get worse.

.jond said:
I called sprint support and they said it's defective to return it.
Taking it in for replacement today.
Click to expand...
Click to collapse
How much they charged you?
Sent from my PC36100 using XDA App

MedSchool26 said:
Same thing here. I posted my issue in the rom threads i used, and everyone ignored the issue, lol.
For me, I noticed it about a week after using roms with the new software update (3.29). It happened with navigation, launching multiple apps, running quadrant, etc.
So yesterday I installed DC 3.5 from scratch, turned nav on and let it sit for a couple of hours. NO reboots. Before, after 10 mins of the screen and nav being on, I'd get a reboot. Has anyone else tried this (or willingly to try it)? I switched back to my nand backup, ran quadrant -> bam, reboot.
Click to expand...
Click to collapse
I reset mine back to stock. Unrooted it and everything.
Didn't fix the issue for me.
Now I did try erasing all the stuff that's erasable inside recovery and it seemed to go a few days without a reboot. Not sure if that was a fluke or not.

[Q] Strange screen behavior

Sometimes the screen of my Galaxy Nexus freaks out; it behaves as if I'm touching the screen repeatedly while I'm not. It does not happen a lot, but I think it mostly occurs after pulling down the notification menu and touching a notification message there.
I have tried to reproduce this behavior (camera ready so I can video the screen of my GN), so far no luck. Anybody else experienced this?

Of course, as soon as I'm in bed and have put my camera away I experienced the issue again.
Will try again this evening.

That really sounds like a faulty screen I'm sorry to say. I had a similar issue with my HD2 two years ago, had to send it for replacement.

Hmmm I hope not. Since it's very hard to reproduce I doubt I can prove it in order to get a replacement.

It happens to me only when I'm charging the device. Do you use custom ROM? I'm suspecting that right now.

Nope, stock rom. I haven't even rooted it yet.

Finally caught it on video! It's not very focused but it clearly shows my problem.
http://www.youtube.com/watch?v=Z5_tUcosrtQ&feature=youtu.be
I don't think its a hardware problem because I'm mostly experiencing this problem at home. Today at work I used the phone the whole day without encountering this behavior. I'm 15 minutes home and the problem pops up again. Difference? At home the phone is connected to my WiFi. Any thoughts?

Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium

@rbiter said:
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, it does not happen spontaneously. I happens when I'm using the phone.

I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.

stopdogs said:
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
Click to expand...
Click to collapse
Sounds like a longshot, but I will try it anyway. Thanks!

Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk

noobdeagle said:
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
The phone has a stock image. Also it's not rooted and I haven't touched the bootloader either.

[Q] Wifi stuck "turning on" - Galaxy Nexus

Hi all,
I recently sent my GN (Running 4.0.2 stock, yakju build) back to be repaired because my phones wifi stopped working. what happens is that the phone's wifi seems be stuck "turning on", but never actually does. No wifi icon or anything appears. wifi hotspot doesnt work either. I had my GN from about a week after it was released (I'm in australia so that was about the 22nd December), and around the 15th January is stopped working. This issue cannot be fixed with a reboot, a hard reset, flashing stock roms, toggling airplane mode or anything trivial like that, as I (and others) have tried.
Now i have searched a while on google while i have been without my phone and I'm finding this problem is surfacing for other people too. From what i have seen there seems to be a correlation between 4.0.2 and this issue. Also, it seems to happen some time into the phones life; they do not have this issue when first purchased. I am concerned that this may be a recurring issue which surfaces over time, due to a design flaw or some sort of software issue. If so, this problem will start affecting a lot more people. If anyone who reads this has the same problem, could you please post when it started occuring and what rom, build etc (and anything else which may be helpful) you are running so we can shed a little light on this issue. which many more users i am sure will experience. cheers in advance

just incase anyone actually reads this Galaxy Nexus was sent back, and it was found that the printed ciruit board (PCB) needed replacing. More forums have surfaced since i last checked up on this problem so numbers are slowly rising. Once again, post here if you get the issue, we need numbers

Hi same issue i have butni solve i am living in turkey and i use habertürk news and i saw this application make notification wifi turning om.i reset my phone i load factory firmware but nothing happen ...always say wifi turning on...you need to change your system language another still write wifi turning on on screen in eglish and a application cause to this like my haberturk app
Sent from my Galaxy Nexus using XDA

same problem
Hi,
i had the same problem, wifi mac info was not showing anymore on the Nexus. Reboot and factory reset didn't help. Wifi wouldn't come on anymore.
Ask for a replacement, that's the only thing you can do

Can i ask what version of android you guys had? I'm wondering if this is going to be a recurring problem with hardware due to software issues or if it is purely a design flaw (PCB burning out, etc..) Cheers!

I have the same problem which happened last Saturday and it frustrated the hell out of me, i flashed to different versions of OS....didnt help...
restored to factory firmware and didnt backup the pictures and stuff on the phone!! (FML)
and brought it in to Fido on monday to have it serviced....
talking about bad luck...sigh....
they told me the turn around time is 10-15 business days... (N)
will report back once i hear from them

Before the issue happened, did your phone have any other issues? Say heating up while charging or running the WiFi?
I received a device in for repair with this issue and the customer reported it got really hot before the issue started happening. Everything looked fine on the motherboard - the WiFi antennas were intact. Reloading the software did nothing which means it's a hardware issue..
So very strange. I wonder what's causing this.

i remember when my wifi stopped working i was running 4.0.2. I was actually on holidays in Japan at the time and i was wifi hopping quite a lot around the airport (i was walking around and the wifi would go out of range, latch on again... etc) not sure if that had anything to do with it. Hopped on the plane home and i remember i was on airplane mode using an app called colornote. the phone hung pretty hard and i had to pull the battery. rebooted and tried again and after 10 mins, phone crashed again doing the same thing. Got home and the wifi wasnt working. Not sure if any of this had anything to do with it, but maybe. Didnt notice any overheating, but then again i was around snow haha

hi mrmiklepower
just wondering if your phone has been good since you got it back from repair?
i noticed the phone would reboot itself over and over again after i flashed it back to the stock rom. I just called the third party repair shop that my carrier sent the phone to, they told me its still being fixed.
Oh i hope they will return me my phone soon.

My phone is actually still being repaired also. It's been a total of 2 months since i sent if back! they contacted me and all i know so far is that the phones PCD needed replacing. when my phone arrives i will update as soon as i can. should receive it sometime this week, but its not certain. the majority of my ownership of this phone has been me waiting for its return

Holy mother of lord...
I actually called the third party repair shop that my carrier uses to check on the status of the repair. And they told me its actually In quality control which means the problem was fixed and they're just testing it before they send it back to the store where I brought the phone too. Hoping they'll send it in on Monday so I can either pick it up on the day of or the next day.....keeping my fingers crossed.
Will keep you posted on the status of it too.
Sigh

Ok I got my phone back today.
on the reference sheet I got from the repair shop
it states REPLACED PBA, BGA Failure
I looked it up online and PBA means Printed Board Assembly
which probably means the motherboard was defective and had to be replaced.
and now the phone is working fine. So i guess when this phone was made, there were some flaws with the motherboard on it, thus causing this problem.
Anyways, I hope this information helps with others who experience the same problem

Thanks for letting us know! O got mine back today with the same thing. So looks like there is no way of fixing besides sending it back. Good luck to anyone else who gets this problem
Sent from my Galaxy Nexus using xda premium

So it seems there's no fix for this?
I've been doing some research and it doesn't seem anyone can fix this.. I tried reflashing, wiping every possible thing, etc.. even flashing the stock software via odin. Still no luck.. It seems that we are indeed stuck with sending it back in for a supposedly defective part which seriously blows.
My other question is.. you guys who already received your phones back, did anyone end up with the problem again?
PLEASE if anyone knows how to fix this.. chime in!!!

I had an issue similar to that with my transformer and to fix it I just flash a new kernel im not sure itwill fix the problem for you but it's worth a try
Sent from my Galaxy Nexus using xda premium

Since getting my phone back the problem has not occurred again. I don't think there is anything that can be done as a component needed to be changed apparently. Good luck :/

Zeon45 said:
I had an issue similar to that with my transformer and to fix it I just flash a new kernel im not sure itwill fix the problem for you but it's worth a try
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks, when returning to stock it flashes a new kernel. Also tried it again for the hell of it with faux's kernel, still no luck .

This sucks! This very same thing happened to me yesterday! I Odined back to stock.. no luck! Now after finding this thread, it looks like a hardware issue! That blows! I'll have to give Sprint a call tomorrow!

Hmm sucks to hear it's still cropping up around the place, I heard someone say this issue entered quality control. But anyway, if it helps I've had my phone back for about a month and a bit and its still going strong. hopefully it doesn't happen again though. good luck, hopefully it won't take too long for your phone to come back!

Hi,
I'm with Telus in Canada and had the exact same problem and had my GN repaired. It took only 2 weeks and I just got my unit back. I had already read a lot online about this issue so I asked the Telus rep to tell me what the issue was. She told me that the report states that the board was replaced. This is definitely a hardware problem. I'm hoping that the new board doesn't have this problem and my phone won't need to be repaired again,
I run 4.0.1 on my phone. Telus hasn't released an update yet. I was going to update mine by switching to yakju, but that's when I noticed that the wifi is not working and I thought it's not a good idea to change the stock ROM.

Problem with charging or hardware. Help?

Hi,
I don't actually know if this is ROM related or kernel related or something just wrong with my phone. My phone keeps 'randomly charging' even when the charger isn't plugged in. The status bar icon changes to the lightning one and it says it's charging on the lock screen.
Sometimes the charger doesn't seem to charge the phone till I reboot (It works perfectly with my Nexus 7 and Tab 2).
I'm running the latest CM10 20120930 with Franco kernel (only because I had the problem with the stock kernel and wanted to try another). And yes, I did wipe everything before updating.
If anyone can help, please do. It's really annoying since the screen turns on every time the phone decides to 'wirelessly charge' and runs down my battery.
Thanks for any advice, tips, etc.
Sent from my Galaxy Nexus

AndIKnow said:
Hi,
I don't actually know if this is ROM related or kernel related or something just wrong with my phone. My phone keeps 'randomly charging' even when the charger isn't plugged in. The status bar icon changes to the lightning one and it says it's charging on the lock screen.
Sometimes the charger doesn't seem to charge the phone till I reboot (It works perfectly with my Nexus 7 and Tab 2).
I'm running the latest CM10 20120930 with Franco kernel (only because I had the problem with the stock kernel and wanted to try another). And yes, I did wipe everything before updating.
If anyone can help, please do. It's really annoying since the screen turns on every time the phone decides to 'wirelessly charge' and runs down my battery.
Thanks for any advice, tips, etc.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
There are a lot of topics about this. It's a hardware problem.
I have the same problem, so I bought this USB port replacement http://www.ebay.com/itm/310412314270 and I'm waiting it to arrive so I can change mine... If it works, I'll post it in the General section of this forum.
If your phone is still under warranty, use it, and don't let samsung tell you that is not a manufacturing problem, because it is, there are thousands of people whit the same problem.
Sorry for my bad english.

I've been using the phone since January so I doubt they're gonna listen. Anyways if you're gonna replace the whole port could you make a how-to so anybody who has the same problem could fix it themselves?
Sent from my Nexus 7 using XDA Premium HD app

AndIKnow said:
I've been using the phone since January so I doubt they're gonna listen. Anyways if you're gonna replace the whole port could you make a how-to so anybody who has the same problem could fix it themselves?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
as soon as I replace the port, if it works, I'll post a video and some explanation on how to do it.

Had this problem , sent it back to Samsung and they replaced it and sent it back with a broken screen. Poor customer service but they fixed. As people have stated its the USB port , replace it or send it back under warranty
J
Sent from my supercharged iPhone 5 killing galaxy nexus

I'm replacing mine with the part in the second post. Shipping to Australia is gonna take some time but hopefully it's worth the wait.
Thanks for all the help.
Sent from my Galaxy Nexus using XDA.

GT-N7100 Won't turn on or charge

Hey guys,
From what I've read, this seems to happen to a lot of different phones, but not out of the blue and I didn't find anything on the Note 2, so I'm wondering if it's the same issue and if my only hope is to get a replacement. It seems to be dead at the moment.
Before going to bed, I charged my phone to about 90% and then unplugged it and left it on my desk.
This morning when I woke up, it was off, which was kind of odd, since there's no way it would fully discharge over night. I tried turning it on, plugging it to charge, swapping out the battery for another original one I purchased directly from Samsung, trying other chargers, even the PC and different USB cables, all to no avail.
The only thing I noticed was that the proximity sensor seems to flash every 5-10 seconds, and I'm not sure what that would mean, other than the fact that it's getting some power somehow so that it can light up.
For the time being, I removed the battery and left it like that while I'm at work.
The phone is running the stock ROM for the GT-N7100, nothing was ever modified, it's not rooted or anything.
I know there was a firmware update pop-up on it at some point, but I hadn't installed it.
Any clues guys? I know there's some really knowledgeable people here, so I'm hoping someone might have an idea!
Thanks for the help and sorry for the text!

That sounds like the dreaded sudden death syndrome, how long have you had your device? You need to take it to a service shop. Was it rooted?
Sent from my GT-N7100 using xda app-developers app

Sorry to hear it . Last week I left mine on my bedside table around same charge 90% full and it was completely discharged and just wouldnt turn on but after leaving it on charge for about 30 min when I checked it started working .
Sent from my GT-N7100 using xda app-developers app

Heard of that for the S III but not the Note II!
Never rooted, nope :/
I've had it since November, got it from Newegg while I was in the US.
I should contact Samsung for a service shop location then? I've never done anything like that before.
Thanks!

koalauk said:
Sorry to hear it . Last week I left mine on my bedside table around same charge 90% full and it was completely discharged and just wouldnt turn on but after leaving it on charge for about 30 min when I checked it started working .
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
When you plugged it in to charge, did the LED light up at all? Mine acts as if it wasn't plugged in.

No it didnt but at the time I didnt think of it and walked away leaving it on charge. And also I didnt even know anything sds . Did you try leaving your battery out overnight or use another battery? You called call in to any mobile phone shop and maybe ask them to see if uou can at least tey theirs
Sent from my GT-N7100 using xda app-developers app

All the sign and symptoms indicating its sudden death.
- Have you updated to 4.1.2 which is believed to be patch for SDS?
-Can you reboot to recovery/download mode?

Well, I did try just plugging it in for a few hours, when I went back to it the battery was cold and nothing happened.
I do have 2 original batteries, so I've been trying everything with both of them.
It just seems like the SDS because of the proximity sensor lighting up.
Right now it's unplugged and without a battery, just in case the capacitors need to discharge or something.
I guess I'll try again tonight!
It's really complicated with the GT-N7100 being an international phone, I can't register it on Samsung for warranty, so I've been trying to talk to Newegg and haven't been successful with them so far.
Thanks for the replies guys.

dr.ketan said:
All the sign and symptoms indicating its sudden death.
- Have you updated to 4.1.2 which is believed to be patch for SDS?
-Can you reboot to recovery/download mode?
Click to expand...
Click to collapse
The crazy part is that I think the phone was asking me to update firmware, but I didn't have time to update it before it died like this... what luck, right?
For the download mode, it never reacts while plugged in other than the sensor, so even if I hold the key combinations, it doesn't seem to react. I'll try again more thoroughly tonight.

You didn't update that's prove you were not on latest rom which have fixed sds, really bad luck otherwise it could have took 10min on good network.
Anyway Goodluck for replacement.
Sent from my GT-N7100 using xda premium

Endracion said:
Hey guys,
From what I've read, this seems to happen to a lot of different phones, but not out of the blue and I didn't find anything on the Note 2, so I'm wondering if it's the same issue and if my only hope is to get a replacement. It seems to be dead at the moment.
Before going to bed, I charged my phone to about 90% and then unplugged it and left it on my desk.
This morning when I woke up, it was off, which was kind of odd, since there's no way it would fully discharge over night. I tried turning it on, plugging it to charge, swapping out the battery for another original one I purchased directly from Samsung, trying other chargers, even the PC and different USB cables, all to no avail.
The only thing I noticed was that the proximity sensor seems to flash every 5-10 seconds, and I'm not sure what that would mean, other than the fact that it's getting some power somehow so that it can light up.
For the time being, I removed the battery and left it like that while I'm at work.
The phone is running the stock ROM for the GT-N7100, nothing was ever modified, it's not rooted or anything.
I know there was a firmware update pop-up on it at some point, but I hadn't installed it.
Any clues guys? I know there's some really knowledgeable people here, so I'm hoping someone might have an idea!
Thanks for the help and sorry for the text!
Click to expand...
Click to collapse
Have you tried hard reset, or soft reset. and if you cant get into recovery then sorry buddy :/ it seems like the SDS bug.
The proximity sensor light indicated the system is booting up but if no system boots up then you should send it back to samsung for repair.
Mine should be arriving tomorrow with an engineer's report. I will fill you guys in on what the service centre says.

soljakid said:
Have you tried hard reset, or soft reset. and if you cant get into recovery then sorry buddy :/ it seems like the SDS bug.
The proximity sensor light indicated the system is booting up but if no system boots up then you should send it back to samsung for repair.
Mine should be arriving tomorrow with an engineer's report. I will fill you guys in on what the service centre says.
Click to expand...
Click to collapse
It seems to indeed be the SDS, and I can't reset it or anything since it won't boot up, nor can it go into download mode.
Biggest problem is that seeing as it's a GT-N7100, after calling Samsung; they're telling me it's an international phone and that it can't be serviced in the US or Canada, so I'm basically stuck with a $700 paper weight... this majorly blows. I wish there was someone higher up at Samsung I could speak to, since this is just an extremely bad experience with the product...

Endracion said:
It seems to indeed be the SDS, and I can't reset it or anything since it won't boot up, nor can it go into download mode.
Biggest problem is that seeing as it's a GT-N7100, after calling Samsung; they're telling me it's an international phone and that it can't be serviced in the US or Canada, so I'm basically stuck with a $700 paper weight... this majorly blows. I wish there was someone higher up at Samsung I could speak to, since this is just an extremely bad experience with the product...
Click to expand...
Click to collapse
Dude that sucks hard! I can try and get management number of the people in the uk of you like?

soljakid said:
Dude that sucks hard! I can try and get management number of the people in the uk of you like?
Click to expand...
Click to collapse
I would definitely appreciate any help! You think this would help? I know phones don't exactly carry international warranty, but if I could send it there for replacement or something; that's already a step forward.
I do believe that since Samsung knows of this problem, they should offer outright replacements for anyone suffering of this issue though - because it's literally putting a faulty product on the market; there should be something we can do about this.
Appreciate it, once again!

soljakid said:
Dude that sucks hard! I can try and get management number of the people in the uk of you like?
Click to expand...
Click to collapse
Would you be able to tell us about your engineer's report?