So my friend owns a Redmi Note 11 Pro+ 5G device and on June 16 evening, he slept with the phone at 6%. Come morning, the phone is stuck at fastboot mode. He asked me for help and since I had a rooted phone myself, I thought of just simply booting it up again normally. It then showed this message
"Your device is corrupt.
It can't be trusted and may not work properly.
Press power button to continue.
Or, device will power off in 5s"
Of course I tried pressing power but it just kept showing the MI logo. So I rebooted to recovery and wiped data, still nothing. What should we do to fix it?
Now the recovery doesn't work at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WTF was your buddy thinking anyways ?
On a battery that's never been properly calibrated, you never ever want to let the device discharge below 10% -and even that level is probably pushing your luck..
My bet is that the device is good for a trip to the nearest service center.
Snakeforhire said:
WTF was your buddy thinking anyways ?
On a battery that's never been properly calibrated, you never ever want to let the device discharge below 10% -and even that level is probably pushing your luck..
My bet is that the device is good for a trip to the nearest service center.
Click to expand...
Click to collapse
Are all Redmi devices this brittle? Damn.
I never trust xiaomi phones. I always unlock the bootloader on them as soon as i can so i won't have surprises like yours and if i do i just flash the rom again.
Michael P. said:
I never trust xiaomi phones. I always unlock the bootloader on them as soon as i can so i won't have surprises like yours and if i do i just flash the rom again.
Click to expand...
Click to collapse
On that particular point it's rather the Qualcomm SoC that would be to blame -even though they are what they are by explicit demand from the OEMs who mass-buy them to integrate into their devices, and Google is of course happy to oblige with ever-tighter Android security models that make use of the hardware functions offered by the newer chipsets. It's a never-ending spiral of ever-increasing roadblocks to any develoment not coming from either the OEM or Google themselves, with the (voluntary or not, that is a matter of debate) collateral damage implicated to any 3rd-party devs or just the tech enthusiast...
I won't even mention Mediatek chipsets here -which are the bane of any self-respecting modder ever to venture into the Droid ecosystem... :/
But on the principle you are right : unless you explicitly need a locked bootloader (e.g. because you want to be able to RMA your device at any time while the warranty period is valid, or because it's a workplace-supplied phone that has to run "sensitive" company apps), it is always a worthwhile precaution to unlock, so you can at least access the ADB interface in case of trouble. Because it's not a question of "IF" trouble should appear, but more a question of "WHEN" it eventually occurs..
Can't tell for Xiaomi, never had one -not a real branded one anyways : they're flagship devices geared to fill the upper market brackets, so way too expensive for me.. But I've had 3 Poco devices up to rn (2x X3 Pros "vayu" and one X5 5G "moonstone"), and they're by far the best bang for the buck I've ever found. I even got to like the MIUI firmware, over time (the .EU version of it, that is). At least it runs without any issues on those devices without major bugs, something which cannot be said of many AOSP-based firmwares. And even POCO started out as a subsidiary of Xiaomi, they are their own independent brand that just happens to use Xiaomi-supplied parts in their devices, and Xiaomi's OS MIUI.
It's true that Xiaomi devices can be very frustrating sometimes (what with their waiting period to unlock your bootloader). Still, when compared to some other brands like Oppo or Nokia (who don't even provide a way to unlock their bootloaders and proudly and publicly boasts of this unwillingnessto be "open"), Xiaomi is rather "dev-friendly"... rofl
Snakeforhire said:
On that particular point it's rather the Qualcomm SoC that would be to blame -even though they are what they are by explicit demand from the OEMs who mass-buy them to integrate into their devices, and Google is of course happy to oblige with ever-tighter Android security models that make use of the hardware functions offered by the newer chipsets. It's a never-ending spiral of ever-increasing roadblocks to any develoment not coming from either the OEM or Google themselves, with the (voluntary or not, that is a matter of debate) collateral damage implicated to any 3rd-party devs or just the tech enthusiast...
I won't even mention Mediatek chipsets here -which are the bane of any self-respecting modder ever to venture into the Droid ecosystem... :/
But on the principle you are right : unless you explicitly need a locked bootloader (e.g. because you want to be able to RMA your device at any time while the warranty period is valid, or because it's a workplace-supplied phone that has to run "sensitive" company apps), it is always a worthwhile precaution to unlock, so you can at least access the ADB interface in case of trouble. Because it's not a question of "IF" trouble should appear, but more a question of "WHEN" it eventually occurs..
Can't tell for Xiaomi, never had one -not a real branded one anyways : they're flagship devices geared to fill the upper market brackets, so way too expensive for me.. But I've had 3 Poco devices up to rn (2x X3 Pros "vayu" and one X5 5G "moonstone"), and they're by far the best bang for the buck I've ever found. I even got to like the MIUI firmware, over time (the .EU version of it, that is). At least it runs without any issues on those devices without major bugs, something which cannot be said of many AOSP-based firmwares. And even POCO started out as a subsidiary of Xiaomi, they are their own independent brand that just happens to use Xiaomi-supplied parts in their devices, and Xiaomi's OS MIUI.
It's true that Xiaomi devices can be very frustrating sometimes (what with their waiting period to unlock your bootloader). Still, when compared to some other brands like Oppo or Nokia (who don't even provide a way to unlock their bootloaders and proudly and publicly boasts of this unwillingnessto be "open"), Xiaomi is rather "dev-friendly"... rofl
Click to expand...
Click to collapse
yeah, i do agree with that. same goes for realme too, they're less prick-ish when it comes to unlocking bootloaders. i unlocked mine under 15 minutes on my Realme C12, and now I don't get to use their stupid realme UI. as for my friend though, i had recommended rooting, or at least, unlocking the bootloader.. i just hope it's not too late for it now as there aren't lots of xiaomi technicians around my city (or any that i know of).
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing custom ROMs & warranty
Some assumptions:1. Law in each country is different (mostly based on common law (US & UK) nad civil law (continental Europe), but "warranty" term means more or less the same everywhere. In simple words it's a legal contract that is very often a part of legal transactions. Purchase agreement is not a warranty contract itself. Warranty always must be stated on the separate document. If you were not given warranty document then most probably you were not given warranty at all. Very often different sellers are misunderstanding warranty with consumer law that gives some separate claims for consumers, but it does not gives warranty.
2. So if warranty is kind of legal contract, it is based on freedom of contract. It means that a party that is the guarantor can write any terms he wants as long as they are valid with imperative law (lex imperativus).
3. Keep in mind that the same company can have different warranty terms in different countries. So the fact that your friend in the U.S. got brand new device after 3 unsuccessful repairs doesn't mean it's valid for you, a customer leaving in f.g. France.
4. Everyone who wants to know their warranty terms should read their warranty. Don't relay on what you read on the internet or even in this thread. I don't know your warranty. That's why my post have just a general context.
Now the main part. I'll try to make it as clear as possible.1. Read your warranty. Do it like 3 or 4 times.
2. Is there directly written that flashing custom operating system voids your warranty? I'm quite sure it's not. Do you believe that installing Ubuntu over machine with Windows 7 sticker voids notebooks warranty as well?
3. My experience is based on reading my warranty terms. In every warranty I saw there was a term about installing any software that comes from 3rd party company. That means it doesn't refer only to custom ROMs. That refers to Angry Birds as well. And Facebook, and Twitter, and SuperUser, and Instagram etc.. So... another question: do you believe that installing Angry Birds voids your warranty?
Well... it might have.
4. The most important thing here is the cause and the effect relationship. That means that the guarantor can reject your claim to repair broken device only when the fault is a direct effect of installing software that comes from 3rd party company.
Example: you flashed custom ROM over your Android device. All went fine. Then you installed Angry Birds and one of the birds broke your screen. Guarantor can reject your claim to repair broken screen. But not because of custom ROM you flashed and you sent your device back to service with custom ROM on board. But because of Angry Birds (of course he needs to proof that the fault is a direct cause of one stoned Angry Bird).
Digression: yes, the side that is rejecting your warranty claims needs to proof their affirmations on why they rejected it.
In short words: if the fault is not a direct cause of installing any software that comes from 3rd party company then your warranty claims are valid. Of course we speak just about the situation that refers to installing software. Once you throw your device from the 10th floor it's obvious that you can't say: "There is no direct cause of installing any software that comes from 3rd party company and the fault so you need to repair my device."
5. Now another interesting part - rejecting some warranty claim doesn't mean that warranty is no longer valid at all. Again - it depends on your warranty statements, but based on mine it works like this: let's say I broke my internal speaker by flashing some sounds boosters. Let's even say that guarantor proofed it (which is not really possible that he even would try to waste his time). So I have no warranty now? More likely - I still have. But I have no legal claims about the speaker anymore. Now let's say that one week later my CPU burned out with no reason. There was surely no direct cause between CPU and 3rd party software because I don't installed any CPU controlling/overclocking apps. Based on warranty terms written in my warranty I still have valid warranty for that and guarantor needs to repair my CPU.
Disclaimer:
This text is just for education purpose. It's not a law itself so you can't base your claims versus some company on this. I may be wrong in many parts - feel free to PM me and I will make corrections. I don't know law in every country so there might be some differences.
Stickied for the time being
I have a screen defect on my Moto X Style. Some red marks on the screen that have occurred. No physical damage has happened to the phone.
Details of the fault
https://www.dropbox.com/s/2atvxn7b5zlvo4e/IMG_20151110_122942.jpg?dl=0
https://www.dropbox.com/s/mkyf8sm6sq6vs6g/IMG_20151110_122946.jpg?dl=0
Entered their live chat to sort this out. They requested images of the defect via email. I promptly sent the images.
Had to keep pestering for a reply for two days.
They got back and asked where I bought the device from. I replied it was from them and give them an order number.
Next reply said that as the device was more than 28 days old they won't offer me a replacement (which totally flies in the face of all UK consumer rights).
So I complained about this and told them about their rights and responsibilities as a retailer.
Their next reply pulled up the fact I bootloader unlocked, suggesting this invalidates the Motorola warranty - which is right, but doesn't release them from their responsibility as a retailer and doesn't affect my statutory rights.
I told them of the above and told them I want to exercise my right to a replacement (I still like the device and want to keep using the Moto X Style)
They give me the complaints address and told me to send a letter to them.
This is really unacceptable behaviour from a company selling in the UK. If I buy a brand new laptop and immediately install Ubuntu (which I would do) this would invalidate the manufacturer warranty, but not my statutory rights. So if I had a software issue, or I wanted help recovering Windows, I'm out of luck, because I voided my warranty, but if the hardware breaks, my statutory rights are unaffected and the manufacturer is bound by legal obligation to repair, replace or refund (depending on the timescale).
Lesson? Always buy from Amazon! They never quibble over faulty devices. Instant refund or replacement.
To be impartial as an outsider. If the warranty is voided due to bootloader unlock, they aren't under any obligation to replace, isn't that correct?
I have the red thing also. And I didn't even bother trying for a replacement because I bootloader unlocked :/
paoloroeseke said:
To be impartial as an outsider. If the warranty is voided due to bootloader unlock, they aren't under any obligation to replace, isn't that correct?
Click to expand...
Click to collapse
In Europe and America, if the defect isn't software related (or hardware damage caused by a software issue), they are still supposed to fix hardware issues under warranty.
Thanks for the info
jeffreycentex said:
In Europe and America, if the defect isn't software related (or hardware damage caused by a software issue), they are still supposed to fix hardware issues under warranty.
Click to expand...
Click to collapse
Yep, this, which is the case I'm arguing with them now. The agreement on the website that voids the Motorola Warranty is invalid as it tries to invalidate statutory rights (which only a statute can void) and is keyed towards American laws (mentioning the FCC, etc). They can invalidate their own warranty if they want, but not my statutory rights.
Interesting that someone else also had the red thing on the display. Clearly this is a fault with the device, because I only ever installed Google Dialer and AdBlocking on my phone. I didn't touch any low-level settings in any shape or form.
Alternatively, I had a Nexus 6 (also by Motorola) which ran like a dream and was running an unlocked bootloader. None of these issues, but the camera was appalling, so I thought I was getting a better deal with the Moto X Style.
Good luck, stick it to them
@gmillz can you post pictures of the defect, please?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for bad pic quality. You can kind of see it
Sent from my LG-D800 using Tapatalk
@Op,
Sorry for you. i would sue motorola uk to official uk consumer laws office and take my money back in the end, show motorola a big middle finger and never see each other again.
Sent from my Nexus 6 using XDA Free mobile app
Can i make a suggestion.. Come over to Consumeractiongroup... They can help you
Im on there as fkofilee, if you make a post, ill dig out some info. With the changes to the SOGA, it means new rules apply
fkofilee said:
Can i make a suggestion.. Come over to Consumeractiongroup... They can help you
Im on there as fkofilee, if you make a post, ill dig out some info. With the changes to the SOGA, it means new rules apply
Click to expand...
Click to collapse
I should still fall under the SOGA, as I bought the device prior to Oct 1st. If I'm honest the new Consumer Rights Act is a huge step backwards, so I'm glad I'm under SOGA.
I have the red mark also but it isn’t noticeable unless i force a fully black screen.
I unlocked my bootloader before i noticed (maybe before it happened??). I’m not too bothered at the moment but if it gets worse then i might be a bit more interested in getting it sorted out.
Hi, i'm in Spain and today I called Motorola because i want to send my Style for repair because my screen has a vertical line of pixels that got unnoticed until yesterday, uneven backlit and the left side of the screen has a darker shade than the right. Their response over the phone? The repair is almost sure out of warranty and its up to their technician to repair under warranty or not because i unlock the bootloader but i told them that the EU law covers hardware problems that are not caused because software modifications and they told me that i could try. One of the most infuriating things is that i have to pay to send them the phone and they will not cover this expenses, unbelievable . And the icing on the cake is that they will not inform me of the status of the repair until i'll call them 7 days after i send the phone, and they don't have a tracking system in Spain. The phone it's great but this is my last Moto for sure.
Enviado desde mi XT1572 mediante Tapatalk
mrvanx said:
I have the red mark also but it isn’t noticeable unless i force a fully black screen.
I unlocked my bootloader before i noticed (maybe before it happened??). I’m not too bothered at the moment but if it gets worse then i might be a bit more interested in getting it sorted out.
Click to expand...
Click to collapse
Picture would be a great help, no matter how noticeable. 3 people with the issue so far is starting to be a good case.
I can get better pictures. I just gotta have an all black page.
Got an email form Motorola today. I'd been passed up the echelons of their corporate hierarchy to Motorola HQ:
Dear Mr. Booth,
Thank you for your patience.
We have decided to replace your phone exceptionally as an act of goodwill. We would like to send you a DHL label which will be valid for 5 days, so that your phone can be dropped off at a DHL drop off point. Once your phone has been received and processed by the repair centre, we will send you a new Xcode which you can use to order a new Moto X Style 64GB.
Could you please confirm your postal address and your phone number for me again so I can notify DHL?
Click to expand...
Click to collapse
This is basically their way of saying they will replace my phone without prejudice. I was right, my rights have been upheld, but no-one is going to admit it. But, I'll take it. I get a new Moto X Style. Now the decisions is whether to keep the replacement or not, because I will want to root.
If I do buy a new phone, it'll be from Amazon.
--
the unlocked bootloader was obviously directly responsible for the hardware issue. SMH
all of these moto cs horror stories..i hope i never have to deal with them.
Might want to take a look here. There are some sympathetic people in moto's forums that seem to be able to escalate these issues when the front line drones want to give you the run around.
You're probably right. However, I'm tired, busy, and I need my phone. I have lost all patience for Motorola CS. Although I might be able to escalate my case, I lack the effort needed to go through the process again, which would inevitably require me to jump through more hoops to cajole Motorola into enforcing its warranty. I found the part I needed (XT1575 Flex Cable Ribbon with Power & Volume Button ) and will just repair the phone myself. Although I appreciate the support of Motorola employees on that thread, the very existence of a thread dedicated to consumers trying unsuccessfully to return their phone don't give me much faith in the process. Thanks for the advice, anyways, though.
lomlomlom said:
You're probably right. However, I'm tired, busy, and I need my phone. I have lost all patience for Motorola CS. Although I might be able to escalate my case, I lack the effort needed to go through the process again, which would inevitably require me to jump through more hoops to cajole Motorola into enforcing its warranty. I found the part I needed (XT1575 Flex Cable Ribbon with Power & Volume Button ) and will just repair the phone myself. Although I appreciate the support of Motorola employees on that thread, the very existence of a thread dedicated to consumers trying unsuccessfully to return their phone don't give me much faith in the process. Thanks for the advice, anyways, though.
Click to expand...
Click to collapse
For the cost and time involved in *intentionally* voiding your warranty by opening your phone, you could literally post a thread in their forum and I'm sure they'll get you sorted.
lomlomlom said:
You're probably right. However, I'm tired, busy, and I need my phone. I have lost all patience for Motorola CS. Although I might be able to escalate my case, I lack the effort needed to go through the process again, which would inevitably require me to jump through more hoops to cajole Motorola into enforcing its warranty. I found the part I needed (XT1575 Flex Cable Ribbon with Power & Volume Button ) and will just repair the phone myself. Although I appreciate the support of Motorola employees on that thread, the very existence of a thread dedicated to consumers trying unsuccessfully to return their phone don't give me much faith in the process. Thanks for the advice, anyways, though.
Click to expand...
Click to collapse
If you open your Moto X you will need a new back cover too, because the way it is peeled of to get to the screws will damage it.
At the one side I think, if you want a open bootloader AND a no questions asked warrenty, you should buy a nexus or OnePlus. It's Motorolas right to do so.
But I don't understand why they handle this different in so much cases, one time its fine and there is an explaination that in the US non software related faults will be covered and the next time they refuse to repair a Volume Rocker even if you want to pay for it....
For the cost and time involved in *intentionally* voiding your warranty by opening your phone, you could literally post a thread in their forum and I'm sure they'll get you sorted.
Click to expand...
Click to collapse
That's not what I mean. I mean the time involved with sending the phone back to Motorola, where they can process it, would not be worth it. Here's an estimate based on my previous experience:
~3 days - Obtaining and shipping phone back to Motorola
~5 days - Motorola's processing time
~5 days - Evaluating and repairing device (assuming no other "problems" are encountered)
~3 days - Shipping back to me
That's over two weeks, as a bare minimum. As for voiding the warranty, by Motorola's standards, it's already voided. Even if my case is escalated in this case, if I ever have another problem, I will still run into the same problem with Motorola CS. If I never have another problem, the warranty doesn't matter, does it? The parts I need cost ~$30. I would rather pay $30 than wait at least two weeks in another attempt dealing with Motorola CS.
lomlomlom said:
My experience with Motorola RMA. Bought a Motorola X Pure (US) in early October, and rooted it soon after. Soon began to experience problems with volume rocker, so I RMA'd after about a week and a customer support call, my device was "received" (even though it had signed for a few days earlier). Four days after that, I received a second email containing a FedEx shipping number. Confused onto whether or not my device had been repaired, I used the support chat. The customer service rep told me that the phone will be sent back unrepaired, because the boot loader was unlocked. After asking whether or not it could be repaired off-warranty, the rep told me they would repair literally nothing (including crack screens, etc.) if bootloader is unlocked, even if customer is willing to pay for repair. Just though I'd share my experience. Don't bother with Motorola support if you've unlocked the bootloader. Although this isn't surprising, I'm quite dissapointed that Motorola will not repair completely unrelated hardware problems if the bootloader is unlocked, under any circumstances (and, even more importantly, this was not made clear until I had been without my phone for a week and a half). For me, this was enough to discourage future purchases of Motorola phones.
Click to expand...
Click to collapse
The new (2015) Moto X Pure is not a developer edition, so unlocking the bootloader does void the warranty. Sorry about the lack of clarity on this. We've been using this answer but I was double-checking it before posting.
To sum up and clarify:
Unlocking the bootloader will show your warranty as void.
However, if an unrelated physical material failure should occur, such as a bad volume rocker or a failed speaker, it will be covered if the phone shows no signs of physical abuse. The key is that the problem can't be traced to software or abuse.
These same principles apply to MotoCare Insurance (extended warranty).
The above guidelines are applicable in the US only. Policies differ by region/country.
I'll talk to the marketing team about improving our communications about this aspect of our phones. But as a rule of thumb, if it doesn't say "Developer Edition" then unlocking the bootloader is not supported by warranty.
Updated 9/23/15
https://forums.motorola.com/posts/cda80927a1
Same here, had digitizer issues and Motorola RMA wanted to change the PCB first and then look into it further. With a heat gun and some 3M tape you'll be able to re-use your current back cover.
stg87 said:
The new (2015) Moto X Pure is not a developer edition, so unlocking the bootloader does void the warranty. Sorry about the lack of clarity on this. We've been using this answer but I was double-checking it before posting.
To sum up and clarify:
Unlocking the bootloader will show your warranty as void.
However, if an unrelated physical material failure should occur, such as a bad volume rocker or a failed speaker, it will be covered if the phone shows no signs of physical abuse. The key is that the problem can't be traced to software or abuse.
These same principles apply to MotoCare Insurance (extended warranty).
The above guidelines are applicable in the US only. Policies differ by region/country.
I'll talk to the marketing team about improving our communications about this aspect of our phones. But as a rule of thumb, if it doesn't say "Developer Edition" then unlocking the bootloader is not supported by warranty.
Updated 9/23/15
https://forums.motorola.com/posts/cda80927a1
Click to expand...
Click to collapse
But a lot of people were claiming that it was just the software warranty that got voided after unlocking the bootloader.
Probably best bet was to get tradesquare insurance coverage on it.
But a lot of people were claiming that it was just the software warranty that got voided after unlocking the bootloader.
Click to expand...
Click to collapse
The rep said to me that the warranty (I assume in its entirety) is voided. I asked for transcript to be emailed to me, as one was with my previous conversation, but I have received no transcript two days later. Very suspicious Motorola. Anyways, it really doesn't matter what Motorola's policy is, all that matters is how they enforce it. It seems now that they are not honoring any service for unlocked bootloader.
So I got the phone back today . . .
This is what was included in the box:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my "Liquid-damaged" phone, which is clearly not liquid damaged:
(Sorry for low-res, its from my old phone).
So, seriously Motorola, WTF? It's marked that my warranty is NOT void, and blames the malfunction on Internal Liquid Abuse. This is absurd, and there's no way that anyone could blame the malfunction on liquid abuse. No where is it marked that it was not serviced due to bootloader. There's absolutely no way Motorola could have handled this worse.
Closed per OP request
I've noticed some unusual things regarding this Samsung Galaxy S10 I purchased from Amazon. I specifically wanted an AT&T branded phone so I could use the AT&T features. My old S7 International Version was unable to do so. I was first sent an unlocked phone, and it didn't work with the AT&T features. I sent it back and they sent me back what seemed to be an AT&T branded phone, because it shows the AT&T logo on boot and can use the features. I checked the IMEI number on one of those phone checker sites and it came up showing a completely different model and even processor phone than what I've got! I'm supposed to have a standard S10 (g973U) with a snapdragon chip, it shows an S10+ g975U with an exynos chip. AT&T shows it as such as well on the website when I look at my bill and profile. Looking at the phone itself it reports as a g973u though. I've heard that there are instances where phones might be blacklisted or stolen and have their IMEI's changed to hide what they are, and I'm afraid that this might be one of those. I was hoping to use it as a trade in with a Samsung Pre-Owned program to go up to an S20, but I don't want to get stuck with a bill and lose my phone if it turns out that that is the case. Is there a way to know for sure if that has happened with this phone? If so, I want to find a way to get my money back from the Amazon seller...
You within a certain period of time can return the phone to Amazon without stating reasons and get the purchase amount refunded : at least that's possible if you bought phone within the territory of the EU, you're EU citizien.
jwoegerbauer said:
You within a certain period of time can return the phone to Amazon without stating reasons and get the purchase amount refunded : at least that's possible if you bought phone within the territory of the EU, you're EU citizien.
Click to expand...
Click to collapse
Yes he can return it after purchase but it has to be in the same condition as when purchase this means if he brought it new than he used it which means well it's now used and not new than they won't accept return because it's not in same condition as when purchased
It was used when I purchased it. I'm interested in finding out if my phone is legitimate, or if it's been messed with somehow and isn't what they claimed it was. Why does it show up on multiple different IMEI checking websites as an S10+ exynos when it's supposed to be an S10 snapdragon? Either the database is incorrect, or someone flashed a different IMEI onto a stolen or blacklisted phone in order to make it work. I want to know if it's a simple mistake of the IMEI database being incorrect, or if it's a malicious issue where someone sold me a stolen phone. If it was, then I don't care about the condition of the phone for returning, I will pursue a return with Amazon on grounds of being sold something that wasn't what they advertised.
The global IMEI database gets fed by OEM when a phone gets placed on the market and before it gets connected to any network.
Device info such as CSC, baseband info and code name can all be faked, your best bet is to check the download mode (which is by turning of the phone, connecting it to your computer, and holding the volume down and bixby keys) , to exit download mode just hold the volume down and power buttons together for ~10 - 15 seconds
download mode will tell you the real model name of the device, U variants are snapdragon, and they are not easily unlockable, but it could be a reused IMEI from another device (those are written with specialty tools like chimera or z3box) and that can be problematic depending on the country. afaik 2 phones with the same imei cant be on the same network and they get black listed
if your model is F variant, or N then it is the exynos model, and not really AT&T, in that case you can return it just fine
Well, I've done some more digging. I realized that the IMEI was also printed on the back of the phone, albeit in microscopic print, but it does match what it shows in the software, so I guess that's good. That's probably hard to fake? I also downloaded this app to do some more digging: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en It shows what it should be, and also a refurbish check shows it's original AT&T. So I guess it's ok. I don't know why multiple IMEI check websites would show the wrong information if that is supposed to come from the manufacturer. I guess if it's a fake, it's a darn good one.
Oh, also did the download screen trick, it didn't actually show the model number. It does show Knox is not tripped and it says it's official samsung. So I guess that means it's all ok?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Upgrading Smartphones: To wait or to Upgrade?Nowadays almost everyone is using a smartphone , And almost every week a new smartphone is being launched. As far as I can imagine more than 90% of users should have an old smartphone . Old means not like an ancient one it means it's predecessor is already launched . So where do you belong ? In the 90% category or in the least 10% category ? Don't ask about me I am using an ancient one to be more specific I am still using Realme 2 pro because why not ?
Nowadays it's so hard to control the peer pressure of upgrading your smartphone Keeping an eye on the number of new smartphones coming to market every month and number of new techs / features introduced by the OEMs . So when you really need to upgrade your smartphone ? And did the upgrade is really worthy ?
Click to expand...
Click to collapse
Your old smartphone never becomes worse (it is as it is from the beginning) just the new launched phone is better than the old so it's our obvious psychological thought that our old smartphone is no more a good phone .
(image credit)
Here are some questions to ask yourself before you plan to upgrade your phone .
The first and foremost cause is you are either satisfied or not with your phone. By thinking this you must have to keep your emotions aside . Because you must have heard that "dil mange more" means we humans are never satisfied with something we always want better than the existing one .
Below are the some reasons which you must be noted when you planned to upgrade, with their pratical solutions too .
If your device didn't lasts throughout the day ? It's a obvious problem which everyone should have faced with their smartphones after one or two year of usages . But it's not a worthy reason to upgrade . You can simply visit to a service centre and replace the battery of your device.
Second you must have been run out of storage . It's another common reason but you know you can upgrade you storage by a external card or you can clear the trashes I mean unnecessary files from your internal storage. Storage space is never sufficent for anyone .
Third the software in your phone seems outdated . It's one of the most common problem some OEMs provides only one or two year of software upgrade which is really bad and you can't do anything they are not going to listen you by any means . You will ask what's the solution for this ? If you are really a tech geek and really want to know about all stuffs ( not a usual person ) then you must have to check the open source projects once . There is a whole lot of new things out there . You can get latest Android versions and security patches for your old devices too . This is how I am using my realme 2 pro with Android 12 .
Did you think there are any other reasons too which I forgot to note ? Please let me know in comment section .
Click to expand...
Click to collapse
When do you need to upgrade ?
First the most common one if it damaged physically and the repair cost is higher then expected then you must need a upgrade.
Second if the camera quality is not up to the mark and it really affects your day to day life .
Third if you can't find the parts to replace like battery, usb port etc then you must have to upgrade .
These are the some reasons where you must have to upgrade . What else you think must be included here ? Comment down your thoughts I am waiting for your response .
Click to expand...
Click to collapse
(image credit)when you planned to upgrade what will be your minimum requirements ?Now let's come into the final phase of this thread.
First you saw what are the reasons which are not worthy for upgrade , then I mentioned what are the reasons where you must have to upgrade , now finally when you planned to upgrade what will be your minimum requirements ? Let's talk about it .
Here I mentioned my minimum requirements if i am going to upgrade my smartphone . Keeping in mind the budget is around 15k to 25k .
Click to expand...
Click to collapse
It must have to be atleast 60hz amoled (good quality amoled though not inferior ramless amoleds ) . If 90hz amoled then it's like cherry on the cake . Hell no to lcd .
It must have a snapdragon seven series or higher processor . Or mediatek dimensity series . But snapdragon is always preferred by me .
It must have 6 gb or above ram and 128gb and above internal storage and the storage should be ufs 3.1 not usual emmc storage.
It should have atleast 4000mhz battery and supports fast charging I think fast charging is common now a days.
It should have atleast 3 years of Android update and should be launched with latest Android versions and the UI should be clean and bloat free.
These are my minimum requirements . I will consider this much when buying a new phone . What's your minimum requirements ? Let me know in the comment section . And after checking my requirements if you have to suggest a phone to me then what will it be ? Please suggest one I am planning to upgrade . It should be from any OEMs.
This much is for today. Hope you liked it , please hit the thumbsup button if you liked it. see you in upcoming thread .
Ta ta
Sujit Kumar Mishra .
Not everyone has the same needs; some people don't play games or do a lot of Web browsing on their phone, so they don't need any more features than that. I watch a lot of video and browse the Web; my Pixel 2 was quite sufficient for nearly 5 years, and I only upgraded to the Pixel 5 because the battery was at the end of its useful life.
I agree with the general principle of bloatware and a clean UI, which is why I bought a Pixel.
Please note that battery capacity is measured in milliamp-hours (mAh) not megahertz (MHz).
Lastly, security needs are largely subjective; someone who uses only a few trusted apps and doesn't do much Web browsing is much less likely to be a target of malicious software than someone who does. It is however a good idea to keep your device up to date.