Develop Bugs

[Q] Dead screen

I was running my 3G Slide on Cyanogen 6 Stable (latest) with no problem. Then one day I say artifacts on my screen, I thought there was no problem, as I was playing a game at the time. I assumed it was just a bug in the game. So I kept on using the phone with no problems. About a week later however, the first signs of my current problem surfaced. The face keys died and no longer responded, unless I slided the phone open. The problem just got continually worse from there. It progressed to the point where I could not utilize the touch screen when the phone was open and now it is at a state where the touch screen completely doesn't work either open or closed and the face keys do not work either.
Just to differentiate, the face keys are the home, menu, back, and the google search thing. But the side buttons are all intact.
I've tried rebooting the phone with no success. A memory wipe, resetting Cyanogenmod, failed to solve the problem. I've since then emailed HTC to see if I still have coverage, since I bought it second hand, and reverted back to the original rom, from a thread in the Android Development forum, so I would be covered by warranty.
I at first assumed it was the digitizer, which might still be part of the problem; I still haven't completely ruled it out. But the digitizer alone wouldn't explain the dead keys, would it?
Help? Any suggestions if HTC decides not to repair it or charges a ridiculous price?

I also get the "android.process.acore has stopped unexpectedly" message now once I boot up.

It's most likely the flex cable that connects your screen, front buttons, microphone, etc. (everything on the front panel). That would explain the gradual going-out of the touch screen and the artifacts on the LCD. Send it in to t-mobile, the phone has only been out since last June, less than a year, so it's under warranty. Call for a replacement.

Thanks for the advice, MusicMan. I visited a T-Mobile store today, and its no doubt its under warranty. But here's the problem. I didn't buy the phone from a corporate store or an authorized store, I bought it second hand, and T-Mobile, after a visit and numerous calls of begging and pleading and employing moral responsibility, they said they can't replace the phone because the phone is not registered under my name... blah blah blah. Apparently warranty is through person and not transferrable.
What do I do?

Also, a side note.
In the off chance that I have to deal with HTC for my problem, what is the radio of the stock T-Mobile rom?
Just to make sure my phone is "stock" as ever before I send it in.
As of now I have 7.00.35.04S
I assume that the phone is still rooted even though it is back on the stock rom, will that be a problem if I send it back to HTC?

Leoster121 said:
Also, a side note.
In the off chance that I have to deal with HTC for my problem, what is the radio of the stock T-Mobile rom?
Just to make sure my phone is "stock" as ever before I send it in.
As of now I have 7.00.35.04S
I assume that the phone is still rooted even though it is back on the stock rom, will that be a problem if I send it back to HTC?
Click to expand...
Click to collapse
You could try to get a hold of the guy who sold you it. If he calls T-mobile customer care and puts you as a "authorized user" of the phone you can get it replaced.
However, make sure you are on the latest OTA. Check out this http://forum.xda-developers.com/showthread.php?t=946435 and scroll down to my post for another non over the air update method.
-Current stock ( ota ) radio is 7.09.35.10
- Make sure you don't have superuser. If you replaced your rom with the stock build ( like in the method linked ) you should be fine.

He's currently in Taiwan "for a few months", so I doubt he can help me from there.

Also, I'm pretty sure you have to have proof of purchase when you send it to HTC... So that might be a roadblock as well. Your last option would be to order a new flex cable online and install it yourself. Or you could pay HTC the repair fee to fix it.

MusicMan374 said:
Also, I'm pretty sure you have to have proof of purchase when you send it to HTC... So that might be a roadblock as well. Your last option would be to order a new flex cable online and install it yourself. Or you could pay HTC the repair fee to fix it.
Click to expand...
Click to collapse
Thats why the "owner" of the account calls customer care. They already have the record that he purchased the phone. So if he is put as an "authorized user" of the phone he can send it in. Of course the original owner would have to give t-mobile the shipping address and in sense do it. However it only takes maybe 20 mins? Once his refurbished comes in the mail it comes with either a plastic back or box pre-labeled to send the defective product back in.
Along the lines of have the guy call tmobile.
Hi..my cousin is in the states and is having problems with the tmobile slide..I would like to add him as an authorized user so that he may send it in for a refurbished phone...
tmobile will ask for the # and two other pieces of information...password and something else.
imo worth a shot before you have to spend money!

