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.
Related
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.
It seems the search function is down, so my apologies if this has been covered before. I scanned 5+ pages of the General forum and saw nothing answering my question.
So as the title says, I need to mail back my phone for warranty exchange. I've been rooted and running a custom ROM for quite some time, with most of my recent time spent on the various versions of LiteROM.
My question is, do I need to do anything outside of flashing the latest UCLJ3 stock ROM via odin? I did that last night (after a wipe through CWM), and it removed CWM and replaced it with the stock recovery. I needed to use the phone for another 12 hours before my new one arrives this afternoon, so I added my account and a couple apps, but before mailing it back I plan to do a factory reset (through the stock ROM) and tell it to format the internal SD. After that, is there any trace of my mods that might void the warranty? I greatly appreciate AT&T's program where you get the new phone first, then mail back your old one within 14 days. But I don't want to get an email or call in 2-3 weeks telling me they deemed my warranty void, and I need to return the new phone. Has anyone ever had a problem with warranty exchange after root or custom ROM?
The only thing that sorta worries me is when the phone is put into download mode (power plus vol up), it says:
-----
ODIN3 Download Mode
(Protocol v2.1)
Reason: Force Key
Secure mode: Secure
Check Signature: Check
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
Waiting USB Cable...
------
My concern is with "Custom Binary Download: Yes (1 counts)". Is this giving AT&T/Samsung evidence that I flashed a custom ROM, possibly voiding my warranty? Is there a way to reset that?
Thanks for any tips on the reset/warranty procedure.
Ive sent back 3 rooted phones, one running cm7 (moto backflip). They don't seem to care that much about root or even a custom Rom.
Sent from my SGH-I927 using xda app-developers app
Good to know. I'm probably over-thinking it, just want to make sure. The guy on the phone from AT&T sure was easy to convince that I needed a new phone. I originally had battery issues (suddenly went from 75% to 5%), so he mailed me a brand-new battery overnight. That solved the battery issue, but I continued to have really bad GPS reception (see attachment, this was while standing outside on a clear day). The rep actually called me to see how my phone was after the battery was replaced, told him I was still having GPS problems, he ordered me a new phone without any questions. Should arrive at my desk at work any minute now...
You didnt have to through troubleshooting stuff? They have always done that for me and my family.
Sent from my SGH-I927 using xda app-developers app
Yeah, I figured I would have to jump through all sorts of hoops. All the guy asked me is if I had the latest version of ICS, and I said no (technically, I didn't, I was on LiteROM 0.6). He said once I get the new battery, do a software update, then check the GPS signal. When he called 2 days later to ask about the battery, all I said was that I updated to the latest ICS, and my GPS reception is still very poor. He asked nothing more, just initiated a new phone coming my way. Maybe they have a big push internally for better customer service, and if so, they definitely get my thumbs up.
Heck, a couple weeks ago I had an online chat with AT&T about the fact that I was missing my corporate discount on 2 of my lines. I had been overcharged about $70 over the course of 10 months. The person couldn't fix it online, so she asked me if they could call me, and a "discount specialist" spoke with me. She couldn't re-apply the discount over the phone (said I had to go into my local AT&T store), but immediately offered me a $250 "courtesy credit" for the inconvenience. Sounds good to me!
And the new beast has arrived. Showed up with no battery, sim or back cover. Also came running Android 2.3.6. Ah well, I'll have all that fixed soon.
Dang, in download mode, it says "Custom Binary Download: No (0 counts)".
Ah well, I'm sure it will be fine.
how is gps now after having the phone replaced and reflashed ?
Waaaay better. Locks my position very quickly, strength in GPS Test is much improved. Glad I swapped it out while under warranty. Now just to get the old one accepted without issue. Should be fine.
Back to loving my phone. Now to figure out a good case before this one gets dropped. That's where a slider is a pita, with a 2-piece case.
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........
I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have a 9 month old S3 (T999/Canadian/Mobilicity Variant)
I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. I could manage a reboot if I pulled the battery.
I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.
It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.
Last night the phone was working on AOKP 4.2.2 while on the charger. I woke up and noticed it was hard locked, so I batt pulled, rebooted and went to sleep.
Now (this morning) it wont boot at all. I thought maybe it was the charger or the battery. I swapped batteries with a different S3, mine still does not boot.
So. What now?
Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?
Have you tried Odin? Plug it into a computer see if things register if so go further with Odin.
I'd say that and see if it persist while on a stock then don't install your apps, if problem still persist call Samsung or whom ever and see about that. Or get it up and running and if steady put on Craigslist then get s4....
T-Mobile SGS III
mt3g said:
Have you tried Odin? Plug it into a computer see if things register if so go further with Odin.
I'd say that and see if it persist while on a stock then don't install your apps, if problem still persist call Samsung or whom ever and see about that. Or get it up and running and if steady put on Craigslist then get s4....
T-Mobile SGS III
Click to expand...
Click to collapse
It used to be that when connected to PC Device man said: SGH-T999
Now the phone is connected via usb cable, but isnt booted and it says: QHSUSB_DLOAD
AMRivlin said:
It used to be that when connected to PC Device man said: SGH-T999
Now the phone is connected via usb cable, but isnt booted and it says: QHSUSB_DLOAD
Click to expand...
Click to collapse
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
mt3g said:
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
Click to expand...
Click to collapse
QHSUSB_DLOAD means your need JTAG. Because it's bricked.
mt3g said:
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
Click to expand...
Click to collapse
That is found on XDA and the interwebs as a bricked device. it applies to captivate/HTC/s3 others.
I downloaded odin, but I can't get into download mode Power+Home+VDown (Nothing happens)
I didn't flash an incorrect ROM, since my phone was working, it bricked itself over night? Power Surge?
Aerowinder, if I am under warranty, can i take it to my carrier/samsung for repair? I can't get into Download mode.
Call them up and find out. It might be failing/tired internals/hardware... Did you have your phone over clocked at all in the 9 months, just curious?
T-Mobile SGS III
AMRivlin said:
Aerowinder, if I am under warranty, can i take it to my carrier/samsung for repair? I can't get into Download mode.
Click to expand...
Click to collapse
I had the exact same problem and was still under the warranty and they exchanged it. I just told them that I plugged my phone before going to bed and when I woke up I wasn't able to turn it back on.
I actually remember this now. This a bug not common but its here for users on all D2 SIII decices... They've publically admitted it
T-Mobile SGS III
No over clocking.
Jan-April 30th Touchwiz 4.1.1 (Frosty ROM) Lockups Started monday (No Changes)
May 1 AOPK 4.2.2 ROM (Hard Lock/Brick today)
Time to find a receipt
AMRivlin said:
No over clocking.
Jan-April 30th Touchwiz 4.1.1 (Frosty ROM) Lockups Started monday (No Changes)
May 1 AOPK 4.2.2 ROM (Hard Lock/Brick today)
Time to find a receipt
Click to expand...
Click to collapse
Ya I suggest just avoiding the headache of trying to fix, tell them you plugged it in over night to charge and now its completely dead and that its been acting weird for a while before. You should be good.
T-Mobile SGS III
rener78 said:
I had the exact same problem and was still under the warranty and they exchanged it. I just told them that I plugged my phone before going to bed and when I woke up I wasn't able to turn it back on.
Click to expand...
Click to collapse
Not sure how this is going to turn out. The carrier refused to do the warranty, and gave me the # to samsung canada. I went to the Samsung Canada store, where they took the phone and gave me a GNexus (loaner)
So... lets hope they dont see the romming, my triangle should be 0.
If they do figure out my romming and their quote to fix is absurd, I will get HTC1 and repair the S3 on my own time.
I prefer Apple's warranty to be honest.
Does anyone know how much 3rd party Brick repair should cost? In the crap chance Samsung gets me for ROMing
AMRivlin said:
Does anyone know how much 3rd party Brick repair should cost? In the crap chance Samsung gets me for ROMing
Click to expand...
Click to collapse
Mobiletechvideos does it for $60.
http://mobiletechvideos.mybigcommerce.com/
Sent from my SGH-T999 using xda premium
Update:
7 days after submitting for service, the phone came back from a 3rd party repair shop in Burnaby, BC. PBA replaced due to bad BGA (Ball Grid Array)
So I guess they couldn't boot it to see the root.
Working fine. The new phone came back carrier locked, original unlock # worked again.
Da Kine said:
Mobiletechvideos does it for $60.
http://mobiletechvideos.mybigcommerce.com/
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Some kijiji advertisements are charging $49.99 same day repair.
ysr84 said:
Some kijiji advertisements are charging $49.99 same day repair.
Click to expand...
Click to collapse
Managed to get it repaired under warranty.
can u help me out
AMRivlin said:
Managed to get it repaired under warranty.
Click to expand...
Click to collapse
Did you buy the warranty when u bought the phone?
I have the same issue. But not sure where to send the galaxy too?
Please help coz the local stores were not able to help
JBn
Help
AMRivlin said:
I have a 9 month old S3 (T999/Canadian/Mobilicity Variant)
I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. I could manage a reboot if I pulled the battery.
I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.
It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.
Last night the phone was working on AOKP 4.2.2 while on the charger. I woke up and noticed it was hard locked, so I batt pulled, rebooted and went to sleep.
Now (this morning) it wont boot at all. I thought maybe it was the charger or the battery. I swapped batteries with a different S3, mine still does not boot.
So. What now?
Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?
Click to expand...
Click to collapse
I Hard Bricked my Samsung Galaxy S3 and if you dont mention anything about rooting they will give you a new one no questions asked. Now if you dont have a warranty or some type of insurance then call samsung and see what you can do about it. i did a warranty exchange and i got a new one. As long as you dont mention brick or root you will be find they will right it down as defective.
It took about a week between sending it in and getting it back. The issue I had was that the note would not reboot if you pulled the battery and reinserted without having to connect it to the charger. Before I sent it in, i flashed back to stock using ODIN. I checked the status of the repair and it said they had replaced a component. I wasn't sure if they were going to do anything since I had tripped KNOX counter.
**The kicker**
I got it back today and immediately went into download mode and to my surprise, KNOX was reset to 0X0!! I know they said they were going to flash it back to stock when they got it, but i didn't think KNOX could be reset (even by them).
people211 said:
It took about a week between sending it in and getting it back. The issue I had was that the note would not reboot if you pulled the battery and reinserted without having to connect it to the charger. Before I sent it in, i flashed back to stock using ODIN. I checked the status of the repair and it said they had replaced a component. I wasn't sure if they were going to do anything since I had tripped KNOX counter.
**The kicker**
I got it back today and immediately went into download mode and to my surprise, KNOX was reset to 0X0!! I know they said they were going to flash it back to stock when they got it, but i didn't think KNOX could be reset (even by them).
Click to expand...
Click to collapse
Maybe they swapped the whole board?
Mine went in tripped and came back reset also and it said they replaced a component. Mine had a non working SD card slot, i figured that replacing that part would but the phone still has the same serial number and imei number, plus I had used the region unlock and it was still in place and the software wasn't even reset.
Compusmurf said:
Maybe they swapped the whole board?
Click to expand...
Click to collapse
Nice. Maybe the programmer geeks here will figure out how they did it and make everyone else one.
Not that I care about KNOX and wish it would just die already.
bookmonke said:
Mine went in tripped and came back reset also and it said they replaced a component. Mine had a non working SD card slot, i figured that replacing that part would but the phone still has the same serial number and imei number, plus I had used the region unlock and it was still in place and the software wasn't even reset.
Click to expand...
Click to collapse
Same here. Used region lock away before and it sim unlocked my note. I got the unlock code from tmobile but didn't even have to use it. Unlock was still in place when I got it back
Sent from my LG-E988 using xda app-developers app
Same here. I sent it to Tmobile tripped and I got a replacement 0x0
Thing is, the Knox warranty gets voided by a private key missing from the bootloader. Most likely, they are just flashing it back to stock with the signed bootloader, hence returning it back to 0x0.
Sent from my SM-N900T using Tapatalk
noobtoob said:
Thing is, the Knox warranty gets voided by a private key missing from the bootloader. Most likely, they are just flashing it back to stock with the signed bootloader, hence returning it back to 0x0.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes but this goes a long way to proving that it isn't an efuse as has been suggested in the past and has been shot around as being a fact by so many. An efuse wouldn't ever be able to be reset. Since its being reset, there is a possibility (no matter how small) of figuring out how to reset the bootloader so that it is signed when it gets sent in for warranty or traded in for JUMP.
EtherealRemnant said:
Yes but this goes a long way to proving that it isn't an efuse as has been suggested in the past and has been shot around as being a fact by so many. An efuse wouldn't ever be able to be reset. Since its being reset, there is a possibility (no matter how small) of figuring out how to reset the bootloader so that it is signed when it gets sent in for warranty or traded in for JUMP.
Click to expand...
Click to collapse
I agree. I never thought it was an e fuse myself. But private keys are nearly impossible to crack, unless released, which I doubt Samsung is going to leak.
If they put an e fuse in the phone, they would lose money replacing parts during their manufacturer warranty.
But, here's to hoping it does get cracked one day...:beer:
Sent from my SM-N900T using Tapatalk
Even if it is an e fuse they probably able to just solder in a new one.
If software then they simply flash the code and it resets.
We just need to talk to someone there. I know its hard to get a hold of anyone let alone get this info out of then.
But cool you guys got it back reset.
I think it is like the HTC One tampered bootloader setup.
Just give it time and we will have a way to reset it.
Yeah there is a tread in the international note 3 forum about this same thing. Couldn't find it with tapa but the topic was quite a few pages long last time I checked. Appears Samsung had the ability to rest it with their magic equipment.
Sent from my SM-N900T using Tapatalk
There could be many possibilities here:
1. They replaced the whole device, motherboard, or CPU. The motherboard contains the CPU which supposedly contains the efuse. Replace the whole board with a fresh stock board and it will be reset. They definitely have the ability to load your old unit's serial number/IMEI/etc. onto the new board if need be.
2. The Knox flag is an efuse, but there are backup fuses. They could have set it so that a tripped fuse can be "reset" by blowing yet another fuse, which in turn would make the knox flag look at yet another fuse for the status. Since efuses are likely just one-time programmable memory there's probably millions of potential fuses in the chip. OTP memory is often available in the hundreds-of-KB to MB range on integrated CPU chips like this.
3. The Knox flag isn't an efuse, but rather a bit in EEPROM or Flash memory. If this is the case, they can reset it by just erasing the secret location that holds this status. It's possible the CPU has a small bit of EEPROM memory inside that could hide the bit from being found in the main EMMC flash. I have no idea if this is the case on this particular SoC though.
I highly doubt the efuse is a soldered on discrete component they could just replace. For one, it would have been found on the board during teardowns and two, I'm sure we'd be seeing "knox reset services" offering to replace the blown fuse for a price. Plus it would increase cost, something no high volume manufacturer want to do.
Mine bricked flashing from Wicked 4 to 5, couldn't Odin stock back and my backups wouldn't work either. T-Mo overnighted me a new one after the tech at the store tried to boot it up a few times.
noobtoob said:
Thing is, the Knox warranty gets voided by a private key missing from the bootloader. Most likely, they are just flashing it back to stock with the signed bootloader, hence returning it back to 0x0.
...
Click to expand...
Click to collapse
No, that is not accurate - that theory was tested by re-programming the flash directly with JTAG programmer and it failed on Qualcomm-based devices where something IS stored in qfuses (but there are rumors it might work on Exynos-based devices and the latest generation of JTAG programmers that can also access the "invisible" partitions of flash.).
I agree someone on here will cracked it
Sent from my SM-N900T using XDA Premium 4 mobile app
DAD12345 said:
I agree someone on here will cracked it
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
While I'm all for enthusiasm, positivity and support for the community I think you should ask Verizon modders and Moto modders.
Aside from the fact that as we find exploits that only makes the next exploit increasingly more difficult to come across (as we are pointing out the weaknesses in their systems in the process, effectively helping to harden the security wielded against our own community...for good and evil), if this e-fuse thing ends up being what a lot of us suspect it is (or, worse yet, what they claim it is) then there ain't much to "crack," sadly.
Thankfully this has the potential to be an extremely elaborate system. The more elaborate it is the more vulnerabilities will exist for it. Though, again, as we exploit vulnerabilities we are only helping them to harden the system against future compromises of said security.
...There is a very high likelihood that in the not-so-distant future we'll have to just get a Nexus device to ensure custom ROMability...and that's assuming that El Goog doesn't turn to teh evilz outright.
Either way, here's hoping for the best.
Someone posted earlier about trading in a device with Knox tripped concerned about JUMP upgrade eligibility. I would say it isn't an issue, as a T-Mobile Retail Sales Rep not a damn person in store would even know what Knox was anyways, and the people who did would not care if it were tripped.
Sent from my SM-N900T using XDA Premium 4 mobile app
people211 said:
It took about a week between sending it in and getting it back. The issue I had was that the note would not reboot if you pulled the battery and reinserted without having to connect it to the charger. Before I sent it in, i flashed back to stock using ODIN. I checked the status of the repair and it said they had replaced a component. I wasn't sure if they were going to do anything since I had tripped KNOX counter.
**The kicker**
I got it back today and immediately went into download mode and to my surprise, KNOX was reset to 0X0!! I know they said they were going to flash it back to stock when they got it, but i didn't think KNOX could be reset (even by them).
Click to expand...
Click to collapse
I was having issues with my Note 3. (Unit becoming unresponsive intermittently) After trying to clear cache(s) and reverting back to stock via Kies, as well as not installing any apps, AND having it freeze on me during initial setup, it became clear that the device had an issue. Sent it to Samsung (Plano,TX) and the technical assigned it a "BER" (Beyond Econimical Repair) status. They shipped it back the same day and received it via UPS exactly a week later from when I mailed it out. In detail, they didn't even touch it because Knox was voided.
Not giving up, I went to a TMobile store and told them the symptoms and replicated the issue. I also mentioned that Samsung wouldn't fix it due to Knox being tripped. The manager at the store was helpful and explained to me that TMo has a warranty exchange program separate to the manufacturers. So, he verified that it was a TMobile phone (checking IMEI) and ordered a replacement Note 3. I paid the $20 processing fee. I would then simply have to send the defective unit back. I asked about Knox begin tripped. He stated that as long as there isn't any physical damage (screen) or water damage, that I shouldn't be liable for anything else. (He inspected the unit and deemed it was free of those things)
Anyway, he did mention that the unit could be a new or refurb depending on what they had in stock. I told him that it didn't matter as long as it the replacement works. We'll see... The unit arrives in five days.
That makes me feel great incase mine ever breaks. I cannot live without root.
Sent from my SM-T520 using XDA Premium HD app
EtherealRemnant said:
Yes but this goes a long way to proving that it isn't an efuse as has been suggested in the past and has been shot around as being a fact by so many. An efuse wouldn't ever be able to be reset. Since its being reset, there is a possibility (no matter how small) of figuring out how to reset the bootloader so that it is signed when it gets sent in for warranty or traded in for JUMP.
Click to expand...
Click to collapse
There's a thread on the T-Mo JUMP! here in he general section that corroborates instances of JUMP! and warranty returns not affecting warranties. In fact, I sent my knox tripped N3 back to T-Mo on JUMP! warranty replacement last month without incident.