Related
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.
Where exactly do you go to see the 0x0 or 0x1 flag?
Also, is warranty voiding the main concern? Is the 10.1 a 90 day or 1 year? Full of questions tonight, but thx in advance.
~Vol
Vol4Ever said:
Where exactly do you go to see the 0x0 or 0x1 flag?
Also, is warranty voiding the main concern? Is the 10.1 a 90 day or 1 year? Full of questions tonight, but thx in advance.
~Vol
Click to expand...
Click to collapse
Reboot into download mode:
Turn on tablet holding volume down and power button until the screen turns on. Press Vol up to continue. On the next screen you will see: Warranty Bit: 0. Once you root and flash stock recovery back this will turn to a 1.
The warranty is 1 year. And yes, it technically will be void after you do this. I still maintain that that if your screen dies or hardware button comes off that they can't blame software for it. Now if you brick your tablet by farting around with stuff you don't know how to do and then try to get Samsung to fix it then that is a different story. Only time will tell before we know how Sammy will handle this issue...
I actually chatted with Samsung tech support about the Knox trigger and the warranty and they said that if their techs see that the counter has been triggered, the warranty on the Note will become immediately voided. They did say, however, that they would still fix the Note for free if they determine that a part failure was not related to Root and other software tinkering.
So Rooting and using CPU & GPU overclocking apps, for example, completely voids the warranty and they won't fix it for free. But if the screen or some buttons fail and they determine that just Rooting was not the cause or related, then Samsung will still honor the warranty and fix the defective parts.
optimummind said:
I actually chatted with Samsung tech support about the Knox trigger and the warranty and they said that if their techs see that the counter has been triggered, the warranty on the Note will become immediately voided. They did say, however, that they would still fix the Note for free if they determine that a part failure was not related to Root and other software tinkering.
So Rooting and using CPU & GPU overclocking apps, for example, completely voids the warranty and they won't fix it for free. But if the screen or some buttons fail and they determine that just Rooting was not the cause or related, then Samsung will still honor the warranty and fix the defective parts.
Click to expand...
Click to collapse
So no need to worry :thumbup:
Sent from my SM-P600 using XDA Premium 4 mobile app
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.
is the us wifi versions bootloader unlocked by default?
i'd like to get cm on it asap.
k.electron said:
is the us wifi versions bootloader unlocked by default?
i'd like to get cm on it asap.
Click to expand...
Click to collapse
How can I tell?
Like most or all devices when you boot it up it would show a unlock icon on the bottom of the screen if the lock is closed its not unlocked
Sent from my Nexus 7 using xda app-developers app
There is no lock symbol on the boot screen.
Sent from my SM-T320 using Tapatalk
Then its prolly locked I know the past 3 devices I've had when I unlocked the boot loader it would show it every time I booted it up
Sent from my Nexus 7 using xda app-developers app
It is locked
Just went Into bootloader mode (odin) and Knox is there. So yes It is locked
very locked.
for those who like to tamper: there's a recovery firmware intended for the gtpab 8.4 for Ukraine available for download. Don't know if Kies works on this device yet.
But if you blow your device off the rails, this will get it booting again:
http://nasirtech.blogspot.com/2014/02/t320xxu1anb2-android-442-kitkat.html
Oh, my, this is better than I expected - it recovered /system but didn't blow out my personalization. Freaking wonderful!
If your device "recovery bootloops," by which I mean:
you try a Chainfire root from the snapdragon note 8 on the tab pro 8.4
your device boots and tells you that you're bad, that Samsung knows your bad, and then displays something like
"RECOVERY IS NOT SEANDROID ENFORCING...
Set Warranty bit : recovery"
and reboots you, here's the fix:
take your a slim object and starting at the USB port, pry the backing loose one snap at a time, working left to right along the bottom and around the lower corners on each side.
Now, gently, start to pry down each side.
You'll feel central resistance. That's because there's adhesive holding the backplate to an internal frame that laps over the USB connector. Gently pry that up.
Once you're about halfway down each side, you can see the battery connector - six wires, two each black, blue, red. Keep going; there is another point of resistance at the camera housing. Gently finesse that last after you have all the other snaps off.
Free the battery from the mainboard by prying up the connector, or unscrew the 4 screws holding it in place and use the battery's weight to free it from the mainboard.
Let the device sit about 30 seconds.
Reconnect the battery.
Hold the home, volume down and power buttons simultaneously to bring the device into download mode and recover using Odin or your tool of choice.
Once you've recovered, button it back up.
Well, if it's not unlocked it's very free about what it accepts. I did blow the Knox flag but I was able to upload modified system.img, recovery.img and cache.img without any problems. And I now have a persistent root.
Good point - the OS is locked to void warranty, but if the flashable system images are that simple to load, that's great. The onboard recovery won't load them and I don't think Kies will, either
But I think it's reasonable to say that the upgrade mode on the samsung devices is analogous to an unlocked bootloader.
stevedw said:
Well, if it's not unlocked it's very free about what it accepts. I did blow the Knox flag but I was able to upload modified system.img, recovery.img and cache.img without any problems. And I now have a persistent root.
Click to expand...
Click to collapse
Can you share with us how you got root on your tab 8.4? I just bought one and I love it but without root it feels weird.... Thank you
sent from my Nexus 7 with CM11
roustabout said:
Good point - the OS is locked to void warranty, but if the flashable system images are that simple to load, that's great. The onboard recovery won't load them and I don't think Kies will, either
But I think it's reasonable to say that the upgrade mode on the samsung devices is analogous to an unlocked bootloader.
Click to expand...
Click to collapse
Yes please share
Sent from my SM-T320 using xda app-developers app
CAR1977 said:
Can you share with us how you got root on your tab 8.4? I just bought one and I love it but without root it feels weird.... Thank you
Click to expand...
Click to collapse
As I said over in the root thread, I'm not going to share the actual image as it's probably likely to make your device explode in flames, and it will trigger the Knox flag. But basically I unpacked the stock recovery.img, added the CF Auto Root bits from another Samsung 4.4 device and the same with cache.img, packaged them up and flashed with ODIN. Once I had root, I re-flashed the original recovery and cache.
As the subject stated:
1. If I buy this tablet today, would it have 4.3? I don't want Kit Kat because of the SD card issue and VPN issue
2. The Home button is on the side. I now have an iPad Air for work and most of the time hold the tablet in portrait mode. With this tablet, wouldn't I keep accidentally touching the Home button and/or soft key?
lanwarrior said:
As the subject stated:
1. If I buy this tablet today, would it have 4.3? I don't want Kit Kat because of the SD card issue and VPN issue
2. The Home button is on the side. I now have an iPad Air for work and most of the time hold the tablet in portrait mode. With this tablet, wouldn't I keep accidentally touching the Home button and/or soft key?
Click to expand...
Click to collapse
1. Probably depends on what country you are purchasing the tablet in. I sell a lot of these in the US, and for the past 2 months, they have all had 4.4.2 out of the box. I assume it would be the same for any country that has had the 4.4.2 update released.
2. You can always rotate the tablet 180°. If you're holding it in your left hand, have the buttons on the right. If you're holding it in your right hand, have the buttons on the left.
Rotation is what I unhappily do.
Via my Note 3
blindmanpb said:
1. Probably depends on what country you are purchasing the tablet in. I sell a lot of these in the US, and for the past 2 months, they have all had 4.4.2 out of the box. I assume it would be the same for any country that has had the 4.4.2 update released.
2. You can always rotate the tablet 180°. If you're holding it in your left hand, have the buttons on the right. If you're holding it in your right hand, have the buttons on the left.
Click to expand...
Click to collapse
You mentioned you sell a lot of these. I assume you also deal with customer warranty issue?
I am just wondering because there is no root for the SM-P600 without tripping KNOX. If I root, KNOX tripped, and I need to send to Samsung for warranty, I am afraid Samsung will reject it and I am out of $600.
No, I don't deal with anything warranty-related, so I'm not entirely sure how that works.
However, I have heard varying reports on KNOX tripped devices and warranty status. Seems to be mostly luck of the draw. If there is no way that rooting could have caused the issue, it seems some people have still had their warranties honored. But this is just what I've heard, and isn't anything official.