tri4life said:
However, make sure you are on the latest OTA. Check out this http://forum.xda-developers.com/showthread.php?t=946435 and scroll down to my post for another non over the air update method.
-Current stock ( ota ) radio is 7.09.35.10
- Make sure you don't have superuser. If you replaced your rom with the stock build ( like in the method linked ) you should be fine.
Click to expand...
Click to collapse
I've installed the esprimg, but how do I install the extraneous files for radio?

Leoster121 said:
I've installed the esprimg, but how do I install the extraneous files for radio?
Click to expand...
Click to collapse
So right now you are unrooted and installed the 1.27.531.1 stock correct? In order to update to the latest OTA make sure you download the zip provided. Both are the same file, but for some reason the one on the google docs worked for me.
-copy the update.zip file to your sd card.
-Turn off your phone then power into fast boot( volume down and the power button)
-go into recovery once fastboot gives you the option.
-Once in recovery just hit "apply update.zip"
-Wait for it to finish installing then reboot.
Edit:
Original Thread for update.zip
http://forums.t-mobile.com/t5/HTC/Manual-Update-for-Mytouch-Slide-Guide/m-p/439800#U439800
Follow the rules in the original thread. Much more detail than I provided!
Enjoy man.
I checked all the settings and anything else that I could think of with a normal never rooted mytouch. All looks perfect...also sent my mytouch back to tmobile doing this. Have yet to hear from them.

Phone reboots

Hey folks
These aren't really random reboots, and they don't seem to be caused by an app. They're more like 'when I touch it the wrong way' reboots. If I set the phone down, or pick it up, sometimes it will reboot.
I checked the battery contacts so that's not it. I'm thinking its either a problem with some internal contacts, or something with the accelerometer.
Has anyone experienced something similar? I just passed my 1 year manufacturer warranty period, unfortunately.
Thanks
Sent from my HTC Vision using XDA App

Hmm sounds like a hardware prob. It shouldn't be the accelerometer. Does it reboot when u are using it?

It rarely reboots when I'm using it. It will usually reboot when I pick it up or set it down. If I drop it on my bed from 2 feet up for example, it may reboot. What's weird is that its not a guarantee. In fact I've gone days without a reboot, and sometimes I'll get numerous reboots in a day.
Sent from my HTC Vision using XDA App

Several people have noted there can be a problem with the battery not fitting snugly into the chassis of the phone. When you drop it, the contacts on the battery can move slightly off the contacts on the phone and it can reboot. Some people just shim the battery down a little.

> Has anyone experienced something similar? I just passed my 1 year manufacturer warranty period, unfortunately.
I do not know how far you are out of warranty.
I was in the same situation 2 weeks ago. I was on my last day of warranty (so I thought), when I got tired of the constant reboots. I went to my local TMO store and they claimed that I was out of warranty by one day. Fortunately they put me on the phone with customer service. There it was confirmed that my warranty was out since 1 day. The person was very nice and said: "Let me see what we can do for you". She came back after one minute and offered me a waiver that would have allowed an immediate full upgrade. I told her that TMO does not really have any upgrade that I was interested in (I wanted a keyboard and stock Android), so she went back to her supervisor and came back with the offer that they would assume that my warranty would not run out on that day at 12am, but at midnight and that they would replace the phone under warranty. I have the phone now for a week AND no more reboots. TMO rocks !!
PS: I am with TMO for > 7 years

Yea tmo had some awesome customer service from my experience! I really hope they don't get bought out. Kinda inevitable though since the owners don't want it...boo!

