Related
Hey All,
Dropped my XT-1056 after owning it 6 months -> black screen and what appears to be a boot-loop. Contacted Motorola, and apparently it is still covered under warranty. However I do have an unlocked bootloader & root, and therefore my warranty is void. What are the chances they will notice the unlocked bootloader before opening it up and send it back as-is? I have heard rumors that popping it in the micro (I know I know this will pop a few transistors and brick my phone) will render it inert, and they would most likely just replace the phone. I have also heard that the first thing they do in the RMA process is a factory reset, so they might not notice the unlocked bootloader.
Any thoughts on which way I should go?
Apologies if this is posted in the wrong place.
msuttie said:
Hey All,
Dropped my XT-1056 after owning it 6 months -> black screen and what appears to be a boot-loop. Contacted Motorola, and apparently it is still covered under warranty. However I do have an unlocked bootloader & root, and therefore my warranty is void. What are the chances they will notice the unlocked bootloader before opening it up and send it back as-is? I have heard rumors that popping it in the micro (I know I know this will pop a few transistors and brick my phone) will render it inert, and they would most likely just replace the phone. I have also heard that the first thing they do in the RMA process is a factory reset, so they might not notice the unlocked bootloader.
Any thoughts on which way I should go?
Apologies if this is posted in the wrong place.
Click to expand...
Click to collapse
What did you tell them happened?
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
msuttie said:
Hey All,
Dropped my XT-1056 after owning it 6 months -> black screen and what appears to be a boot-loop. Contacted Motorola, and apparently it is still covered under warranty. However I do have an unlocked bootloader & root, and therefore my warranty is void. What are the chances they will notice the unlocked bootloader before opening it up and send it back as-is? I have heard rumors that popping it in the micro (I know I know this will pop a few transistors and brick my phone) will render it inert, and they would most likely just replace the phone. I have also heard that the first thing they do in the RMA process is a factory reset, so they might not notice the unlocked bootloader.
Any thoughts on which way I should go?
Apologies if this is posted in the wrong place.
Click to expand...
Click to collapse
Also, you didn't mention if you tried flashing back to complete stock. Maybe you should.
drago10029 said:
What did you tell them happened?
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Also, you didn't mention if you tried flashing back to complete stock. Maybe you should.
Click to expand...
Click to collapse
Sorry I didn't elaborate. I told them I dropped it from pocket height, and when I picked it up the screen was black, and it appeared to be going through a boot loop (vibrating for a second, 10-15s pause, repeat). I did not mention the bootloader/root. I am currently trying to find a way to do a factory reset without the use of my screen, possibly through TWRP (if I can find a good set of screenshots) or some terminal commands. I believe I can get my phone to the bootloader by holding vol down + pwr for a few seconds, but have no way of confirming this, other than the fact that it stops the periodic vibrating. Still does not show it is connected to my PC, so I think Terminal is out of the question unfortunately.
msuttie said:
Sorry I didn't elaborate. I told them I dropped it from pocket height, and when I picked it up the screen was black, and it appeared to be going through a boot loop (vibrating for a second, 10-15s pause, repeat). I did not mention the bootloader/root. I am currently trying to find a way to do a factory reset without the use of my screen, possibly through TWRP (if I can find a good set of screenshots) or some terminal commands. I believe I can get my phone to the bootloader by holding vol down + pwr for a few seconds, but have no way of confirming this, other than the fact that it stops the periodic vibrating. Still does not show it is connected to my PC, so I think Terminal is out of the question unfortunately.
Click to expand...
Click to collapse
Dang that sucks, and I was about to recommend terminal. I think trying to connect and run abd commands thru linux or ubuntu might help. also just youtube a TWRP video, but MAKE SURE YOU ARE VIEWING THE CORRECT VERSION! lol if not that could be fatal.
---------- Post added at 10:19 PM ---------- Previous post was at 10:14 PM ----------
also the microwave thing don't sound like a good idea lol. Especially if you didn't purchase the accident proof warranty.
drago10029 said:
Dang that sucks, and I was about to recommend terminal. I think trying to connect and run abd commands thru linux or ubuntu might help. also just youtube a TWRP video, but MAKE SURE YOU ARE VIEWING THE CORRECT VERSION! lol if not that could be fatal.
Click to expand...
Click to collapse
Indeed it would be. Haha! Even it it was fatal, do you think they would open it up before doing software diags? Seems unlikely, but might be worth a shot.
Another alternative is that it is just a loose cable, and opening it up might be an easy fix. This however would definitely void the warranty, would it not?
msuttie said:
Indeed it would be. Haha! Even it it was fatal, do you think they would open it up before doing software diags? Seems unlikely, but might be worth a shot.
Another alternative is that it is just a loose cable, and opening it up might be an easy fix. This however would definitely void the warranty, would it not?
Click to expand...
Click to collapse
Also you gotta test on a good cable bro lol and the back USB port. That like an XDA rule or it should be! also microwave would melt the plastic on the moto X and could hurt you or your microwave so please don't do that. Cell phones have enough radiation and microwaves too.
Opening up would void that, unless you know what your doing. check some youtube videos as well. If you can get a stuff flashed at least, that would be the best bet to save yourself.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
WAIT A SEC!! You said you dropped unlocked your bootlader?? right? and THEN you called and asked about the warranty and they said it still in effect?
I'm only mentioning that because they're supposed to have record of unlocked bootladers, someone help on this? Or was it just a bad rep.
You def should double check with another representative. You did unlock through Moto's website right?
drago10029 said:
Also you gotta test on a good cable bro lol and the back USB port. That like an XDA rule or it should be! also microwave would melt the plastic on the moto X and could hurt you or your microwave so please don't do that. Cell phones have enough radiation and microwaves too.
Opening up would void that, unless you know what your doing. check some youtube videos as well. If you can get a stuff flashed at least, that would be the best bet to save yourself.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
WAIT A SEC!! You said you dropped unlocked your bootlader?? right? and THEN you called and asked about the warranty and they said it still in effect?
I'm only mentioning that because they're supposed to have record of unlocked bootladers, someone help on this? Or was it just a bad rep.
You def should double check with another representative. You did unlock through Moto's website right?
Click to expand...
Click to collapse
Nope. My coworker helped me through the unlocking process. He's done it a thousand times apparently, and it was my first, so I don't quite remember how he did it. Definitely not through Moto though. Told them I dropped it, was surprised when they said it was still covered, and am now going to send it off with all fingers crossed, and hope they don't send it back unfixed after a week.
Hell. Might be worth it to just drop the 200 for a new one. lol!
msuttie said:
Sorry I didn't elaborate. I told them I dropped it from pocket height, and when I picked it up the screen was black, and it appeared to be going through a boot loop (vibrating for a second, 10-15s pause, repeat). I did not mention the bootloader/root. I am currently trying to find a way to do a factory reset without the use of my screen, possibly through TWRP (if I can find a good set of screenshots) or some terminal commands. I believe I can get my phone to the bootloader by holding vol down + pwr for a few seconds, but have no way of confirming this, other than the fact that it stops the periodic vibrating. Still does not show it is connected to my PC, so I think Terminal is out of the question unfortunately.
Click to expand...
Click to collapse
That is what you told them, dropped... but what really happened?
Symptoms do sound like something I had when I flashed a bad logo.bin on my XT1060. Screen didnt' work, just vibrated every few seconds. I did manage to hold the power button to stop vibrating, and then managed to get the phone into fastboot mode and fix.
If you can get your phone into fastboot mode, fastboot erase data and fastboot erase cache should do a factory reset.
If your screen doesn't turn on, they may not see you unlocked your bootloader (since you got code from 3rd party, they wound't have another way to check). and since your phone doesn't boot, they probably wont see its rooted either. So you MIGHT be ok.
So a few people know that I've been having problems with my Note 4 (documented in different threads, can replicate any day), as it relates to the camera performance under cold temperatures. I've confirmed that it's not happening on neither my friends' AT&T Note 4's, nor an AT&T Note 3. This brought me onto calling Samsung and checking things out with their warranty. I explained my case in great detail - that I live in northeast and every time I leave the phone in temperatures below 40 F (next to an open window, or in my jacket pocket, for instance), upon launching a camera app, I see a very visible purple line going across the screen, which happens in every single camera app that I tried, and does not happen anywhere else. The lady I spoke to said that, apparently, I should not be exposing the phone to extreme temperatures. I asked what the extreme temperature range was - she could not answer and pointed me to the Note 4 warranty page (http://www.samsung.com/us/support/s...d_mdl_cd=SM-N910TZKETMB&prd_mdl_name=SM-N910T, also attached), where in section H) it says that "exposure to weather conditions" would not be covered. I searched the page for words "temperature", "hot", "cold", but could not produce anything at all. The result of the call was that she sent me a UPS label for me to send them the phone. I've since decided that I'm not going to send it in, since it isn't that big of a deal, and I've already invested quiet a bit of time into rooting, installing stuff. Plus, since most ROMs void the warranty, I don't think I'd qualify anyway.
But my question mostly concerns the vague wording in the warranty itself. With all the engineering that went into these devices, wouldn't they know which temperatures affect it? Also, that 'weather conditions' bit - sounds like the moment you take it out of the package, you are exposing it to the weather conditions, be it a hot, sunny summer day, a breezy morning on a pier, or a blistering cold during your favorite blizzard, or, of course, a quiet chilly morning next to your very window.
Considering the battery is intended to be used between -20°C and 60°C (-4°F and 140°F) usually, asking the phone to function correctly at -40° is a bit excessive.
Taking it outside into -40° weather while it was within normal range would be one thing. But to have the phone itself also be -40° is asking a lot.
The phone was not made for those kind of conditions. Just like it is not made to be dunked in water.
Common sense goes a long way.
Sent from my SM-N910T using XDA Free mobile app
nosympathy said:
Considering the battery is intended to be used between -20°C and 60°C (-4°F and 140°F) usually, asking the phone to function correctly at -40° is a bit excessive.
Taking it outside into -40° weather while it was within normal range would be one thing. But to have the phone itself also be -40° is asking a lot.
The phone was not made for those kind of conditions. Just like it is not made to be dunked in water.
Common sense goes a long way.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I did write below (not negative) 40 F = 4.44 C. I would not leave my windows open in -40F.
LaidBackTech said:
I leave the phone in temperatures below 40 F (next to an open window, or in my jacket pocket, for instance)...
Click to expand...
Click to collapse
LaidBackTech said:
I did write below (not negative) 40 F = 4.44 C. I would not leave my windows open in -40F.
Click to expand...
Click to collapse
Ahh sorry. Lol. I know people that do that in -10° weather so... But yeah. I miss read that then.
Mine was working fine(camera) after sitting in a 0 degree garage the other day for 2 hours. Replacement time.
I'd argue the battery deal still. Since that is a fair indicator of expected working conditions.
Sent from my SM-N910T using XDA Free mobile app
Do a warranty exchange if you think it's the particular tmobile note 4 you have or t mobile note 4s in general.
It could be just yours. It's not all of them, of course.
They are physically identical to the att ones except for badging.
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
If you are worried about Knox being tripped. Don't. We have exchanged our fair share of note 4s to tmobile and Samsung at this point. Knox tripped every time.
Result. New phone every time. Just Odin back to stock or flash a stock rom in recovery first.
+
Factory data reset.
Just exchange.
Android_Monsters said:
Do a warranty exchange if you think it's the particular tmobile note 4 you have or t mobile note 4s in general.
It could be just yours. It's not all of them, of course.
They are physically identical to the att ones except for badging.
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
If you are worried about Knox being tripped. Don't. We have exchanged over a thousand note 4s to tmobile and Samsung at this point. Knox tripped every time.
Result. New phone every time. Just Odin back to stock or flash a stock rom in recovery first.
+
Factory data reset.
Click to expand...
Click to collapse
When you say exchange - are you referring to the Samsung exchange, or T-mobile exchange?
Either or.
It depends on whether you are out of the 14 day period (which you are).
Whether you have insurance or jump.
But I meant either.
10-K said:
Either or.
It depends on whether you are out of the 14 day period (which you are).
Whether you have insurance or jump.
But I meant either.
Click to expand...
Click to collapse
Just called T-mobile - lady said that I can go to a T-mobile store, explain the situation and exchange it. She said nothing about a 14-day period; I'm definitely out of it - I've had the phone for roughly 2 months.
Seems like you'll be cool then.
...And, of course, what I was told on the phone was incorrect.
The Tmo store rep said that I need to call 800-937-8997 and have them do a warranty-exchange, which involves 1) them sending me a new phone with a prepaid return label, 2) take the new phone out and put my current phone in there, 3) peel off the label to expose the prepaid return label and 4) send the current phone back to them.
I called the number and was told that, wait for it, the Tmo store clerk was also incorrect; that 1) they will send me a prepaid label, 2) I send the current phone to them, 3) wait 5-10 business days for them to test and repair it if necessary and ship the new replacement back if they do or don't find anything and 4) wait for the returned phone.
Instead I went to the Best Buy (where I bought the phone) to exchange it, who - after hearing the issue - insisted that they do not replace phones, be it under or out of warranty, unless it's covered under their Geek Squad protection plan. After 10 minutes of arguing, the BB rep agreed to take my phone, purchase a new one and have it ship to my address.
To be continued...
Wow. For having tech in your name. You suck at returning phones.
Android_Monsters said:
Wow. For having tech in your name. You suck at returning phones.
Click to expand...
Click to collapse
Forgive me if I'm not as talented as you are. I've never returned any of my prior phones.
No worries man. I was having a bad day. You'll get a new one and it'll be great I'm sure.
In general, if I do a complete backup of everything on phone #1, is it wise to restore the same backup on phone #2 if it's a replacement phone (same make and model)?
I used to think you shouldn't, but yeah its just fine.
Go for it.
Got the new phone yesterday, slow and stuttery as **** from the moment it booted. Since I had nothing on it, I wiped everything (Dalvik, system, data, cache, internal storage) - same thing, even after trying 3 different ROMs (Hyperdrive, Fire Kat, Dynamic Kat). The stutter showed in camera the most, followed by file managers, followed by everything else. I returned the phone once again and ordered a new one.
Did you do a factory reset, as well as the wiping?
---------- Post added at 04:40 AM ---------- Previous post was at 04:39 AM ----------
I still get my ring tones, etc. When I wipe. I think it's fragments
Android_Monsters said:
Did you do a factory reset, as well as the wiping?
---------- Post added at 04:40 AM ---------- Previous post was at 04:39 AM ----------
I still get my ring tones, etc. When I wipe. I think it's fragments
Click to expand...
Click to collapse
Yes, I did everything 3 times (once for HD, FK, and DK each).
Got the new phone - everything was more or less okay until I restored Dynamic Kat from the SD card. Things started stuttering again, from the setup screen. Tried two other ROMs - same thing. When I flashed the ROMs, I wiped everything clean, including the 'Format Data' option. I am at a complete loss - is there a different stable kernel that I can try?
I really enjoy my Nexus 4 and wasn't planning to change it until it fails, but i found an Nexus 6 at a very attractive price...
The guy who sells it says he got it from outside the country, it was working and he did an factory reset and now the phone wants the previous gmail account and password to finish the reset. I don't know how true is his story, and I really don't care...
I'm tempted to buy it, but can it be resurrected? Can i root it, install a custom recover and ROM, as the phone is? I don't want to end up with an paper weight...
The rooting guide suggest it's possible, but it says that first i have to enable OEM Unlock and USB Debugging, and this has to be done from the phone.
kiarfuzzy said:
I really enjoy my Nexus 4 and wasn't planning to change it until it fails, but i found an Nexus 6 at a very attractive price...
The guy who sells it says he got it from outside the country, it was working and he did an factory reset and now the phone wants the previous gmail account and password to finish the reset. I don't know how true is his story, and I really don't care...
I'm tempted to buy it, but can it be resurrected? Can i root it, install a custom recover and ROM, as the phone is? I don't want to end up with an paper weight...
The rooting guide suggest it's possible, but it says that first i have to enable OEM Unlock and USB Debugging, and this has to be done from the phone.
Click to expand...
Click to collapse
No, it cannot be recovered without the gmail password. This is a security feature. This leads me to believe that the phone may be stolen.
---------- Post added at 12:44 PM ---------- Previous post was at 12:30 PM ----------
Oh and questions go in the Q&A section, not in general forum.
I did some research on the new "Device Protection" and it seems pretty solid... But i'm afraid this will kill the second-hand android market also...
Just a few scenarios:
1. I want to sell my phone, but obviously i don't want to sell it with my account. How will i do that?
2. I buy a SH phone, i enter my email then do a factory reset. What will happen than? Will it ask for my account or the previous one?
kiarfuzzy said:
I did some research on the new "Device Protection" and it seems pretty solid... But i'm afraid this will kill the second-hand android market also...
Just a few scenarios:
1. I want to sell my phone, but obviously i don't want to sell it with my account. How will i do that?
2. I buy a SH phone, i enter my email then do a factory reset. What will happen than? Will it ask for my account or the previous one?
Click to expand...
Click to collapse
Neither of your scenarios are causes for concern.
1: Only a moron would sell a phone without performing a factory reset BEFORE handing it over to the purchaser.
2: See #1.
3: ALWAYS perform a factory reset **AND** network test with YOUR SIM CARD WITH the seller BEFORE handing over the money. If it completes successfully, then you're golden. If it is a NEXUS device, perform an OEM UNLOCK on it before handing over the money. If it completes successfully (along with functional network), then you're golden.
If #3 is not possible, you should ensure that your method of payment protects you from fraud of this nature.
If you're selling your phone, or passing it on to someone else, you can remove your account before you do so. Factory resetting without removing your Google account first will not un-protect the phone. If you reset without removing your account it will remained locked to your account.
To turn off device protection, remove your Google account from your device. If you have Developer options enabled on your device, you can also go to Settings > Developer options and check "OEM Unlocking."
Click to expand...
Click to collapse
Without access to a Google account that was previously setup on a protected phone there seems to be no way to activate it on a new Google account.
https://support.google.com/nexus/answer/6172890?hl=en
On a side note; if you've changed your Google account password don't factory reset your phone for at least 72hrs.
http://forum.xda-developers.com/showpost.php?p=59780601&postcount=4
kiarfuzzy said:
I really enjoy my Nexus 4 and wasn't planning to change it until it fails, but i found an Nexus 6 at a very attractive price...
The guy who sells it says he got it from outside the country, it was working and he did an factory reset and now the phone wants the previous gmail account and password to finish the reset. I don't know how true is his story, and I really don't care...
I'm tempted to buy it, but can it be resurrected? Can i root it, install a custom recover and ROM, as the phone is? I don't want to end up with an paper weight...
The rooting guide suggest it's possible, but it says that first i have to enable OEM Unlock and USB Debugging, and this has to be done from the phone.
Click to expand...
Click to collapse
Nobody should be selling used Nexus 6 at any kind of discount at this point in time.
The reason it is a discount, is because it is STOLEN.
If the owner of the registered gmail account cannot be contacted, then the ownership chain is broken and the device is stolen.
It *MAY* be possible to bring it back to life using low level reinitialization, HOWEVER, it could also have a blocked IMEI, making it useless on a network even IF you manage to clear the lockout.
If I were you, I would report this seller to law enforcement.
So after i do a factory reset, I verify my account and the reset finishes. Than it will be like a new phone, my account will than be removed and the buyer will have to enter a new/his account?
@doitright
I'll stick with my Nexus 4... Reporting him to the police will probably be just a waste of my time...
Look here for a bit more info:
https://support.google.com/nexus/answer/6172890?hl=en
Again, thanks @efrant for finding this.
Edit:
Oops, I see this link was already provided. Sorry.
If the boot loader is unlocked can it be flashed back to 5.0.1 and do away with the new security feature all together, of course if it is stolen/blocked imei then of course it still wouldn't work
If you look on eBay for used iPhones, you'll see many cheap 5 and 6 variants - except in cases where the phones are horribly damaged, they are usually iCloud Activation Locked. I tend to see that as a comparable concept to Lollipop's Device Protection scheme and it may likewise lower some phone theft numbers over time, for all we know.
At the very least, Device Protection might make people more cautious when purchasing Android phones - a seller on eBay sold me a locked S5 and none of her passwords worked - fortunately, this was KitKat, so performing 10 bad passcodes forced a factory reset with no additional locks.
- ooofest
Yup, stolen, don't buy.
It's always fun to see these - the phone at a great price, only one thing wrong with it ....
Here's a way to get out of it without calling the person a thief, ask for the IMEI to have it checked, betcha they don't want to give it out.
kiarfuzzy said:
@doitright
I'll stick with my Nexus 4... Reporting him to the police will probably be just a waste of my time...
Click to expand...
Click to collapse
You really should report him. As should *everybody* who runs into this kind of fraud. You're right, it probably won't amount to anything, but in the off chance that it could, then you manage to do something good and it doesn't cost you anything.
---------- Post added at 08:06 PM ---------- Previous post was at 08:04 PM ----------
RW-1 said:
ask for the IMEI to have it checked, betcha they don't want to give it out.
Click to expand...
Click to collapse
Nobody with an ounce of sanity would give out the IMEI anyway, since that is all you need to GET a phone blacklisted.
---------- Post added at 08:15 PM ---------- Previous post was at 08:06 PM ----------
There is a strong possibility that some variation of http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 would be able to fix a locked out device.
doitright said:
Nobody with an ounce of sanity would give out the IMEI anyway, since that is all you need to GET a phone blacklisted.
Click to expand...
Click to collapse
Seen this a few times now. I don't think that is how it works. Pretty sure you have to prove you owned the phone. As in it was attached to your account, or a police report. If you can just call and say your phone with blah blah IMEI was stolen and they don't verify anything what's stopping me from just blacklisting all phones (of I had enough time to go through all IMEI's)?
(OK that's a bit extreme as it would take well longer then a few life times to call and so each one, but you get the idea)
doitright said:
There is a strong possibility that some variation of http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 would be able to fix a locked out device.
Click to expand...
Click to collapse
Possibly. It would be great if that is the case. We just need someone to figure out how.
help please
ok.. i was not aware of the new device protection thingy and bought a nexus 6 for 150$. Realistically what is my option? i have search everywhere in xda for solution but have not able to find it yet. Without access into the phone to enable usb debugging and enable oem unlock there is not thing much to do right? Resale with a warning that is lock with email account ?
haixingau said:
ok.. i was not aware of the new device protection thingy and bought a nexus 6 for 150$. Realistically what is my option? i have search everywhere in xda for solution but have not able to find it yet. Without access into the phone to enable usb debugging and enable oem unlock there is not thing much to do right? Resale with a warning that is lock with email account ?
Click to expand...
Click to collapse
Your only option is to try and return it. Or try to sell it as unusable.
Sent from my Nexus 6 using Tapatalk
" Sameer: Sorry to inform you that as the device will be sent back with out any repair as it was rooted."
Unbelievable.
The phone had been playing up for 2 weeks, shutting down between 70-40% battery for no good reason. I flashed 5.1 again and factory reset it. Surely that is enough to un-root it? Or do they have some special way of telling if it's been rooted before?
At the moment it seems they are posting it back to me, so I'm down the £7 in postage to them, and I now have a faulty £500 phone.
Anyone know what I should do?
I originally rooted it with 'CF-Auto-Root-shamu-shamu-nexus6.zip' and run the 'root-windows.bat' - believe while in fastboot?
I also flashed the 5.1 update straight from the google website - also through fastboot I believe..
But I do remember when I booted it up just before packing it up, that the unlocked padlock wasn't there...
I even tried google but they won't RMA it because I didn't buy it from them.
Well ,I presume that Motorola or any other company would not accept a Bootloader unlocked device .
Hi, questions go in Q&A forum, not in general. I've asked the mods to move it there so you can get a better response to your question.
Evolution_Freak said:
Hi, questions go in Q&A forum, not in general. I've asked the mods to move it there so you can get a better response to your question.
Click to expand...
Click to collapse
Done:good:
toString said:
" Sameer: Sorry to inform you that as the device will be sent back with out any repair as it was rooted."
Unbelievable.
The phone had been playing up for 2 weeks, shutting down between 70-40% battery for no good reason. I flashed 5.1 again and factory reset it. Surely that is enough to un-root it? Or do they have some special way of telling if it's been rooted before?
At the moment it seems they are posting it back to me, so I'm down the £7 in postage to them, and I now have a faulty £500 phone.
Anyone know what I should do?
I originally rooted it with 'CF-Auto-Root-shamu-shamu-nexus6.zip' and run the 'root-windows.bat' - believe while in fastboot?
I also flashed the 5.1 update straight from the google website - also through fastboot I believe..
But I do remember when I booted it up just before packing it up, that the unlocked padlock wasn't there...
I even tried google but they won't RMA it because I didn't buy it from them.
Click to expand...
Click to collapse
Did you flash the entire factory image, including userdata and cache? Are you sure that you relocked your bootloader?
just something to know and live by.. generally, only google will except devices with an unlocked bootloader(with root) for exchange or repair. sometimes you can get away with it from other companies, but only google would give you no issues with it.
Where did you buy it? Could try returning it to them after a full factory / relock
It was relocked after I did the full flash to 5.1 as per googles android website (the flash-all.bat route).
Someone has told me there is a status flag? 0 = locked, 2 = re-locked, 3 = un-locked.
So maybe when I locked it again for stock, it was set to 2, how can I change it to 0? Maybe that will 'fool' them at least....
toString said:
It was relocked after I did the full flash to 5.1 as per googles android website (the flash-all.bat route).
Someone has told me there is a status flag? 0 = locked, 2 = re-locked, 3 = un-locked.
So maybe when I locked it again for stock, it was set to 2, how can I change it to 0? Maybe that will 'fool' them at least....
Click to expand...
Click to collapse
2 is stock. I have one that is 100% stock , never rooted or unlocked and it shows 2. My only guess would be you left some root files on the device. After you flashed back to stock did you wipe data/ factory reset?
Sent from my Nexus 6 using XDA Premium HD app
Intub8 said:
2 is stock. I have one that is 100% stock , never rooted or unlocked and it shows 2. My only guess would be you left some root files on the device. After you flashed back to stock did you wipe data/ factory reset?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I completely flashed everything, so there wouldn't be anything left. I then did a factory reset just for added mesasure! So far I can't see how they knew it was rooted. As it's impossible that it was rooted when they got it. So there's either something secret or they're lying so they don't have to repair or replace it....?
toString said:
I completely flashed everything, so there wouldn't be anything left. I then did a factory reset just for added mesasure! So far I can't see how they knew it was rooted. As it's impossible that it was rooted when they got it. So there's either something secret or they're lying so they don't have to repair or replace it....?
Click to expand...
Click to collapse
Well if they are lying then ask them to provide proof that it was "rooted" at the time they received it. If they cannot provide any proof then there are some sales of goods act stuff you can start applying on them.
You have a warranty on the device provided that the phone is not modified in any way that would void this warranty.
Motorola are are bunch of pricks when it comes to Customer Services, i wanted to send back my Moto X 2nd Gen which had an unlocked bootloader. Even though they accepted bootloader unlocked phones, it didnt reach the customer service team and i was refused, and then told later once they received the memo that i could return it. I ended up selling it on ebay for more than i paid for it which turned out alright
IINexusII said:
Well if they are lying then ask them to provide proof that it was "rooted" at the time they received it. If they cannot provide any proof then there are some sales of goods act stuff you can start applying on them.
You have a warranty on the device provided that the phone is not modified in any way that would void this warranty.
Motorola are are bunch of pricks when it comes to Customer Services, i wanted to send back my Moto X 2nd Gen which had an unlocked bootloader. Even though they accepted bootloader unlocked phones, it didnt reach the customer service team and i was refused, and then told later once they received the memo that i could return it. I ended up selling it on ebay for more than i paid for it which turned out alright
Click to expand...
Click to collapse
Sama as LG. That's why I decided to buy from Play this time.
Just as an update from my post last week:
Dear xxx,
Thank you for contacting Motorola.
I have now heard back regarding your Nexus 6 unit. After carrying out the initial repair the engineers at our repair centre then discovered a more serious fault with the battery on the phone as it started to swell during their testing.
As this battery swelling issue is irreparable we are instead going to exchange your phone for a new unit. Unfortunately the repair centre do not have any spare Nexus 6 units in stock at the moment. They are currently awaiting delivery of new stock. As soon as this arrives they will dispatch a new unit to you.
Please accept my apologies for any further inconvenience that this causes you. We will try our best to get this resolved as soon as possible for you.
Kind regards,
Motorola Mobility UK Ltd.
Click to expand...
Click to collapse
Good result it seems. New phone. Not sure what changed their mind though, because apart from moaning to the online chat guys (who appeared useless) I didn't actually contact the repair guys, I just expected them to return it and I would take things from there.
But the more serious point here is if you experience these issues with the battery that I did (random shutdowns between 70-40%) then you may find that your battery starts to swell and who knows what could have happened to me or my home after that....
Hey mate
I got to send mine in for the same reason as you....
Any tips mate i have unlocked bootloader with stock back on. Did you have to send in receipt as mine is on contract did not keep any details.
cheers matey
toString said:
Just as an update from my post last week:
Good result it seems. New phone. Not sure what changed their mind though, because apart from moaning to the online chat guys (who appeared useless) I didn't actually contact the repair guys, I just expected them to return it and I would take things from there.
But the more serious point here is if you experience these issues with the battery that I did (random shutdowns between 70-40%) then you may find that your battery starts to swell and who knows what could have happened to me or my home after that....
Click to expand...
Click to collapse
TheLoverMan said:
Hey mate
I got to send mine in for the same reason as you....
Any tips mate i have unlocked bootloader with stock back on. Did you have to send in receipt as mine is on contract did not keep any details.
cheers matey
Click to expand...
Click to collapse
Lock your bootloader.
http://forum.xda-developers.com/showthread.php?t=3067302
Thanks for that did the lock all sorted but i have a follow up question....
Will it matter what firmware i used? Dont want to put anything on there to give them an excuse.
Thanks again
TheLoverMan said:
Thanks for that did the lock all sorted but i have a follow up question....
Will it matter what firmware i used? Dont want to put anything on there to give them an excuse.
Thanks again
Click to expand...
Click to collapse
No, that shouldn't matter.
toString said:
But the more serious point here is if you experience these issues with the battery that I did (random shutdowns between 70-40%) then you may find that your battery starts to swell and who knows what could have happened to me or my home after that....
Click to expand...
Click to collapse
I very strongly believe that this is a chicken-and-egg problem. Generally, the battery reading problem is a software problem, BUT, it can probably lead to overcharging, which causes swelling. There is a bootloader procedure to reset the battery data that should be performed *immediately* when it starts exhibiting "early shutdown" symptom.
I also suspect that the quick-charge chargers are supplying more current than the battery itself is capable of taking, increasing the battery temperature and prematurely aging it. My personal recommendation is to limit yourself to 5 volt at 1 amp.
doitright said:
I also suspect that the quick-charge chargers are supplying more current than the battery itself is capable of taking, increasing the battery temperature and prematurely aging it. My personal recommendation is to limit yourself to 5 volt at 1 amp.
Click to expand...
Click to collapse
Again, I agree. We are definitely on the same wavelength today.
Hey mate what is the bootloader procedure?
Thanks
doitright said:
I very strongly believe that this is a chicken-and-egg problem. Generally, the battery reading problem is a software problem, BUT, it can probably lead to overcharging, which causes swelling. There is a bootloader procedure to reset the battery data that should be performed *immediately* when it starts exhibiting "early shutdown" symptom.
I also suspect that the quick-charge chargers are supplying more current than the battery itself is capable of taking, increasing the battery temperature and prematurely aging it. My personal recommendation is to limit yourself to 5 volt at 1 amp.
Click to expand...
Click to collapse
So, I've been using this wonderful device for a while now, since early October. I've finally got it set up the way I like it and all. Now, I'm just flashing ROMs to see which I prefer. Just a few hours ago, I decided to revert to the T-Mobile ANK3 (or AN-whatever) stock ROM because on Lollipop 5.0.1+ the battery dies much quicker than I'd like it to. Yet, that ROM would constantly either:
A) Die whenever it wanted to
B) Freeze and just not respond
C) Require a battery pull
D) Send me to D/L mode with "mmc_read fail".
So I decided to revert back to stock 5.0.1 because I was tired of all the bugs I was encountering with 4.4.4.
Now, every hour or so, the phone dies and gets stuck on the splash screen (with the obvious SEAndroid not enforcing + Set Warranty Bit). Or if it isn't that, the phone just outright freezes when I'm using a light application (i.e. Kik Messenger).
I'm starting to think that my eMMC is dying, because the phone was not acting like this when I first got it in early October. Every once in a while D/L mode keeps repeating my fears. I cannot send it in to Samsung because I already voided my warranty, and I am a prepaid subscriber on T-Mobile. (So, no, T-Mobile will not help me, likely.)
Any ideas on what's happening, or what I should do?
First thing I would do Is flash a different kernel
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did that, ended up having the same problems. I said screw it, and am now using CM12.1...
Although I really don't like it (because TW is now a good thing as opposed as to how bad it was on the S3), I'll settle with it. It's not so bad.
---
LMAO OOOOO I LIED TO MYSELF
even CM is force rebooting itself wwwwhat
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
sqmala4321 said:
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
Click to expand...
Click to collapse
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Good news...since they know that the eMMC chip is bugging out, they'll do a free repair. Success! Now, time to go into the repair shop and hope they accept my reference ticket, since I'll be a walk in.
I can't call right now, seeing as my phone has difficulty doing ANYTHING now...
eduardog131 said:
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Click to expand...
Click to collapse
actually i am having the same exact problem....i had the tmobile note 4, and its doing the same thing about 1 month ago...reboots, black screens; and all that you have mentioned. so i started to look into rooting/flashing tekxodus hd onto my phone...still the same problem...phones restarts to boot loop time to time...bad screens....i'm still trying to find outwhat the hack is going on...and the phone's warranty expireds about 1 month ago right before the phone start to act up....let me know if you find a solution to that..lol...thanks:good:
---------- Post added at 11:25 PM ---------- Previous post was at 11:17 PM ----------
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
yes, i did that too...odin back to stock, still same problem...my phone was on stock when these problems started. i hoping different roms would solve the problem...so i started rooting and intalled tedxodus and the same problems...hopefully someone could help please.