Related
I am in California so I have 30 days from the day I received the phone in order to return it. So I am thinking should I return it ?....If I root my phone, can I still return it without any repercussions from rooting ?...
If you are asking why do I want to return it: IDK honestly, just feel kind of stupid/bad for spending so much on this phone especially when some of its tech is already phased out (the touch screen sensor)...but it is not on a contract and I guess I can always buy another phone and even try to sell this one....
any ways..if you have any ideas/comments on any of these issues then please advise me. The main thing here is I want to know if I can return it if I root it ?
Don't think so, you void the warranty when you unlock the bootloader. I would have to imagine that your right to return it goes with the warranty as well.
I understand what you are saying, but returning and warranty are two different things, they would not necessarily be linked...
any other insights ?
Tech is phase out???? example touch sensor?
You coming from which century? year 3010?
Well if you go buy anything and void your warranty don't expect them to refund you lol
You should be able to return it unless the seller of the phone powers it on to inspect it.
buyers remorse
just return it. if you feel like it's outdated, that's a cop out. if you feel like it's defective, clear conscience.
If you root it you will never WANT to return it
erebusting said:
I am in California so I have 30 days from the day I received the phone in order to return it. So I am thinking should I return it ?....If I root my phone, can I still return it without any repercussions from rooting ?...
If you are asking why do I want to return it: IDK honestly, just feel kind of stupid/bad for spending so much on this phone especially when some of its tech is already phased out (the touch screen sensor)...but it is not on a contract and I guess I can always buy another phone and even try to sell this one....
any ways..if you have any ideas/comments on any of these issues then please advise me. The main thing here is I want to know if I can return it if I root it ?
Click to expand...
Click to collapse
I've been hearing you complain about the phone being outdated all over the place, can you hurry and do whatever you're going to do and go to the HTC Incredible section, if there is one.
Have you already rooted it? if not, don't until you are sure you don't want to return it.
Eclair~ said:
I've been hearing you complain about the phone being outdated all over the place, can you hurry and do whatever you're going to do and go to the HTC Incredible section, if there is one.
Click to expand...
Click to collapse
So what? There are other members who want insight and all I see is "yes its worth it, just keep it etc..." I mean I understand they are writing in the Nexus One section, but that does not mean they should only read/get the positive replies about the phone -there are others like me who have gripes about it and I will share my opinion as long as they are asking...why don't you just ignore everything I say since you seem so upset that I am offending your phone simply by bringing up truths and opinions WHEN ASKED mind you. Did I say the PHONE WAS OUTDATED? NO (which is beside the point any ways)- I said some of the tech is outdated/being phased out already such as the Multi Touch Sensor...now if that hurts your feelings or makes you upset then take it up with google -I for one feel that I would like to have been able to have the new MaxTouch sensor included in the Nexus, but since that is not the case then it is definitely something which makes me second guess if I should keep it or wait for another phone to arise with the MaxTouch tech.
Now why would you reply such a way to this topic when I am asking if I can return it if it is rooted, you reply has nothing to do with my topic...is it really bugging you that much? Do you really care about what I am doing/saying so much?(thanks BTW haha )
LMFAO - Look at what I found:
http://forum.xda-developers.com/showthread.php?t=650854
Looks like ~Eclair was in the same concerned position as I am....You just happen to talk about the same thing as me also -the tech being outdated...it just so happens that it HAS already been outdated (with regards to the touch sensor that is) and that is what I was unsure about...So why are you all of a sudden coming back at me like you never had the same concerns about the phone..I am sure we are not the only ones who have these same concerns and others may want to hear it -if not they can overlook it, simple.
Put simply: just stop and either please try to be helpful or don't reply at all..seems reasonable, doesn't it ?
That was funny finding that thread you made though and you are here coming after me about the same thing you created a thread about...
imo, if you didn't want this to happen you shouldn't have posted why you wanted to return it. Just simply stating the question would do.
and I also believe that rooting would cause the phone to be non-returnable. But since they can relock the bootloader, there's also not much reason why not.
yea I wish someone had some definite insight into this topic...
Call htc then?
liam.lah said:
Call htc then?
Click to expand...
Click to collapse
yeah I guess that would give me the most official answer....
One lesson this OTA fiasco has taught me, is that as careful as we are, there is no way to put our phone back to the way they were when we bought them once we start flashing:
The only people that I've seen reporting success on the OTA update are the ones who never flashed. Thanks to people like designgears, workarounds have been provided, but the fact remains: once you flash, there's no going back (for now). Which brings me to my concern: if the OTA is failing because of this currently unidentified difference, then AT&T, Samsung, etc. can certainly tell whether or not you've screwed with your phone if you send it in for repair, even if you flash back to stock. And they could claim this voids the warranty. It seems like it would be worthwhile for us to understand why the patch is failing and remove this problem in future 3rdparty ROMS, just in case the return/repair dept. starts looking for this inconsistency.
It's not really something to be concerned over.
I really doubt Samsung is going to waste time checking the phones that get sent in to them. I sent Microsoft a melted Xbox 360, and they replaced it for free under the warranty.
MikeyMike01 said:
It's not really something to be concerned over.
I really doubt Samsung is going to waste time checking the phones that get sent in to them. I sent Microsoft a melted Xbox 360, and they replaced it for free under the warranty.
Click to expand...
Click to collapse
I agree. And to just double confirm this- I have actually spoke to a couple techs at Samsung who do the RMA stuff, and it does not void our warranty to flash THEIR OFFICIAL firmwares. All they do anyway when they get the device is immediately flash back to stock firmware themselves. They dont have time to "investigate" each RMA. The techs dont get paid enough and the turn around time woudl be a LOT long if this was the case.
It's a breach when we start flashing cooked stuff on there, but as long as the problem remains with factory based ROM there isn't a problem. It's only void if say you jack it up and cant get back to a "factory load" to verify the problem is actually hardware based.
Same thing with HTC devices too so just FYI. Oh and AT&T & Tmobile reps will also confirm this too. Your best bet though when calling in warranty is to NOT SAY you were dorking with your phone and messing with Cooked ROMS.
[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...
Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)
scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back
ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software
Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.
seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen
NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.
Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:
-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.
-if the above is possible then what procedures should I follow
I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.
Sorry for the bad quality of the images but that's what the guy selling it uploaded.
brurhh said:
Hi everyone, I'm planning on buying a bricked moto x because it's cheap and it's new. In the past I already bought a bricked phone and made it work, however I'm not sure I will be able to this time so I wanted to know if you guys can help me understand:
-IF it can be unbricked/fixed, I don't care if it's difficult but I need to know if it's possible first.
-if the above is possible then what procedures should I follow
I'm probably asking for too much, sorry, but from what I tried to investigate it looks like it has more than one single problem so im not sure if all of them have a solution.
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
*since I still don't own the phone I can't test anything, I just need to know if those errors shown above have a solution, or at least are not a death declaration so I can still try something if I buy it.
Sorry for the bad quality of the images but that's what the guy selling it uploaded.
Click to expand...
Click to collapse
You'll be rolling the dice on that one. MAYBE it can be fixed using the de-bricking procedures, but if anyone tells you that it can FOR SURE be fixed...well...I'd question their source.
If its cheap enough that you don't mind throwing that amount of money down the drain....give it a shot. Your call.
brurhh said:
What the seller said:
The old owner sold it with the bootloader unlocked, I didn't knew that, so I updated via OTA (in the phone) and ended like that.
Looks like it can't have an unlocked bootloader if OTA updating, I don't even know please help me.
Click to expand...
Click to collapse
I call BS on that account of what happened... The bootloader is LOCKED STATUS 0. That device was never bootloader unlocked. (and having an unlocked bootloader doesn't interfere with taking an OTA)
It could be that someone used one of the older procedures to root and disable write protection, took and OTA (losing root/write protection) and later tried to downgrade to root & disable write protection again, thus causing the brick.
It could be as simple as flashing the latest ROM (4.4.4) using mfastboot. I could be as complex as using -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 ... or it could just be a brick that can't be recovered.
Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.
KidJoe said:
... or it could just be a brick that can't be recovered.
Either way, like @samwathegreat said... its a roll of the dice. There is no way of knowing until after you buy the phone and try.
Click to expand...
Click to collapse
I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.
brurhh said:
I'll try, after all it's almost new, even if I need to replace something it would be cheaper than buying an used one, I'm worried about that CID stuff because I read that it has something to do with a unique file that has to be backed up and without that file there is nothing you can do to unbrick.
Click to expand...
Click to collapse
I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.
I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.
For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.
You just don't know.
KJ said:
I'd be worried too. There's a great chance the device can't be fixed... And you're simply out X amount of dollars.
I'd pocket your money and add a bit when you can and buy a used fully working device. At least the money won't be wasted... Potentially.
For all you know he fastbooted a rom or firmware for another device entirely. If so, you're done. Paperweight. He could have brought it somewhere and already been told it's unsalvagable.
You just don't know.
Click to expand...
Click to collapse
Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again
brurhh said:
Thanks, what the seller says doesn't match with the fastboot screen thats my fear, I guess he don't know or perhaps doesn't want me to know how the phone really ended like that, this phone is amazing, I just got excited about getting it so cheap, i guess i'll wait more thanks again
Click to expand...
Click to collapse
I don't blame you!
There's some bricks you can recover from, and some you can't.
Your odds are the same if you just go to the casino and put your money for the phone on red or black at the roulette table. If you lose you lose... But if you win... You can buy a working phone. ?
" 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