Awesome experience! I work in Customer Service, so I know that I could theoretically get it replaced and whose arm I have to twist to get it. But I don't have the time to spend doing so. My phone hasn't rebooted in a few days now. I did a full wipe before I flashed my next nightly. I have my fingers crossed that it stays that way.
Sent from my HTC Vision using XDA App

I feel silly even mentioning this, because I thought I might be the only one dumb enough to suffer from it, but I will go ahead and mention it anyhow. I was hating the reboots with my G2, and found somewhere that I needed to actually make sure the SD basket was locked in place. I had replaced my SD card, and didn't realize it slides into a locked position. Have never had a reboot since I clicked it in place. That was months ago. Hope it is something that simple for you. Yes... I know I was a dufus for not realizing how the SD basket worked.

I had the exact same problem and I could not figure it out. I finally did a complete wipe and reinstalled problem stopped. I also converted my partitions to ext4 but not sure if that would make a difference.

Could it be the radio?
I did a full wipe prior to flashing CM #231. I used titanium backup to restore my apps. Now the reboots were gone!
But my GPS problems returned. I flashed the next best radio 26.08.04.30. Last time I initially switched radios to fix my gps problem. GPS is still broke, and now I am rebooting again.
Sent from my HTC Vision using XDA App

My painfully embarassing NOOB mistake. and an awesome discovery

I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)

Sent from my SGH-T989 using Tapatalk 2

