Related
Hi folks
My Touch HD digitiser has gone faulty and its only 6 months old
or at least thats what i thought because the screen was not responding to touch. i am a electronic technical person so not totally naive.
I was using the wonderful NRG roms with no problems whatsoever.
I tried to replace the stock rom and spl before sending it back to HTC, but i had no way of checking it throughly because i could not get it past the calibrate screen.
Htc now want £159.00 to replace the motherboard, and they state the reason as the unit having foreign firmware installed which damaged the motheboard.
now the Htc touch HD was working perfectly apart from the fact that the screen would not respond to touch. and i admit it would run a little warm at times but nothing excessive. It has nerver been dropped. does anyone think that a complete motherboard would need to be replaced because of "foreign firmware"?
Is Htc trying to rip off their customers?
clearly the xda developers are just enhancing an already great product with their releases of wonderful firmware
this is clearly a hardware fault and not software.
please wade in with your opinions
hi, I totally agree with your statement, but if you restored the stock boot loader and then the stock rom you could say that you tried to do and hard reset of the device and because the screen didn't work you were unable of calibrating it. I think they can't prove that you used a different rom.
hope you solve soon.
greets,
Nicola
omniajet13 said:
Hi folks
My Touch HD digitiser has gone faulty and its only 6 months old
or at least thats what i thought because the screen was not responding to touch. i am a electronic technical person so not totally naive.
I was using the wonderful NRG roms with no problems whatsoever.
I tried to replace the stock rom and spl before sending it back to HTC, but i had no way of checking it throughly because i could not get it past the calibrate screen.
Htc now want £159.00 to replace the motherboard, and they state the reason as the unit having foreign firmware installed which damaged the motheboard.
now the Htc touch HD was working perfectly apart from the fact that the screen would not respond to touch. and i admit it would run a little warm at times but nothing excessive. It has nerver been dropped. does anyone think that a complete motherboard would need to be replaced because of "foreign firmware"?
Is Htc trying to rip off their customers?
clearly the xda developers are just enhancing an already great product with their releases of wonderful firmware
this is clearly a hardware fault and not software.
please wade in with your opinions
Click to expand...
Click to collapse
Unfortunately HTC can legally stand by their clauses with foreign software on device as having a cooked rom on device voids warranty. I know you tried to restore back stock, but you couldn't tell and if appears they have still found your NRG rom on device.
However they are hiprocrites as this does not affect the motherboard and they are just lOoking for any excuse to void warranty which unfortunately you provided.
I believe others have been in your shoes before and posted similar threads. Try searching for these and see if they can shed any light.
but how can they get away with that?
If you buy a computer (which is what the Touch HD effectivly is), then you are entitled to use any operating system you whsh. wether it be Linux, Windows or Apple MAC. and if you develope a hardware fault then this cannot invalidate your warranty???
I dont get it? also how can they say it needs a new motherboard when it is clearly the digitser which has gone wrong?
omniajet13 said:
but how can they get away with that?
If you buy a computer (which is what the Touch HD effectivly is), then you are entitled to use any operating system you whsh. wether it be Linux, Windows or Apple MAC. and if you develope a hardware fault then this cannot invalidate your warranty???
I dont get it? also how can they say it needs a new motherboard when it is clearly the digitser which has gone wrong?
Click to expand...
Click to collapse
I believe someone else asked this same question in another thread, though which one I have no idea. They asked similar question about how does HTC get away with this and I believe (if my memory bank is working) they wrote a letter to them and where able to still get it under warranty (don't hold me to this though) as they argued a new rom wouldn't affect digitizer. Possibly worth having a search for if you can find it.
omniajet13 said:
Htc now want £159.00 to replace the motherboard, and they state the reason as the unit having foreign firmware installed which damaged the motheboard.
Click to expand...
Click to collapse
That Sucks.
A friend of mine had a similar problem,
He had a broken microphone,
and HTC sent a similar letter =>
You'll probably find that the digitizer is on the motherboard. Looking at it, it doesn't look like it can be separate. (Where would it fit?)
It does run a bit hot sometimes and heat is bad as you would know.
I have just read the warranty information and it states that the warranty is limited to the hardware as originally supplied,and makes no mention of any software or operating system. and by the very nature of the product it was made for installing third party software, operting system of choice ect.
in fact it reads " this limited warranty applies only to the hardware components of the product as originally supplied and does not apply to any software or other equipment".
I will persue this and post the outcome
Unfortunately "Software" and "Firmware" are two separate things. While you can install any operating system on your computer, that software isn't a part of the hardware.
In the case of smart phones (windows mobile phones), the operating system is Firmware, and not software. The difference here is that the Firmware is PART of the hardware. Similarly the bios rom on your computer is part of the motherboard hardware. To clarify, software is interpreted and run by hardware. On the other hand, firmware operates the hardware which is why changing to an unapproved firmware also means altering the hardware.
Unfortunately they have this clause in the warranty because you CAN destroy your hardware with a malicious rom, just like you can fry your harddrive, cpu and stuff with a malicious rom on your computer bios. You can have umpteen viruses or malicious 3rd party apps on your device and nothing it does can harm the hardware because it doesn't actually change how the hardware itself works. Firmware is different in that it changes internally how a piece of hardware works and in doing so, can damage it.
I do agree though, that in this case they're looking to void the warranty, but the truth is that the money they loose on one device under warranty must be covered by the profits made by 20+ other sold units (remember, revenue can just go towards warranties).
Hey man, you play the game, sometimes you lose. I took my phone apart, fallowed the factory service manual to the letter but I knew there was a good chance they would notice the missing "void" stickers and I had to pay for the repair ( for the problem that was there before I took it apart). I took it apart and that voids the warranty, so is life...
Hello all,
My name is Mike and I'm new to XDA forums. My question may seem a bit random and I'll ask it at the risk of sounding like an idiot. Is my Nexus One rooted?
I purchased my first unlocked N1 on January 5th and lost it on April 25. (Some one is potentially happy somewhere.) I don't typically lose expensive play things but this night involved copious amounts of alcohol.
I digress. Upon receiving my replacement N1 (replaced through ADH/Loss insurance), I noticed a large unlocked padlock icon on the boot screen with the multi-colored X. This icon was not present on my first N1. Additionally, I thought it strange that the following apps were pre-installed on my device: AnySoft Keyboard, DevTools, Spare Parts, Super User Permissions, Terminal Emulator. Also, my track ball glowed different colors depending on the type of notification.
Previously in the About Phone section of Settings, I was able to check for updates but with my new N1 it's not an option. My phone info goes as follows:
Firmware Version: 2.1update1
Kernel Version: 2.6.33-cyanogenmod
Mod Version: CyanogenMod-5.0.4.1-N1
I'm familiar with rooting but never planned on doing it to my own device. I follow tech blogs religiously so when word of Froyo (Android 2.2) OTA updates came out, I figured I should know whether I'd receive it automatically or have to force it on like I did prior to losing my phone with multi-touch.
So after my short story I ask, is my N1 rooted or is the norm (Mod & Kernel Versions)? If it is, I'll start researching ways to take it back to stock form for the OTA update. If it's not, I will feel like more of an idiot.
Yes, it's rooted.
And it's running a custom mod (CyanogenMod).
its rooted
by replacement do u mean u bought it from google or ebay
Wow, It was actually sent to me from Assurion, my insurance provider. I should've mentioned that earlier.
I thought so. Thanks for the quick, speedy responses guys.
So, it looks like I'm now apart of the modding community because I like what I've seen, especially the trackball notifications. Thanks for the warm introduction.
It's not the latest version of CyanogenMod, so if you like it and want to keep using it, I'd recommend updating it. You can download cmupdater in the market.
Are you not slightly miffed that they've clearly sent you a used phone with possible warranty issues?
Actually Rusty, I am.
I have a busy day today but tomorrow will likely be an epic day as far as phone conversations with customer service goes. What bothers me is that I figured something was amiss with the phone at the initial un-boxing but I chalked it up to me forcing 2.1 on my original Nexus and possibly not receiving the full update. It's been two weeks. Hopefully, they don't assume I performed the root.
I find it amusing that the very people that would void my warranty/insurance claim if I performed the rooting myself sent me a rooted phone. However, I'm also happy that because of this "mishap" I'm free to explore the worlds of modding without concern for warranty voids.
Today, I will figure out the best approach for resolving this issue with customer service (T-Mo, Asurion, HTC...whoever). I'll keep you posted.
So I called T-Mo and Asurion and they have no idea what "rooted" meant. They assumed I was mispronouncing refurbished. Whatever the case, I had them notate the account and I recorded their info.
Once again thanks for your help. I've already updated to Froyo as of a few minutes ago. Life is good.
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
btonetbone said:
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
Click to expand...
Click to collapse
we're stuck on verizon's firmware. i use viper and the software is updated to the latest release, just not using the eu/intl firmware.
btonetbone said:
Hey everyone -
Apologies if this has been asked before, but a simple search didn't turn up results. Verizon (surprise surprise) is already lagging behind on firmware updates. For those of us who are S-Off, unlocked, and on custom ROMs, is it possible to flash an updated firmware (such as 1.80.617.1) and still use our phones? Or are we stuck on Verizon's release cycle for firmware updates?
EDIT - I meant to post this in the Questions & Answers section, my apologies. If any mods want to move it, please feel free.
Click to expand...
Click to collapse
If you are on Verizon you should be using Verizon firmware. Just because a version number is different doesn't mean it's ahead. They are different forks tested and tweaked for entirely different networks.
Sent from my HTC6545LVW using Tapatalk
dottat said:
If you are on Verizon you should be using Verizon firmware. Just because a version number is different doesn't mean it's ahead. They are different forks tested and tweaked for entirely different networks.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
But does that hold true when flashing the Verizon radio behind the other firmware?(not challenging your statement here, just asking a variation of the OP question)
I think that is the main thing people want to know when this topic comes up. I've seen the question and information on it scattered in pieces across multiple threads, but never fully answered by being backed with a report by someone who did it.
So you don't think I am one of those that just sits back to let someone else do the work - I am willing to try such a thing by flashing the US unlocked or Europe FW followed by the VZW radio you pulled, but would need a little guidance in terms of how to provide feedback. Test signal before/after? I know from Viper thread loss of camera is something to watch out for. Any other specific items/parameters to check before/after? Since Viper just did a re-base, I have been searching and debating between those two FW anyway. First the Euro to match the ROM, then the US because they have the ROM flashing on all FW out at the moment.
camparks said:
But does that hold true when flashing the Verizon radio behind the other firmware?(not challenging your statement here, just asking a variation of the OP question)
I think that is the main thing people want to know when this topic comes up. I've seen the question and information on it scattered in pieces across multiple threads, but never fully answered by being backed with a report by someone who did it.
So you don't think I am one of those that just sits back to let someone else do the work - I am willing to try such a thing by flashing the US unlocked or Europe FW followed by the VZW radio you pulled, but would need a little guidance in terms of how to provide feedback. Test signal before/after? I know from Viper thread loss of camera is something to watch out for. Any other specific items/parameters to check before/after? Since Viper just did a re-base, I have been searching and debating between those two FW anyway. First the Euro to match the ROM, then the US because they have the ROM flashing on all FW out at the moment.
Click to expand...
Click to collapse
So here's the thing... you will see unlocked users who simply flashed the radio complain they often get stuck on 3g/1x. You will see the posts about the camera loss. You will see things about loss of volte. The firmware is always optimized for the rom/carrier for which it was written. They won't include vzw fixes in unlocked firmware since that phone isn't targeted for use on the vzw network.
Between the rom and the firmware it's really just a different fork altogether. They aren't mean to be used without each other as a dependency.
Euro firmware will likely have some odd wifi side effects for some folks as they use different bands over there.
dottat said:
So here's the thing... you will see unlocked users who simply flashed the radio complain they often get stuck on 3g/1x. You will see the posts about the camera loss. You will see things about loss of volte. The firmware is always optimized for the rom/carrier for which it was written. They won't include vzw fixes in unlocked firmware since that phone isn't targeted for use on the vzw network.
Between the rom and the firmware it's really just a different fork altogether. They aren't mean to be used without each other as a dependency.
Euro firmware will likely have some odd wifi side effects for some folks as they use different bands over there.
Click to expand...
Click to collapse
So can we back up just a bit to where I believe this all stems from - Is the HTC 10 truly a single-hardware phone? Therein, making all "variants" manifested only by which firmware is flashed? Is that true globally? If not, is that true for all in a particular "zone"(Europe, Asia, US, etc.)?
Ok, with the Euro FW the issues are apparent, given different standards not only for cellular, but also the camera and wi-fi vary from those here in the US. Even if one were to flash a US carrier radio, the camera and wi-fi issues could still pop up. Moving on from that consideration.
For US unlocked, there should be no standards issue, correct? Assuming hardware is the same for atleast all US carriers, what besides the radios would differ between carriers when not running stock ROMs?
Obviously there would be issues when on stock ROMs due to custom apps, features, etc. that would break not only when running different non-stock FW, but also when running one carrier's stock ROM on another carrier's network. All that is ill-advised and goes back to you only recommending stock FW.
Thanks for discussing this. I do not question your advise at all, I just want to explore the what and why of it all to put it all in one place. Thanks for humoring me and my questions!
camparks said:
So can we back up just a bit to where I believe this all stems from - Is the HTC 10 truly a single-hardware phone? Therein, making all "variants" manifested only by which firmware is flashed? Is that true globally? If not, is that true for all in a particular "zone"(Europe, Asia, US, etc.)?
Ok, with the Euro FW the issues are apparent, given different standards not only for cellular, but also the camera and wi-fi vary from those here in the US. Even if one were to flash a US carrier radio, the camera and wi-fi issues could still pop up. Moving on from that consideration.
For US unlocked, there should be no standards issue, correct? Assuming hardware is the same for atleast all US carriers, what besides the radios would differ between carriers when not running stock ROMs?
Obviously there would be issues when on stock ROMs due to custom apps, features, etc. that would break not only when running different non-stock FW, but also when running one carrier's stock ROM on another carrier's network. All that is ill-advised and goes back to you only recommending stock FW.
Thanks for discussing this. I do not question your advise at all, I just want to explore the what and why of it all to put it all in one place. Thanks for humoring me and my questions!
Click to expand...
Click to collapse
Hardware wise most are the same. And you are right about me recommending firmware that matches your carrier. That aside, my experience has been like this....
I have been asked a couple times to try to fully convert a phone from one carrier to another. On the 10, we know that unlocked<->verizon works and we thought it would since HTC gave them the same MID (different CIDs though). On the m9, I have attempted to fully convert a verizon m9 to an ATT model. The RUU flashes everything BUT tp and one or two other ones. It boots up fine (att death star and all)... but it will never boot to recovery and never load TWRP when flashed. There's something about the overall partition structure that makes it different.
On the rom/firmware front.... Verizon and HTC do very specific testing for firmware/OS releases. They do this not only to ensure optimal performance for the user, but also to make sure that the phone itself doesn't cause issues on the network itself. As the manager of an engineering team for a huge US based ISP, I can tell you that firmware of devices CAN and DOES impact the network stability from time to time. I'm not talking about capacity issues, I'm talking about your phone making a phone call and causing a network card back at the CO/Tower/ETC reset. It does happen.
Lastly, I measure things by what you gain. What would gain by flashing unlocked or EU firmware images onto a phone on the verizon network? An increase in number version? As much as I see people who change their aboot do so to avoid red text, it always surprised me to see a VZW phone with a third X.X.401.X number on their bootloader indicating non-vzw firmware. There's a new piece of fun around since the m9 and present on the 10. If you manage to get an aboot on your phone doesnt match your firmware and you reboot the phone you will be stuck in bootloader with no access to download/recovery and often OS. The only fix is to manually flash each firmware image / partition file by name manually and it must match the aboot for it to work. So that's another reason to not go and mix and match because to be honest... most people don't make it beyond the panic moment of that. That phone gets returned and added to the reasons verizon makes it more difficult going forward.
\
There's my 2 cents
If you are using any N7 port rom. You need to read below linked post.
This guy's imei was blacklisted because showing as Note 7. :crying:
This was on Nemesis rom but I'd beware on all N7 roms.
I came across this and wanted to share and inform you all.
http://forum.xda-developers.com/showpost.php?p=70078576&postcount=1053
Only thing i don't understand, i thought when a phone was produced, it is given a range of imei numbers. So these companies should be able to determine this isn't true Note 7.
aaron74 said:
If you are using any N7 port rom. You need to read below linked post.
This guy's imei was blacklisted because showing as Note 7. :crying:
This was on Nemesis rom but I'd beware on all N7 roms.
I came across this and wanted to share and inform you all.
http://forum.xda-developers.com/showpost.php?p=70078576&postcount=1053
Only thing i don't understand, i thought when a phone was produced, it is given a range of imei numbers. So these companies should be able to determine this isn't true Note 7.
Click to expand...
Click to collapse
Just asking
Can the developers of N7 ports deal with this issue?
My note 4 is all I have.
Can't afford to mess it up
natibongo said:
Just asking
Can the developers of N7 ports deal with this issue?
My note 4 is all I have.
Can't afford to mess it up
Click to expand...
Click to collapse
I don't know about the devs.
But these service providers and also samsung should be able to tell not to do this. They shouldn't just read 1 value (like ro.build.model) from build.prop to determine if it's a note 7. All they would need is a script to read a few hardware values to tell is not a true note 7. Plus i always thought your imei was coded to certain models. So no matter what rom you have, your imei will show as a note 4. That's what didn't make sense to me in that post.
But either way, i wanted to share it. So precautions could be taken.
aaron74 said:
If you are using any N7 port rom. You need to read below linked post.
This guy's imei was blacklisted because showing as Note 7. :crying:
This was on Nemesis rom but I'd beware on all N7 roms.
I came across this and wanted to share and inform you all.
http://forum.xda-developers.com/showpost.php?p=70078576&postcount=1053
Only thing i don't understand, i thought when a phone was produced, it is given a range of imei numbers. So these companies should be able to determine this isn't true Note 7.
Click to expand...
Click to collapse
Considering that carriers are supposed to be able to block a single phone via IMEI (if that phone is stolen, for example), it stands to reason that they're supposed to be unique per phone - no two note 7s should have the same number, let alone two phones with different models
So if there's a custom rom out there that is changing everyone's IMEI to the same number, the blacklist in this case might not have anything to do with whether it's a Note 7 IMEI - using the same IMEI on two devices at the same time should raise red flags
styles420 said:
Considering that carriers are supposed to be able to block a single phone via IMEI (if that phone is stolen, for example), it stands to reason that they're supposed to be unique per phone - no two note 7s should have the same number, let alone two phones with different models
So if there's a custom rom out there that is changing everyone's IMEI to the same number, the blacklist in this case might not have anything to do with whether it's a Note 7 IMEI - using the same IMEI on two devices at the same time should raise red flags
Click to expand...
Click to collapse
Exactly, kinda what i meant is, they shouldn't be turning off your phone because of build.prop properties showing as N7. It should all be done by imei.
But that post had me worried, cause he makes it sound like his phone was shut down just for having N7 port rom. Which should not be the case. Unless there's something going on there we don't know about (like changed imei)
Thanks for your input. Cause i was trying to ease my mind about running these roms.
My thought and conclusion on this, is these roms should be fine to run, unless you change or mask your imei to show as a N7. Unless these carrier tech guys are stupid enough to use a script that only detects your build id. Which shouldn't be how it's handled.
aaron74 said:
Exactly, kinda what i meant is, they shouldn't be turning off your phone because of build.prop properties showing as N7. It should all be done by imei.
But that post had me worried, cause he makes it sound like his phone was shut down just for having N7 port rom. Which should not be the case. Unless there's something going on there we don't know about (like changed imei)
Thanks for your input. Cause i was trying to ease my mind about running these roms.
My thought and conclusion on this, is these roms should be fine to run, unless you change or mask your imei to show as a N7. Unless these carrier tech guys are stupid enough to use a script that only detects your build id. Which shouldn't be how it's handled.
Click to expand...
Click to collapse
He never said that it was due to a build.prop value, so I'm not sure where you got that - he specifically said that it was because of the IMEI
styles420 said:
He never said that it was due to a build.prop value, so I'm not sure where you got that - he specifically said that it was because of the IMEI
Click to expand...
Click to collapse
He really didn't say what caused it, just that the IMEI was black listed: "The (AT&T) representative was adamant that the phone imei had been blocked by TMobile, but a call to them confirmed that while at&t put in the blacklisting, reported the phone as stolen as soon as Nemesis ROM registered a note 7 to their system yesterday night, and that there was nothing in their system they could do to unblock the imei. Long story short, after explaining the concept of custom Roms to the rep, at&t has put an unblock request in to be resolved by the 14th, hopefully it works, and just a word of warning to everyone!
PS. I had also changed build.prop product model to SM-G935F shortly after installing yesterday, so the red flag must've gone into their system as soon as it went online. Maybe developers need to stop putting the N9300 as the product model stock to avoid this!!"
It's hard to tell if the fact that he changed the model in the build.prop is what caused the blacklisting. I wonder if he had it properly unlocked from T-Mobile to use it on AT&T? That could have been part of the problem. I was told once, by T-Mobile, that the original owner of a phone had to request the unlocking, on T-Mobile. One thing I do know, is that it is illegal to take an IMEI from one phone and put it on another phone. For example, say you had Note 4, with a broken digitizer. You bought a working, but blacklisted Note 4. Then took the IMEI from your original N4 and put it on the blacklisted one. That's illegal. I fail to see how it would even work if you had 2 different models of phone, though. Or maybe, that was, indeed, what caused the blacklisting. OTOH, people have been porting ROMS from different models forever, and no one has complained of this that we've heard of. As we all know, there were Note 5 ports, as well as S7 ports...
smarcin said:
He really didn't say what caused it, just that the IMEI was black listed: "The (AT&T) representative was adamant that the phone imei had been blocked by TMobile, but a call to them confirmed that while at&t put in the blacklisting, reported the phone as stolen as soon as Nemesis ROM registered a note 7 to their system yesterday night, and that there was nothing in their system they could do to unblock the imei. Long story short, after explaining the concept of custom Roms to the rep, at&t has put an unblock request in to be resolved by the 14th, hopefully it works, and just a word of warning to everyone!
PS. I had also changed build.prop product model to SM-G935F shortly after installing yesterday, so the red flag must've gone into their system as soon as it went online. Maybe developers need to stop putting the N9300 as the product model stock to avoid this!!"
It's hard to tell if the fact that he changed the model in the build.prop is what caused the blacklisting. I wonder if he had it properly unlocked from T-Mobile to use it on AT&T? That could have been part of the problem. I was told once, by T-Mobile, that the original owner of a phone had to request the unlocking, on T-Mobile. One thing I do know, is that it is illegal to take an IMEI from one phone and put it on another phone. For example, say you had Note 4, with a broken digitizer. You bought a working, but blacklisted Note 4. Then took the IMEI from your original N4 and put it on the blacklisted one. That's illegal. I fail to see how it would even work if you had 2 different models of phone, though. Or maybe, that was, indeed, what caused the blacklisting. OTOH, people have been porting ROMS from different models forever, and no one has complained of this that we've heard of. As we all know, there were Note 5 ports, as well as S7 ports...
Click to expand...
Click to collapse
I know the build.prop isn't a factor - custom rom developers have used a different device model for various reasons without issue (I've seen it used in order to allow apps to be downloaded from the play store that were incorrectly marked as incompatible with that device, by changing the build.prop model to that of a device that was compatible with the app)
I seriously doubt that a developer included his own (or anyone else's) IMEI in a custom rom - they either know better, or they brick devices with the various other similar mistakes they would make. Besides, there wouldn't be just one user with this issue...
The most likely scenario is that the user tried something questionable with his IMEI and wants help fixing the mistake/bad decision without having to admit what really happened
styles420 said:
I know the build.prop isn't a factor - custom rom developers have used a different device model for various reasons without issue (I've seen it used in order to allow apps to be downloaded from the play store that were incorrectly marked as incompatible with that device, by changing the build.prop model to that of a device that was compatible with the app)
I seriously doubt that a developer included his own (or anyone else's) IMEI in a custom rom - they either know better, or they brick devices with the various other similar mistakes they would make. Besides, there wouldn't be just one user with this issue...
The most likely scenario is that the user tried something questionable with his IMEI and wants help fixing the mistake/bad decision without having to admit what really happened
Click to expand...
Click to collapse
First of all i agree with your last sentence and there is definitely something going on with his IMEI between AT&T and T-Mobile. that the part of the equation that is a bit fishy to me. I don't think he was completely forthcoming with his IMEI situation to begin with.
Another thing, the IMEI is never part of any device's flashable software package. Ever. This stuff get's written to EFS and other databases after the flash and during the initial rom setup and activation process so no rom chef can or will include any EFS or IMEI information into any rom. that simply makes no sense.
I also agree that blacklisting in this situation with the recalled N7 should be handled by IMEI databases and not solely on the devices "reported" device model over the network. That's how blacklisting is typically done in situations of lost/stolen devices or when you file an insurance claim on the device. The insurance company and the carrier enter the device's serial numbers into the IMEI blacklist database so they cannot be activated on that network. I can only assume that all network providers are going to honor Samsung's request to deactivate all N7's as well as it being banned by the FCC which also requires carriers to remove these devices from the stores and prevent them from working on their networks. Carriers have a legal obligation to follow these laws and guidelines set forth by the FCC. Period.
So in my opinion we should technically be able to use ported N7 roms on other devices with the build.prop device model etc to the values of that of the N7 variants and not have to worry about our phones' IMEI getting blacklisted. But I have already taken the precaution and changed the build.prop values in my current Sprint N7 port rom (still in final testing phase) just to be safe. I may test the N7 device model in build.prop once the "deactivation" date passes and see what happens. I have two N4's so I can deal with it if my phone incorrectly gets blacklisted due to running a port rom.
tx_dbs_tx said:
First of all i agree with your last sentence and there is definitely something going on with his IMEI between AT&T and T-Mobile. that the part of the equation that is a bit fishy to me. I don't think he was completely forthcoming with his IMEI situation to begin with.
Another thing, the IMEI is never part of any device's flashable software package. Ever. This stuff get's written to EFS and other databases after the flash and during the initial rom setup and activation process so no rom chef can or will include any EFS or IMEI information into any rom. that simply makes no sense.
I also agree that blacklisting in this situation with the recalled N7 should be handled by IMEI databases and not solely on the devices "reported" device model over the network. That's how blacklisting is typically done in situations of lost/stolen devices or when you file an insurance claim on the device. The insurance company and the carrier enter the device's serial numbers into the IMEI blacklist database so they cannot be activated on that network. I can only assume that all network providers are going to honor Samsung's request to deactivate all N7's as well as it being banned by the FCC which also requires carriers to remove these devices from the stores and prevent them from working on their networks. Carriers have a legal obligation to follow these laws and guidelines set forth by the FCC. Period.
So in my opinion we should technically be able to use ported N7 roms on other devices with the build.prop device model etc to the values of that of the N7 variants and not have to worry about our phones' IMEI getting blacklisted. But I have already taken the precaution and changed the build.prop values in my current Sprint N7 port rom (still in final testing phase) just to be safe. I may test the N7 device model in build.prop once the "deactivation" date passes and see what happens. I have two N4's so I can deal with it if my phone incorrectly gets blacklisted due to running a port rom.
Click to expand...
Click to collapse
I use my note 4 outside US so I think there is no worry about blacklist since I use it in non-US CDMA carrier so I am waiting for your N7 rom with no worry ... And I hope that you include international languages to the ROM because the system apps included only 6 languages in their res folder.
Also WIFI HOTSPOT feature as always in your roms.
Thank you.
Here's the latest the guy posted over in the Nemesis thread:
"I'm following up, my debacle from the blacklisted imei / suspended service with AT&T continues (after installing this ROM). AT&T tech rep confirms all of my issues stem from actions lead by Samsung and automatically carried out by AT&T's system. Dev, please updated your build.prop to new update as maybe many of the new people flashing this rom are not getting service / data, as Samsung is becoming increasingly more aggressive and they have no way to tell if it's a real Note 7 or not, according to AT&T people..."
You'd think Samsung and the carriers have both the IMEI and it's corresponding model in their databases. But maybe they think that a Note7 owner could be desperate enough to keep their N7 and tried to reassign the IMEI from their Note 4 to a Note7. I know I really liked my Note7, but not THAT much! Also, we can probably safely discount that the AT&T tech rep really knew what he or she was talking about.
wel in any case i'm rebuilding my still unreleased N7 port and simply tweaking the build.prop and csc cures the N7 ban concerns. No worries on my end. I just need a little time to rebuild my rom from the latest softwares.
Funny I remember flashing a N7 port rom on my wife Note 4 from Verizon, when we had them.. When you plugged the phone into the computer, it would recognize it as a Note 7. I wonder why?
tx_dbs_tx said:
wel in any case i'm rebuilding my still unreleased N7 port and simply tweaking the build.prop and csc cures the N7 ban concerns. No worries on my end. I just need a little time to rebuild my rom from the latest softwares.
Click to expand...
Click to collapse
Take your time man. As much as I was hoping to see it released before this weekend I, along with others, will gladly wait patiently while you work on polishing this ROM. Looking forward to it! And many many thanks (can only press the thanks button once lol)
jbuggydroid said:
Take your time man. As much as I was hoping to see it released before this weekend I, along with others, will gladly wait patiently while you work on polishing this ROM. Looking forward to it! And many many thanks (can only press the thanks button once lol)
Click to expand...
Click to collapse
Me too! Many thanks. I'm sure it'll be great!
Also,
I'm still in disbelief that samsung or at&t would be so noobish to shut down a phone just by reading it's build.prop as a N7(or whatever the case was). Even if they were worried about just going by imei lookup, this just don't seem right. I'm sure they could run some remote script to read it's hardware or bootloader, or modem (I can go on), and know it's not a N7.
Has anyone heard of anyone else this happening to? I'm just thinking there was more to this story than getting blacklisted from flashing aN7 port.
Sorry to rant about this but i can't believe a tech that high up the chain would write code that simple, to allow this to happen.
aaron74 said:
Me too! Many thanks. I'm sure it'll be great!
Also,
I'm still in disbelief that samsung or at&t would be so noobish to shut down a phone just by reading it's build.prop as a N7(or whatever the case was). Even if they were worried about just going by imei lookup, this just don't seem right. I'm sure they could run some remote script to read it's hardware or bootloader, or modem (I can go on), and know it's not a N7.
Has anyone heard of anyone else this happening to? I'm just thinking there was more to this story than getting blacklisted from flashing aN7 port.
Sorry to rant about this but i can't believe a tech that high up the chain would write code that simple, to allow this to happen.
Click to expand...
Click to collapse
From what I can tell the network looks at the FCCID so unless you change that in the rom it will flag on the network and service will be terminated on the device.
tx_dbs_tx said:
From what I can tell the network looks at the FCCID so unless you change that in the rom it will flag on the network and service will be terminated on the device.
Click to expand...
Click to collapse
Cool, Thanks for the info. I'll have to remember that. Ive changed that in floating features before in another rom. But i only changed G to P, to denote sprint model. I'll remember to not change model#.
Any word on your roms arrival?
aaron74 said:
Cool, Thanks for the info. I'll have to remember that. Ive changed that in floating features before in another rom. But i only changed G to P, to denote sprint model. I'll remember to not change model#.
Any word on your roms arrival?
Click to expand...
Click to collapse
I'm rebuilding the rom as I type this. Lots of things i'm having to do to get the rom where I'm happy with it. As for the FCCID in floating features set it to that of the N5 variant and that will be good. Same in build.prop device model. Set that to N920P and that will do the trick and not have any negative effects on the rom. This is what I have done to my N7 test rom and tests have proven this to be the best workaround according to my test group who are running the rom as their daily for weeks now. Sorry about the delay with my N7 rom but I want it to be ready with little to no issues before I release it to the public. There's a lot on the line and I have to make sure peoples' phones will not be impacted by running this custom firmware. It seems to be perfectly fine and no loss of services yet. I will post when the rom is actually ready for a public release so not to keep people in suspense when the rom just isn't up to my standards yet.
tx_dbs_tx said:
I'm rebuilding the rom as I type this. Lots of things i'm having to do to get the rom where I'm happy with it. ....
There's a lot on the line and I have to make sure peoples' phones will not be impacted by running this custom firmware. It seems to be perfectly fine and no loss of services yet. I will post when the rom is actually ready for a public release so not to keep people in suspense when the rom just isn't up to my standards yet.
Click to expand...
Click to collapse
Thank you, I understand. I was not trying to sound impatient, just curious. No worries here! I empathize with the amount of time it must take to port and debug these TW roms.
I know you only release your roms stable and working great.
I'll be anticipating it's announcement. Thanks for your reply and heads up about everything else. :good:
tx_dbs_tx said:
I will post when the rom is actually ready for a public release so not to keep people in suspense when the rom just isn't up to my standards yet.
Click to expand...
Click to collapse
I have been refreshing the thread and searching on your posts for what seems like weeks now. I'm a bit anxious.
Brought S8 from Middle East .. relocated to India, started using it. Was installing and following Samsung Updates quietly up until two days back.
On Jul 1st after the last update, all sensors stopped working bare the Finger Print and the Camera.
Failed sensors I found out so far ... Proximity, Ambient Light, Magnetic, Accelerometer, Barometer, Compass, IRIS
Phone turned into a basic phone having Finger Print sensor.
All this for no fault of mine.
As you guessed, No warranty in India ... Only option given was to "Change the Motherboard" costing nearly half the price of the phone.
Not going to do this, as I have no trust whether this would fail in the next update.
Has anyone got solution / suggestions ?
What I tried
- Factory Reset / Cache wiping
- Taking to the service center and it seems they have flashed the "Correttt version"
- My CSC shows INS/INS/XSG
MORAL :- A Samsung update messes up their Flagship model so much.
do you update it using odin? or OTA?
have u roll back to stock?
leo31 said:
do you update it using odin? or OTA?
have u roll back to stock?
Click to expand...
Click to collapse
Updated using the OTA ... Did not roll it to stock as I was not so sure what to do.
Took it to service center and they say Motherboard (If there is such a thing) has been spoilt
did flash my phone with different pda and csc number which not belong to my country.
everything works fine here. just see couple apps that belong to mexican carrier.
i think the ota update that u did is still 'buggy' . roll back to stock, im sure it will fix all your problem.
leo31 said:
did flash my phone with different pda and csc number which not belong to my country.
everything works fine here. just see couple apps that belong to mexican carrier.
i think the ota update that u did is still 'buggy' . roll back to stock, im sure it will fix all your problem.
Click to expand...
Click to collapse
Thank you and I really wish it does.
Question
1. How to find the pda and CSC thats suitable for my phone ?
2. I have Smart Switch , how do I roll back ?
3. I see people referring to some third party Sammobile etc. If I do that , will it void my warranty in any way ?
4. Once I flash to a different country, will I still get updates or after that I am on my own ?
Attached is my Phone Summary , I am not sure if I understood CSC PDA that well.. Presume its INS
Also attached is the Software Version
AjitBharat said:
Thank you and I really wish it does.
Question
1. How to find the pda and CSC thats suitable for my phone ?
2. I have Smart Switch , how do I roll back ?
3. I see people referring to some third party Sammobile etc. If I do that , will it void my warranty in any way ?
4. Once I flash to a different country, will I still get updates or after that I am on my own ?
Attached is my Phone Summary , I am not sure if I understood CSC PDA that well.. Presume its INS
Also attached is the Software Version
Click to expand...
Click to collapse
let me answer to help :
1. based on your attachment, the pda should be start with your 4 last digit of build number, so it is CRF7. u can use and flash all the rom published for SM-G950F with pda number ended with the same 4 digit like yours (in this case CRF7). it wont break your phone, since the rom is the published for the same type of phone (SM-G950F).
CRF7 is global firmware. the csc number will follow the pda number. just find one which suited best for your daily and dont forget to read the changelog and review from user from xda.
2. u need to root first
3. sammobile is just a website that release official firmware for samsung. i download 8.0 update from that site too. its safe. warranty? the rom is in stock condition, so it wont void your warranty.
4. if samsung says they will give update to their device. they will give the update. no matter which country you choose, update will be given. its just about timing, when will u get the update to your device.
hope my answers will help u brother
leo31 said:
let me answer to help :
1. based on your attachment, the pda should be start with your 4 last digit of build number, so it is CRF7. u can use and flash all the rom published for SM-G950F with pda number ended with the same 4 digit like yours (in this case CRF7). it wont break your phone, since the rom is the published for the same type of phone (SM-G950F).
CRF7 is global firmware. the csc number will follow the pda number. just find one which suited best for your daily and dont forget to read the changelog and review from user from xda.
2. u need to root first
3. sammobile is just a website that release official firmware for samsung. i download 8.0 update from that site too. its safe. warranty? the rom is in stock condition, so it wont void your warranty.
4. if samsung says they will give update to their device. they will give the update. no matter which country you choose, update will be given. its just about timing, when will u get the update to your device.
hope my answers will help u brother
Click to expand...
Click to collapse
Clicked a Thanks for your help.
There are thousands who have been affected like this.
Some of them have actually tried downgrading to a previous version and that did not help either.
However shall take your advice and give it a shot in the near future.
Thank you once again. You guys help more than those Customer Care themselves
AjitBharat said:
Clicked a Thanks for your help.
There are thousands who have been affected like this.
Some of them have actually tried downgrading to a previous version and that did not help either.
However shall take your advice and give it a shot in the near future.
Thank you once again. You guys help more than those Customer Care themselves
Click to expand...
Click to collapse
if that not helping you, bring your phone back to samsung service center, tell them what u did is just updating the system by ota, which released by samsung itself. tell them your phone still on warranty, dont give a **** to their up-coming answers because it will not help you to solve your problem.
shout at them, you want your phone to get fixed on the same day, tell them you are not the only one facing that problem. dont forget to make video recording when you visit samsung service center. if they still dont want to do anyhing, and tell you to pay for board replacement, ask him/her to show their manager, now u can f*ck*ng throw your phone in the manager's face.
samsung release the update , the update broke the system, user need to pay for getting fixed. what the **** samsung
.. contd ... FINAL UPDATE ..
Samsung wont repair my phone for the damage they caused.
Getting reports that many have got their devices repaired free of cost after repeatedly pestering the customer care. Another Technician revealed that this is a ploy to deter people from buying phones from outside ... PLUS .... enroll existing customers for their Extended warranty program.
Meanwhile :- I am sending this piece of **** ..... back to the Middle East for repairs.
Conclusion :- Samsung messed up their "flagship" phone with their own updates. This happened to me, can happen to anyone (even after warranty) So stay safe and be careful.
Now I stand corrected why ppl invest mere 25K+ on Chinese brands that almost give flagship like features
leo31 said:
if that not helping you, bring your phone back to samsung service center, tell them what u did is just updating the system by ota, which released by samsung itself. tell them your phone still on warranty, dont give a **** to their up-coming answers because it will not help you to solve your problem.
shout at them, you want your phone to get fixed on the same day, tell them you are not the only one facing that problem. dont forget to make video recording when you visit samsung service center. if they still dont want to do anyhing, and tell you to pay for board replacement, ask him/her to show their manager, now u can f*ck*ng throw your phone in the manager's face.
samsung release the update , the update broke the system, user need to pay for getting fixed. what the **** samsung
Click to expand...
Click to collapse
You r right. A service center guy revealed that talk tough to the samsung customer care, pester them with phone calls and they might take responsibility.
AjitBharat said:
.. contd ... FINAL UPDATE ..
Samsung wont repair my phone for the damage they caused.
Getting reports that many have got their devices repaired free of cost after repeatedly pestering the customer care. Another Technician revealed that this is a ploy to deter people from buying phones from outside ... PLUS .... enroll existing customers for their Extended warranty program.
Meanwhile :- I am sending this piece of **** ..... back to the Middle East for repairs.
Conclusion :- Samsung messed up their "flagship" phone with their own updates. This happened to me, can happen to anyone (even after warranty) So stay safe and be careful.
Now I stand corrected why ppl invest mere 25K+ on Chinese brands that almost give flagship like features
Click to expand...
Click to collapse
yesterday i broke my a3. removing some of stock apps, and the phone suddenly going crazy, cant use camera, many apps are broken, like instagram, line messenger, many fc's here and there, and reflashing the stock nougat rom using odin, and then my imei is GONE w*f, i dont remember what i did, i do many flashing , cp only , bl only, csc only, combining ap & cp & csc from oreo and nougat, and the imei is back LOL
and yeah, do you have to pay for getting repair of your phone?
Yes I have to pay for repairs ... for a 6 month old device that Samsung Messed up. (around 40% of the price of the phone)
It seems Samsung does a lot of research on their phones and an update doesn't mess up anything.
When I pointed them to the hundreds of issues they round it off with "Sire u do not have warranty"
Some stuffs I tried without success
Recap :- The issues started after I downloaded the firmware
G950FXXU2CRF7_G950FOXM2CRF7 on Jul 1
Update :- After reading lots of stuffs, I downloaded the same firmware (but of XSG version) from Sammobile .. (download is a slow process)
Flashed it with ODIN .. - Knox doesn't trip and doesn't brick if you pay good attention to the instructions.
Result :- The sensors are still dead
So tried with the Firmware before the update of July 1st
i.e. G950FXXU2CRED_G950FOXM2CREB_XSG Sensors are still dead.
Did not go beyond that firmware as it has U1 instead of U2 .. not sure what that is but read somewhere you shouldn't go back to U1 once you are flashed with U2
NOTE :- Contrary to some videos for Odin with s8, the latest firmware flash wont work with odin 3.12.x. You will have to use 3.13.x (It has to do with the Firmware file compression)
Did a factory reset before and after the flash.
The only thing I did not try is removing the SIM before Factory reset.
Summary,
If SHAMsung customer care "advice's" you to downgrade and try .... They are wasting your time .... trying to void your warranty and these wont work anyways
Either they have some software patch that they can rectify this problem
OR else
..... give in and get your Motherboard changed (If you are like me without warranty in your country .. u r SOLJWF)
Conclusion :- I am going to send this trash back to the Middle East via my relative and keeping my fingers crossed.
The cost emailed by SCAMSung India is 20K+ INR with NO WARRANTIES for motherboard. Looking at their service centers there is a worry if they are capable to retain IP65 after opening it PLUS not sure if this would repeat.
So instead of all this, I could shell another 5 to 8K get phones like Vivo / Opo etc with equal or better features All within warranty.
To all those facing such issues, never spend additional money on these brands.
For those proud owner of S8 GALAXY, better start counting ur STARS
Unfortunate owner of S8
You do know, that THAT is excatly what Samsung excludes in their warranty conditions, right?
"Failure of the product arising from incorrect installation [...]
Unauthorized modifications carried out to the product in order to comply with local or international technical standards in countries for which this SAMSUNG product was not originally designed." (Official Samsung's warranty terms and conditions)
And yes, you did so.
Doesn't care if your S8 is an international version or not. Your phone was not meant to be used outside of the middle East. So your firmware/csc/whatever change made you lose your warranty in the first place. Second, you did flash some firmwares by yourself. No one can be sure, that you flashed it correctly (which I assume though). So next time, if Samsung asks you to reset or downgrade it, let them do it at a service point. Period. Then you can definitely say, you did nothing wrong. But, you altered the phone to work in India, which recaps to unauthorized modifications.
I understand, that it is a very unpleasing situation for you, don't get me wrong.
Even if everything worked fine before the 1st July update, you could have a bug in your phone, which just didn't come out to that time.
Some numbers for you: Samsung sold about 8 million copies of the S8 (plus). So even if "thousands of users report this problem", it's just about 0.01% of the actual users. It's sad for a company that big to wave off the customers like that. But believe me, with such a small number they just don't care enough. The high the number of faulty units seem, it's just too few to really think that it could be a malfunctioning update. Because, why do have thousands not working sensors when millions do not have problems? That's where the whole "altered system, you did something wrong etc." starts.
But what I would do, if Samsung denies me that (questionable) service: I would try to make charges and complains against the seller? I think that in your buying contract, there could be something like "promised working etc."
I work in a place, that has such problems every day. Customers who feel let alone from their company.
It's sad, but it's true. If the costs are to high to swap the faulty devices because the amount is so small, it just won't be done.
See Apple with their downsizing battery. They admitted the mistake (like Samsung could do sometime in the future with the motherboard), but they didn't offer a free repair, just cheaper.
In all your anger and disappointment, I hope I could let you see the other site of the problem.
Sent from my Galaxy S8 using XDA Labs
Just to avoid confusion for prospective readers in future.
You said
"Failure of the product arising from incorrect installation
Unauthorized modifications carried out to the product in order to comply with local or international technical standards in countries for which this SAMSUNG product was not originally designed." (Official Samsung's warranty terms and conditions)
My Response:-
Initially it was an OTA update. Maybe you did not read the thread. No where does Samsung say NEVER INSTALL OTA in a different country. Does it?
You Said
Doesn't care if your S8 is an international version or not. Your phone was not meant to be used outside of the middle East. So your firmware/csc/whatever change made you lose your warranty[/QUOTE]
.. and ..
Period. Then you can definitely say, you did nothing wrong. But, you altered the phone to work in India, which recaps to unauthorized modifications
My Response
So what does International version mean ?
You Said
Second, you did flash some firmwares by yourself. No one can be sure, that you flashed it correctly (which I assume though). So next time, if Samsung asks you to reset or downgrade it, let them do it at a service point
My Response
Yes they too tried it, and did a Shabby job too.
In the end Installed the XSG version myself and got it verified by Samsung Customer Care center here as well as from online tech support via their Remote assistance.
You Said
In all your anger and disappointment, I hope I could let you see the other site of the problem
My Response
No you didn't reveal anything I was unaware. Rather you failed reading the entire thread.
Read post #9 of this thread
The only reason why I didn't persist was, I have the option to send this trash back to the Middle East and claim warranty ... which I am going to do.
So
Whether Defects are 1% or .001%, Failures are Failures, I and many like me are affected while trusting a Global brand ... to help its customers.
FACT IS I invested in a Flagship phone, Trusted the Samsung Service personal stating "You will get all Assistance / Warranty anywhere"
Didn't read "Terms and Conditions" to verify that claim.
Another SHAMEsung device dies
My sister had brought S7 Edge along with my S8
Just few hours back, she called me to say her screen has turned Green..
I read a lot of reports online about this infamous "Green screen of Death" problems of Samsung phones. So much for investing in Flagship devices ..
Got my s8 Back
Update !!
I got my S8 back from the middle east and its working "AS OF NOW"
The report says , changed PCB 2 etc etc
Price paid ? 0$
Won the Trust back? Not yet !! I am not sure if I would do another Samsung Update.
Advice (For those who have s8 Note 8 etc )
- If you ARE under Warranty, go for all the Updates and you will have chance to get the problems fixed.
- If you ARE NOT under Warranty, Take your device to the nearest ShameSung service center and ask them to do the update for you.
Advice (For those who are planning to get s8 Note 8 and S7 edge)
- Please Dont !!
Except for the Camera, there is nothing Extra Ordinary.
Curved display is a gimmick, you will end up accidentally touching the sides while wondering why your menu ain't responding.
Tempered Glass always cracks from the sides.
IRIS Scanner doesn't work for some irises, Doesn't work for me at least
So !! there are better options to look into the market. Look what suits you and you will be happy to pay 1/3rd of the price, yet enjoy all the warranty and support.
Good Luck !!
So, If you are still under warranty
Is there any chance that a new update will fix this issue?
Sorry to be the one telling you this - You seem extremely butthurt and unaware of your own wrong doings.
Just because you had these self inflicted issues, you don't recommend the S8 to others? Boy please. It's people like you i advice to cross over to apple and iOS.
AjitBharat said:
Update !!
I got my S8 back from the middle east and its working "AS OF NOW"
The report says , changed PCB 2 etc etc
Price paid ? 0$
Won the Trust back? Not yet !! I am not sure if I would do another Samsung Update.
Advice (For those who have s8 Note 8 etc )
- If you ARE under Warranty, go for all the Updates and you will have chance to get the problems fixed.
- If you ARE NOT under Warranty, Take your device to the nearest ShameSung service center and ask them to do the update for you.
Advice (For those who are planning to get s8 Note 8 and S7 edge)
- Please Dont !!
Except for the Camera, there is nothing Extra Ordinary.
Curved display is a gimmick, you will end up accidentally touching the sides while wondering why your menu ain't responding.
Tempered Glass always cracks from the sides.
IRIS Scanner doesn't work for some irises, Doesn't work for me at least
So !! there are better options to look into the market. Look what suits you and you will be happy to pay 1/3rd of the price, yet enjoy all the warranty and support.
Good Luck !!
So, If you are still under warranty
Click to expand...
Click to collapse
Samsung Updates
Either you haven't read the complete thread ... or ... You did not understand what you just typed
Doing a Samsung Update is what everyone does and what Samsung and Android recommends.
Look around, there are hundreds of S8's and Note 8's affected with the update, and Samsung is rectifying them.
All on their flagship device ?
I have posted both for owners and Prospective buyers..
Lastly my Recommendations / suggestions are based on my experience.
Creedo4Life said:
Sorry to be the one telling you this - You seem extremely butthurt and unaware of your own wrong doings.
Just because you had these self inflicted issues, you don't recommend the S8 to others? Boy please. It's people like you i advice to cross over to apple and iOS.
Click to expand...
Click to collapse