LuniZ916 said:
I would by no means consider myself a NOOB, as no one ever wants to be a newb. Although i have bricked and burned up a few devices. I have been a member of XDA for some quite some time. I started with an HTC HD2, i was dual booting windows phone 7 and gingerbread. UltimateDroid, to this day is and was still my favorite ROM of all time. Still wonder what happened to that guy. I ended up burning up that phone so much so that it would lock up and i would have to put it in the freezer for 10 minutes before putting the battery back in and turning it on. From there i graduated to an HTC sensation. Phone was awesome, i was running an early version of the InsertCoin rom, until i was on skype and dropped the phone. For some reason upon dropping the phone, it never turned on again. I then had a samsung galaxy captivate and was dissatisfied to find out i could only get 2g on tmobile based on the antenna in the phone not being able to recieve tmo's 3g signal. From there i went on to an LG G2x, what a great phone. I was using the Tsugi Rom with the oyusame overclocked, stock voltage kernel. I got kind of sick of the phone because i had flashed every new rom that came out and it just started to get redundant for me, that was when i got my Galaxy S2 Hercules. I love this phone but alas, in my continued need to root and flash the crap out of my phone with all XDA's latest and greatest goodies, i flashed a rom that didnt boot. (This was most certainly my fault for NOT THOUROUGHLY READING THE INSTRUCTIONS) so in discovering this with only a few minutes to spare before work, i opened up odin before work and grabbed what i thought was clockwork recovery and flashed it. This was not clockwork recovery and upon and flashing i recieved what every modder on here is terrifed of. QHSUSB_DLOAD followed by that god awful windows device driver error noise. Pissed off driving to work with no phone, i immediately ordered a USB jig off amazon for $3.50 cents plus an addition $35.00 to overnight ship it to my house. So impulsive to fix my phone, i even stopped at radio shack and bought myself a pack of 100k ohm resistors to try and make the part myself. Several broken usb cables, and my kitchen table looking like a tweekers wet dream later i had no resolution. I woke up the next morning tracking my usb jig every half hour and was very excited to recieve it, goign as far as to tell my wife that i would no longer be going to get her coffee or visiting her parents as I would be pre-occupied with my phone for a while. Murphy's law however saw otherwise as this did not fix my issue either. I of course knew that if i called T-Mo the insurance would not cover this. So i started calling local cellphone repair shops. After about the fifth place i called, i realized that most of those people are lightyears behind whats happening on here and found that when i tried to talk tech they would sit there and scratch their heads. Out of options, I called the 800 number for samsung on the label underneath the battery. I very openly and honestly explained to the lady that i had rooted my phone, installed a custom recovery and was flashing custom roms. I then explained something went terribly wrong and the phone does not respond at all. I also explained the QHSUSB_DLOAD problem. I believe this explanation went a little beyond they types of calls she was used to recieving. She did however explain that Samsung provides complimentry re-flashes of bricked phones as long as there is no hardware damage done to the device. She then e-mailed me a ups label with shipping paid , and my phone is in the process of being repaired. I did buy yet another HTC sensation to get me by for the 2 business day shipping to samsung, the 7 business day evaluation and repair process, and another 2 days for me to get it back. I hope this can help anyone who has made the same mistake, and moreso i hope this can show others how rushing, being careless, and not reading the instructions can come with HEAVY consequences. Although all should work for me just fine, i still had to spend $150 on a used sensation with a cracked screen, and the nearly 2 weeks of downtime i am without my GS2.
___________________________________________________________________________________________________________________
Devices: HTC HD2(DEAD), HTC - Sensation(DEAD) Samsung Captivate(SOLD) LG G2X(SOLD) Galaxy S2 T989 (OUT FOR REPAIR) HTC Sensation (Were keeping that stock at least until i get the glass replaced and my GS2 back) LG G2X (Waiting to warranty my fiance's sensation to get it back)
Click to expand...
Click to collapse
Same thing happen to me the dreaded QHSUSB error when I bricked my exhibit2. I know how you feel.
Sent from my SGH-T989 using XDA Premium App

Lol. I bricked mt very first phone (the T989) the very first day i got it. I got it replaced for free with that 14 day gap thing that Tmo has. Got lucky. Ive never had a bad flash since.
Sent from my SGH-T989 using xda app-developers app

I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.

supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Stupid kies mini hard bricked my trusty vibrant... Luckily, t-mobile replaced it for free, but it was the horrible exhibit 1.

supraman89 said:
I've been on xda for quite some time now, and i know for a fact that people have gotten their phones replaced through standard warranty when they got that error, the old "it stopped working and won't turn on" has worked for some. If you cannot revive it chances are that no one at samsung can, i don't think they even bother, they just open it and reflash the phone.
Click to expand...
Click to collapse
Yeah most people went through regular warranty exchanges, but from what the OP was explaining he's a very honest person and would have said that he rooted the phone therefore he would not be able to exchange it.
That's good that he's honest, but it would have been a lot easier to just do that and get the phone next day because TMobile is just going to send that phone back to Samsung and they'll do the exact same thing they're doing to his phone now
Sent from my SGH-T989 using xda app-developers app

This sounds exactly like something I would! Especially buying parts thinking I could fix it!!
I feel so at home on xda!!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

U could a saved a ton of time and money by just saying ur phone stopped working. Cuz technically it did
Sent from my SGH-T989 using xda app-developers app

LOOOOOOL this made my day^^
I have my phone till two years now and i bricked it once by disconnecting by mistake while unlocking bootloader (yes i fell with my phone in the hand and lukily it only disconnected and didnt pull my laptop with it.
I had it fixed in a half hour^^
Greets
Sent from my Xperia X10 using xda app-developers app

Good to know thanks
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

My very first device was the Mytouch 3G on T-Mobile. Back then, it was maybe the 2nd Android phone to have even existed at that point.
Me, never being satisfied with anything stock and coming from a heavily modified blackberry, wanted to tweak the hell out of it.
Back then, it took a LOT more to root and flash, ESPECIALLY HTC Devices. There were no custom tools yet to root, and the only easy part was using CWM. You HAD to use adb commands to exploit to get root and even get CWM on the device at that point, but only AFTER downgrading it back to Android 1.5, but after that it was easy.
(I couldn't believe how fast and easy it was to root and flash on the T989 after having HTC devices up until last year)
Anyways, I somehow managed to get it CWM to boot (you had to boot into normal recovery after replacing update.zip with a CWM zip, and then flash the new update.zip file back then) and went to flash a ROM, and instead I flashed a zip, but the wrong ROM was uploaded by the OP, and what I had flashed as for the G1. It was literally only uploaded for all of maybe 2 minutes before he pulled the post down and uploaded the correct version.
I was the ONLY one who downloaded and flashed it within that 2 minute window.
Needless to say, I hated my life.
Now the funny part:
I was so paranoid back then about not letting T-Mobile know that I was rooted, that I literally bought a BRAND NEW Mytouch 3G (because you couldn't even find broken ones on ebay yet) and sold the broken one, which I bought the day before mind you, for $20. I wish I would have known that, back then, there were no counters on the MT3G. T-Mobile would have never known as it wouldn't boot.
:crying:
Flash forward to today, and IDGAF.

Need to call Verizon about warranty replacement. What version info should I give?

I need to call verizon about a possible warranty replacement for my phone. What info should I give them if they ask me to go to about phone?
Whats the most recent OTA stock rom, radio, etc?
I'll put it back to stock before I send it in, but I'm not ready to do that yet.
Thanks

qw3rty333 said:
I need to call verizon about a possible warranty replacement for my phone. What info should I give them if they ask me to go to about phone?
Whats the most recent OTA stock rom, radio, etc?
I'll put it back to stock before I send it in, but I'm not ready to do that yet.
Thanks
Click to expand...
Click to collapse
I just recently got mine replaced by verizon due to my phone having charging issues. I went into the store, didn't call before hand.
I had flashed back to stock before i went in. Told the girl there that it wasnt charging right and i have multiple batteries and they all do the same. she went to look up on some database if others were reporting similar issues (there were none). after giving her my phone number and 5 minutes later she said a replacement is on the way and to mail my old one back in the same box (shipping was paid for)
I was very pleased by how quick and painless it all was. She never touched or looked at my phone at all and asked hardly any questions.
Anyways, not sure how a phone conversation would go, but i would just skip all that and go right to the store (after flashing back to stock of course ) good luck!
edit: my phone also had a chip in the screen (about 2 cm at the bottom right, no cracks though). it never even came up. they were very lenient imo. very happy

I'm having charging problems too. It always says its charging, whether its plugged in or not. Then lots of times wont charge when its plugged in, have to reboot it to get it to charge. Problem is my phones really beat up, and I lost the back cover. But I have 2 weeks left on the warranty so I'm gonna give it a shot. I've got insurance as a backup if they say its too beat up.

qw3rty333 said:
I'm having charging problems too. It always says its charging, whether its plugged in or not. Then lots of times wont charge when its plugged in, have to reboot it to get it to charge. Problem is my phones really beat up, and I lost the back cover. But I have 2 weeks left on the warranty so I'm gonna give it a shot. I've got insurance as a backup if they say its too beat up.
Click to expand...
Click to collapse
I'm assuming you're on Verizon. I noticed they have a promotion on their website that through March 8th they are allowing you to add on their various insurances to your plan. If they send you away just add/upgrade to their best protection (which covers accidental damage) and go in once the Samsung warranty is up. That was my plan anyway, but I'm glad things went smoothly.

[Q] Note 2 Dead? SDS?

Hi Folks,
Stock Note II N-7100 (Received from O2 in October 2012). Had, previously, moved from the O2 branded firmware to stock week I received the phone. No water damage or anything, not dropped, phone has lived in a rubber case since new.
No issues since (v occasional random reboot, monthly maybe?).
Today, mid call, I was dropped, and the phone what I thought was rebooting on me (Samsung Galaxy Note II [white, non animated] logo popped up), but it stayed up, rather than moving through the animated logo to the OS.
Vol-Up + Home + Power won't take me to recovery (Vol-Down + Home + Power will take me to an ODIN flash screen).
Connecting a charger brings up the battery, a 'spinner' appears in that for a second, then freezes, battery icon never changes to the animated charging logo.
Does this sound like SDS? or something else? Is there anything to be done at home to recover? Or is it a hardware fault in which case I'll start the process of tracking down a service centre & dig out an old handset in the mean time.
Thanks all,
Gavin.

gicarey said:
Hi Folks,
Stock Note II N-7100 (Received from O2 in October 2012). Had, previously, moved from the O2 branded firmware to stock week I received the phone. No water damage or anything, not dropped, phone has lived in a rubber case since new.
No issues since (v occasional random reboot, monthly maybe?).
Today, mid call, I was dropped, and the phone what I thought was rebooting on me (Samsung Galaxy Note II [white, non animated] logo popped up), but it stayed up, rather than moving through the animated logo to the OS.
Vol-Up + Home + Power won't take me to recovery (Vol-Down + Home + Power will take me to an ODIN flash screen).
Connecting a charger brings up the battery, a 'spinner' appears in that for a second, then freezes, battery icon never changes to the animated charging logo.
Does this sound like SDS? or something else? Is there anything to be done at home to recover? Or is it a hardware fault in which case I'll start the process of tracking down a service centre & dig out an old handset in the mean time.
Thanks all,
Gavin.
Click to expand...
Click to collapse
Sounds like Half SDS for me(in half SDS you can go only into Download mode) With what version of android was your phone 4.1.2 or 4.1.1 this information will be good for us, sorry for your phone try reflashing it with stock rom with ODIN and if the process fail go to the service center with your warranty but check in Download mod if the Binary count is 0 and everything says Stock, not Custom. Good luck mate.

wowrlz123 said:
Sounds like Half SDS for me(in half SDS you can go only into Download mode) With what version of android was your phone 4.1.2 or 4.1.1 this information will be good for us, sorry for your phone try reflashing it with stock rom with ODIN and if the process fail go to the service center with your warranty but check in Download mod if the Binary count is 0 and everything says Stock, not Custom. Good luck mate.
Click to expand...
Click to collapse
Thanks,
Can't recall the version, tho I think 4.1.1? Whatever was avail in October. The in-phone thingy kept reporting 'no update' so hadn't moved on to anything further.
Download screen says:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
If that's any use (no sign of a counter).

gicarey said:
Thanks,
Can't recall the version, tho I think 4.1.1? Whatever was avail in October. The in-phone thingy kept reporting 'no update' so hadn't moved on to anything further.
Download screen says:
ODIN MODE
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
If that's any use (no sign of a counter).
Click to expand...
Click to collapse
They may remove your warranty for the System status its says custom, have you rooted the phone and from which country are you? You should have updated to 4.1.2 with odin the SDS is kinda fixed even thought there are still people with dead Note 2 with 4.1.2.

wowrlz123 said:
They may remove your warranty for the System status its says custom, have you rooted the phone and from which country are you? You should have updated to 4.1.2 with odin the SDS is kinda fixed even thought there are still people with dead Note 2 with 4.1.2.
Click to expand...
Click to collapse
Hmm... believe I may have rooted right at the start for a reason related to the flashing a non-O2 ROM, though wasn't running a rooted phone since. I'm UK based.
Assuming ODIN will flash the phone (even if it won't, subsequently, work) would that reset the System status?

gicarey said:
Hmm... believe I may have rooted right at the start for a reason related to the flashing a non-O2 ROM. I'm UK based.
Assuming ODIN will flash the phone (even if it won't, subsequently, work) would that reset the System status?
Click to expand...
Click to collapse
No you must have working phone and reset it with triangle away.

wowrlz123 said:
No you must have working phone and reset it with triangle away.
Click to expand...
Click to collapse
Sure I did that way back when.

dont worry about the "custom" part. it is known that SDS changes the status to custom so it doesn't matter at all. Send it to samsung and it should be repaired. then check if it have a new chip or an old one
Sent from my GT-N7100 using xda premium

Either way, if you're in the EU, rooting does not void warranty unless it can be proven that rooting is the direct cause of the problem.
Sent from my GT-N7100 using Tapatalk 2

As someone else said, try flashing a rom in odin before doing anything else. A stock system will reset the status to official. Triangle away is only needed to reset the count and usually doesn't reset the system status anyway.
Sent from my SPH-L900 using xda premium

aka_sirok said:
dont worry about the "custom" part. it is known that SDS changes the status to custom so it doesn't matter at all. Send it to samsung and it should be repaired. then check if it have a new chip or an old onem
Click to expand...
Click to collapse
adytum said:
Either way, if you're in the EU, rooting does not void warranty unless it can be proven that rooting is the direct cause of the problem.
Click to expand...
Click to collapse
Thanks chaps, this helps settle a few nerves.
billard412 said:
As someone else said, try flashing a rom in odin before doing anything else. A stock system will reset the status to official. Triangle away is only needed to reset the count and usually doesn't reset the system status anyway.
Click to expand...
Click to collapse
Sadly, no go, due to lack of a PIT according to Odin.
Called Samsung, mail in with 2 week turn around, or walk in and should have it back in 2 days? Sound about right.
There's a Service Centre 10 mins from my office, so I shall walk it in there, but (rather annoyingly), am on a training course until Friday so I won't get along till then. Excellent timing! Still, walk in ought still be quicker than sending it away.
In the mean time, I have hauled out an old SE Arc S running ICS for the time being. Feels painfully slow & restricted (low memory) compared to the Note2!
Thanks for all your help guys.

So...
Walked the phone into the service centre (CRC - http://www.crclondon.co.uk/repairs/samsungrepairs) on Monday, who told me they'd need to send it up to their Level 3 centre, which would likely be a 7-10 day turn around.
Took a call from them today, claiming that as the phone had been rooted, they couldn't do it under warranty, and it would cost £120 to repair. I rather firmly mentioned the aforementioned EU regulation which, I understood, meant that nevertheless, the repair, unless caused by the root, ought still be covered under warranty. The chap was completely intractable, refused to pass me to a supervisor of any sort for further discussion, so I've told him to have it returned to their office and I would collect ASAP and deal with Samsung directly where I hoped to have a more satisfactory discussion.
Seems like it's likely to be back with them on Friday - I will probably collect on Monday and get it dispatched same day.
Wish I hadn't bothered waiting for the walk in centre now. The Sony Arc S I'm currently using is frustratingly slow by comparison with what I've become used to!

I think you were being too honest.
I got my note2 motherboard replaced last month. and since they coundnt tell whether i had rooted or not and samsung havent officially made any announcement about sds, i told them what i found on the net that the system status shown customs because the nand memory was corrupt and it couldnt read the product name nor system partition thereore it defaulted the system status to be custom.

As a further update, Samsung central help group pretty awful to deal with, and not resulting in a satisfactory resolution.
Was eventually promised a call back, finally got an email 4 days later basically telling me 'whatever our 3rd party service centre told you we will stand by, if you collect & send to us, we'll lookup their response and use that in communication with you..' 'If you want to challenge their assertion, you'll need to source a report from an independent assessor.'
So, from all this - Ultimately, I need the phone back in a reasonable timeframe, so I've asked the 3rd party service centre to effect the repair, and I'll pay their £120 bill. I have also told them that I want whatever components they replace (I'm told likely motherboard), and copies of their full engineers report containing details of the fault found, diagnosis of cause, and resolution steps - returned to me along with the device so that I retain any evidence I require for further discussions (getting them to agree to this was an awful task, as they initially quoted various recycling regulations).
Once it's back in hand, I'll then revert to Samsung again, and work my way up through the escalation queue.
Next phone, I suspect, won't be a Samsung device. Maybe Nexus.
Fun fun fun...
G.