Another RMA disaster... - X 2014 General

I bought my Pure Edition about a month ago. A week and a half ago, I wake up and check Google Now for the weather and the phone shuts down and is fried. It has been hot a lot, but I heard it was normal and no big deal. I went through the ordeal of getting a replacement phone a week ago Monday. I then got the email saying it would ship the day after it was received. Sweet! I was thrilled! Only 3 days with a cheap prepaid temp phone. So it doesn't get delivered on that Thursday as stated. Or the next day. I call them to check on it and they said it wasn't going to be here until Today. Surprise! I got it a day early! Yes! However, they sent me a phone that had the bootloader still locked, but the software was modified so I can't use it for work as it shows compromised in Airwatch. I'm fairly certain my account has been flagged, but that's another issue to fix. I called them again today. They will send me a new one. Again. Another week without a phone that I bought only a month ago. I really wish they had the Nexus 6 in stock the day I bought this because that is the one I wanted. I absolutely loved by 2013 Moto X. This one, not so much. The several people I was transfered between had no idea what compromised means on the bootloader. The last guy, thought that the bootloader was used for loading Airwatch in the first place. Has anyone else recieved a phone from the OEM that was compromised or modified software? Slowly, but surely losing faith in this company.

That's a disaster? We must have a very different definition of that word

OK, So I am a little upset by it all, but I just bought the phone a month ago and now I am going to be without it for 2 out of the 5 weeks of ownership. Maybe its not the RMA process, but that I am having to go through it so soon and twice at that.

I do agree that is a PITA. I bought mine used and did not have this experience. It's funny you say you liked the 2013, because I actually very much disliked the 2013 and could not be happier with my 2014.
I'm not quite following the modified software thing. They sent you a phone with a locked bootloader but was not all the way stock? I found that either a) AirWatch does not look for whether the bootloader is locked/unlocked, or b) my firm did not include that in the AirWatch policies or whatever. I unlocked my bootloader, installed TWRP, and rooted, and my phone showed up as compromised. I returned to pure stock with stock recovery, but kept my bootloader unlocked, and had no problems clearing AirWatch. I've heard the same from others on XDA. But I find it weird that Moto would ship out a phone that had compromised software. Even if it was one someone else returned, you would think it would be standard policy to ensure it is completely wiped and returned to full on factory stock condition.

anidrin said:
Has anyone else recieved a phone from the OEM that was compromised or modified software?
Click to expand...
Click to collapse
I would return it again. This is Moto's fault for having these flags in the first place.

Yeah, shipping it locked is not a surprise, showing up in Airwatch as compromised when it's still stock recovery, locked, and non rooted? That's odd.

Paddington said:
I'm not quite following the modified software thing. They sent you a phone with a locked bootloader but was not all the way stock?
Click to expand...
Click to collapse
There is a root checker on Motorola phones since I think ICS days. If a device has never been rooted it's status is 0/0, if it is currently rooted it is 1/1 and if it was rooted and unrooted it is 0/1. If it is either of the latter 2, it will show as modified software in bootloader mode.
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
scottricketts said:
Yeah, shipping it locked is not a surprise, showing up in Airwatch as compromised when it's still stock recovery, locked, and non rooted? That's odd.
Click to expand...
Click to collapse
No it's not, it means it has been rooted in the past.

JulesJam said:
There is a root checker on Motorola phones since I think ICS days. If a device has never been rooted it's status is 0/0, if it is currently rooted it is 1/1 and if it was rooted and unrooted it is 0/1. If it is either of the latter 2, it will show as modified software in bootloader mode.
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
No it's not, it means it has been rooted in the past.
Click to expand...
Click to collapse
Did you try running a root checker app to see if the phone is currently rooted? Because my device was rooted, but reflashing a stock unrooted system made my phone go from compromised to compliant on our AirWatch system. And our AirWatch policies are pretty strict, because they have to meet the security tests of our clients with the strictest security policies, and we are a big law firm that represents most of the Fortune 100 and nearly (or every) major bank.
Although I do agree with your initial stance that there is really no excuse for them to ship you a pre-rooted phone without you requesting it. In the past, that would have saved me 10 minutes, but now, it would be a hassle.

Paddington said:
Did you try running a root checker app to see if the phone is currently rooted?
Click to expand...
Click to collapse
I did it with my N6. I know the phone is unrooted as I flashed a stock system image. In the bootloader mode, it still says software is modified.
This is well known to be how it works with Motorola phones.
Paddington said:
Although I do agree with your initial stance that there is really no excuse for them to ship you a pre-rooted phone without you requesting it. In the past, that would have saved me 10 minutes, but now, it would be a hassle.
Click to expand...
Click to collapse
His phone wasn't pre-rooted - it had been rooted in the past and that then creates the 0/1 state.

JulesJam said:
I did it with my N6. I know the phone is unrooted as I flashed a stock system image. In the bootloader mode, it still says software is modified.
This is well known to be how it works with Motorola phones.
His phone wasn't pre-rooted - it had been rooted in the past and that then creates the 0/1 state.
Click to expand...
Click to collapse
So I just tried this out. I booted into fastboot and it says my device is UNLOCKED, and then it says:
"Status Code: 3"
"Software Status: Official"
I unlocked this phone, flashed TWRP, and rooted it. I screwed around with it, downloaded a few root apps (busybox, rootbrowser, quick boot), then saw it was listed as compromised on AirWatch. I used a toolkit to do a full wipe and revert back to stock, unrooted 4.4.4 and factory recovery. I then upgraded to 5.0 through the OTA. I never relocked the bootloader. My device showed up as compliant when I redownloaded AirWatch.
And I still agree with the original premise that Motorola should have made sure this didn't happen originally--which is why they are going to fix it--but I'm not understanding why he can't get around this the same way I did. I'm not understanding why he is showing up as a modified software while I am not.

Paddington said:
So I just tried this out. I booted into fastboot and it says my device is UNLOCKED, and then it says:
"Status Code: 3"
"Software Status: Official"
I unlocked this phone, flashed TWRP, and rooted it. I screwed around with it, downloaded a few root apps (busybox, rootbrowser, quick boot), then saw it was listed as compromised on AirWatch. I used a toolkit to do a full wipe and revert back to stock, unrooted 4.4.4 and factory recovery. I then upgraded to 5.0 through the OTA. I never relocked the bootloader. My device showed up as compliant when I redownloaded AirWatch.
Click to expand...
Click to collapse
Hmm, that is not what is happening with my N6 or on the Droid Turbo forums for those who are using MoFo. For us, once we root, that is it, even unrooting, flashing back to stock doesn't reset that root check flag.

JulesJam said:
Hmm, that is not what is happening with my N6 or on the Droid Turbo forums for those who are using MoFo. For us, once we root, that is it, even unrooting, flashing back to stock doesn't reset that root check flag.
Click to expand...
Click to collapse
If it was just Droid Turbo, I'd guess it has to do with the MoFo exploit and the fact that it is not supposed to be unlocked and rooted. And by "not supposed to be," I of course mean in the eyes of Verizon, because it is ridiculous that a company will not let you unlock your bootloader on a $600 phone once you've fully paid it off. But that is beside the point. The fact that it is also happening with your Nexus 6 pretty much defeats my theory that it is MoFo causing it.
Could it be that when I updated through a true OTA, like went to Settings > About Phone > Updates, it reset this counter? Or, ignoring the counter for a moment, that the true OTA update re-established my system as being 100% unmodified stock--"Software Status: Official"? Troubleshooting based on recent experiences without the ability to test my hypotheses (it is my work phone ,after all) is driving me nuts.

Paddington said:
The fact that it is also happening with your Nexus 6 pretty much defeats my theory that it is MoFo causing it.
Click to expand...
Click to collapse
I just flashed my N6 back to total stock using factory images and relocked it. Software status says modified and bootloader status is status code 2 locked (which means relocked). And AFAIK, this is what everyone's experience on a Motorola phone is:
Locked Status Code 0 = never been unlocked before by the fastboot oem unlock command
Unlocked Status Code 1 = unlocked in its original factory state and never been locked before*
Locked Status Code 2 = locked but has been unlocked before
Unlocked Status Code 3 = currently unlocked
*You can't buy a phone in the Status Code 1 Unlocked state in the US. You can buy them off of Tao Bao and they are referred to as "factory" devices. They are "removed" from the Chinese factory before they are locked. However, I would not do that as I am not sure if they are on the global blacklist or not.
The Software state can be any of the following:
qe 0/0 = never been rooted
qe 1/1 = currently rooted
qe 0/1 = not currently rooted but rooted at some point in the past
States qe 1/1 and qe 0/1 will show the Software status as modified IME. So Software Modified means modified currently or at some point in the past.

Related

[Q] Root Question related later ota

after a few hours searching, I am still a bit confusing on following question:
1. trip rootchecker
If I do not choose do this during rooting, in other word, I only have adb shell root.
a) should I still be able to install twrp and flash other rom? my impression is "yes", am I right?
b) But if I choose do this, then my warranty is gone. If I later flash back the stock,
will this be wiped and "forget"? i.e. the warranty is back?
Or is this "root checker" will send somthing to LG once it is tripped, hence warranty
is permanently voided?
2. ota
It seems once rooted, one can not take any ota, right? even the kitkat in future?
would "trip rootchecker" matter in this case?
even though thanks to thecubed, it seems we do have a solution.
If you choose not to trip the root checker, root will not work properly and neither will the apps that require it.
It doesn't send any info to LG or your carriers. All it does is... If in the future you break your phone somehow and take it into your carrier store to get it fixed, they will check the phone to see if it's ever been rooted. If it's been tripped, it'll give a number code on the screen to tell them it either was rooted in the past but isn't anymore, is currently rooted, or was never rooted.
Then it will be at the store's discretion on whether or not they'll help you out or make you pay full price to fix it or get it replaced.
I don't know how it is for the G2, but I know awhile back some newer HTC phones got S-OFF which allowed them to reset the root checker to make the device think it's never been rooted. Our phones may have a similar method out there somewhere... Though probably not as it'd be fairly big news. I am however, willing to bet that there is a crack team or two working on disabling that for our devices.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.

[Q] SM-N9000W major problem help

Hi all, I'm new to XDA so hopefully someone can help me. I purchased a brand new unlocked note 3 N9000W8 in canada from a cellphone store on Monday Morning. The phone was great and worked without a hitch and had android 4.3 on it.
Later on during the day, there were numerous news headlines regarding a 4.4.2 was officially released. So i decided to do the software update. With failed attempts with the message "Your device have been modified, Software updates are not available"
I checked my Settings > about device > status > device status and it states custom or modified. I am unsure how this is possible thinking it was a brand new phone. After some in depth reading i powered off the phone and check the android download mode (power, home button vol down key combo).
It states device status: custom, firmware: custom, knox 0x1 (which meant my warranty was gone essentially). I proceeded to call the shop i purchased the phone at, and the manager said they buy the phones from the distributor which unlocks them before it gets in their hands. so it must have been rooted prior to me receiving the phone.
Long story short...i know its been quite the reading already my appologies. I used samsung KIES to backup the phone and it updated it back to the stock firmware 4.4.2. I was prepared to loose the root as i dont need it. More concerned about the warranty. With the device and firmware status back to original i can now do OTA updates, however
Problem i have now is after the factory firmware upgrade to stock, my sim no longer works on the network. Seems as if the device has a sim lock, but it never asked for one. A local cellphone shop in st.catharines said there might be an issue with the baseband after the official update.
before the update, i tried all the suggestions such as unmounting the sd card, wiping cache, using supersu to unroot.
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
i just realized this was posted in the wrong section of the forum. sorry mods, can it be moved to Q/A?
tedmonddo said:
Hi all, I'm new to XDA so hopefully someone can help me. I purchased a brand new unlocked note 3 N9000W8 in canada from a cellphone store on Monday Morning. The phone was great and worked without a hitch and had android 4.3 on it.
Later on during the day, there were numerous news headlines regarding a 4.4.2 was officially released. So i decided to do the software update. With failed attempts with the message "Your device have been modified, Software updates are not available"
I checked my Settings > about device > status > device status and it states custom or modified. I am unsure how this is possible thinking it was a brand new phone. After some in depth reading i powered off the phone and check the android download mode (power, home button vol down key combo).
It states device status: custom, firmware: custom, knox 0x1 (which meant my warranty was gone essentially). I proceeded to call the shop i purchased the phone at, and the manager said they buy the phones from the distributor which unlocks them before it gets in their hands. so it must have been rooted prior to me receiving the phone.
Long story short...i know its been quite the reading already my appologies. I used samsung KIES to backup the phone and it updated it back to the stock firmware 4.4.2. I was prepared to loose the root as i dont need it. More concerned about the warranty. With the device and firmware status back to original i can now do OTA updates, however
Problem i have now is after the factory firmware upgrade to stock, my sim no longer works on the network. Seems as if the device has a sim lock, but it never asked for one. A local cellphone shop in st.catharines said there might be an issue with the baseband after the official update.
before the update, i tried all the suggestions such as unmounting the sd card, wiping cache, using supersu to unroot.
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
Click to expand...
Click to collapse
When the distributor told you that the phone had been modified to enable an unlock, why did you say, "I was prepared to loose root as i dont need it"... the problem is fairly obvious, you had a software-unlocked phone and even though the seller told you that you would lose your unlock, you wiped it back to factory anyway lol...
honestly though, that's extremely sketch, lemme know that shop and I'll report them to BBB, you should never be paying for a cell phone that comes rooted unless your buying something from pacific mall, there are several options for you to unlock the phone, using software, hardware, or IMEI unlock codes
tedmonddo said:
...
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
Click to expand...
Click to collapse
You had a pre-rooted software-unlocked phone (that was originally network-locked). Your warranty to Samsung is completely void, you should get something in writing (or record on audio) from the guy that sold you the phone as to the warranty of the phone.
Other than that - you can buy a network unlock code for something like 15 USD or so.

Fail safetynet even after complete wipe!!

So my safetynet checker says I failed even though I completely wiped all data! Even the sdcard data! I did a complete fastboot flash of all the system image files including the userdata file. I did not root the phone yet and I don't plan to either, I just want Android Pay.
CTS Profile Match = fail
That's what I get from the safetnet checker...My only other idea is to relock and unlock the bootloader again.
It seems you're not alone. I saw a few posts on reddit describing the same thing. The consensus is that Google may possibly be requiring locked bootloaders as well now for Safetynet.
Granted, I live in Canada and we don't have Android Pay yet. But I just won't even bother if this is the case.
It appears you are right mattkroeder...I relocked my bootloader and it passed, I unlocked it again and it failed....
Damn! I could not figure out why my Pay didn't work today. I'm stock, unlocked, custom ROM, no root. I just tried safetynet and its red. That seems like a bigger hurdle then not allowing rooted phones no pay.
It has been said all along that it was a losing battle....I just hoped that they would eventually block any and all root access at worst. Blocking the bootloader unlock I think puts a nail in the coffin of that little game. You will only be able to have Android Pay with a completely stock phone....
Looks like it is the case now. Now I'm gonna waste 2-3 hours of my precious life, reverting everything back to stock and locked.
GatorsUF said:
It has been said all along that it was a losing battle....I just hoped that they would eventually block any and all root access at worst. Blocking the bootloader unlock I think puts a nail in the coffin of that little game. You will only be able to have Android Pay with a completely stock phone....
Click to expand...
Click to collapse

Can you remove the unlocked bootloader warning when powering on device?

As the title implies. Is this possible? if so, how?
I'm talking about the one that says "your device can't be checked for corruption" .... etc
No
It's not the end of the world, but I'm hoping that someone will find a workaround for this.
Seeming that it's allowed and doesn't break manufacturers warranty, it seems rather odd to consistently display this at boot after the first time.
It's because you bootloader is unlocked, therefore it doesn't pass certain security checks. It's like that with the Nexus 6p and I'm sure it's like that with the pixel. That will never change I don't believe.
Also becareful not to ever lock your bootloader while you have a custom recovery installed or you will brick your device.
Eric214 said:
It's because you bootloader is unlocked, therefore it doesn't pass certain security checks. It's like that with the Nexus 6p and I'm sure it's like that with the pixel. That will never change I don't believe.
Also becareful not to ever lock your bootloader while you have a custom recovery installed or you will brick your device.
Click to expand...
Click to collapse
My Nexus 4 and 6 didnt have that warming but my Moto E 2015 does. I think its based on the phone. All UNLOCKED Bootloader.
Warning Sucks!
It's a security requirement set by Google (to show a warning message like that) as part of the agreement for OEMs to use Android on their devices. It will not be going away anytime soon.
The Axon 7 has a patch to get rid of this warning...

To restore or not to restore...

I purchased 3 PH-1's off Amazon during the last few months, right before they skyrocketed in price. One i use for loading stuff like elemental-x kernals and magisk modules/systemizer, aka my test phone. Today i noticed the bottom half of the screen has 3-4 small light spots visible on dark screen applications. The phone in question is still returnable to Amazon since its not even 30 days old.
So the question is do i send it back, as is, with expressed knowledge that the software is fine but the screen itself is defective? Will they get it back and boot it up and see the unlocked bootloader screen and void warranty? Should i attempt to relock the phone?
Its rooted on oct. pie update with 3.09 elemental x on it. If i restore OEM kernal via the backup, uninstall magisk and reflash stock boot image, factory reset the phone and then flashall oct. 9.0 fastboot files again, does anyone believe i'll have a issue relocking it after all that? I've spent a boat load of time reading XDA and I've unlocked/flashed/relocked my wifes PH-1 when i first got it and it went fine but im wondering if ive gone to far on this one and will Amazon even care if its unlocked when returned? Chance calling Amazon and asking? Hate for it to count against my amazon return history.
Thoughts? Edit* its barely noticeable unless its a black, lit screen. Opinions on if it is even worth it to chance relocking/bricking or sending it back unlocked? TWRP has never been loaded on the phone btw.
Twowong4words said:
I purchased 3 PH-1's off Amazon during the last few months, right before they skyrocketed in price. One i use for loading stuff like elemental-x kernals and magisk modules/systemizer, aka my test phone. Today i noticed the bottom half of the screen has 3-4 small light spots visible on dark screen applications. The phone in question is still returnable to Amazon since its not even 30 days old.
So the question is do i send it back, as is, with expressed knowledge that the software is fine but the screen itself is defective? Will they get it back and boot it up and see the unlocked bootloader screen and void warranty? Should i attempt to relock the phone?
Its rooted on oct. pie update with 3.09 elemental x on it. If i restore OEM kernal via the backup, uninstall magisk and reflash stock boot image, factory reset the phone and then flashall oct. 9.0 fastboot files again, does anyone believe i'll have a issue relocking it after all that? I've spent a boat load of time reading XDA and I've unlocked/flashed/relocked my wifes PH-1 when i first got it and it went fine but im wondering if ive gone to far on this one and will Amazon even care if its unlocked when returned? Chance calling Amazon and asking? Hate for it to count against my amazon return history.
Thoughts? Edit* its barely noticeable unless its a black, lit screen. Opinions on if it is even worth it to chance relocking/bricking or sending it back unlocked? TWRP has never been loaded on the phone btw.
Click to expand...
Click to collapse
I myself have locked bootloader 4 times...just run a oct bts and let it boot up..then if it's boots reboot to bootloader and relock it
Twowong4words said:
I purchased 3 PH-1's off Amazon during the last few months, right before they skyrocketed in price. One i use for loading stuff like elemental-x kernals and magisk modules/systemizer, aka my test phone. Today i noticed the bottom half of the screen has 3-4 small light spots visible on dark screen applications. The phone in question is still returnable to Amazon since its not even 30 days old.
So the question is do i send it back, as is, with expressed knowledge that the software is fine but the screen itself is defective? Will they get it back and boot it up and see the unlocked bootloader screen and void warranty? Should i attempt to relock the phone?
Its rooted on oct. pie update with 3.09 elemental x on it. If i restore OEM kernal via the backup, uninstall magisk and reflash stock boot image, factory reset the phone and then flashall oct. 9.0 fastboot files again, does anyone believe i'll have a issue relocking it after all that? I've spent a boat load of time reading XDA and I've unlocked/flashed/relocked my wifes PH-1 when i first got it and it went fine but im wondering if ive gone to far on this one and will Amazon even care if its unlocked when returned? Chance calling Amazon and asking? Hate for it to count against my amazon return history.
Thoughts? Edit* its barely noticeable unless its a black, lit screen. Opinions on if it is even worth it to chance relocking/bricking or sending it back unlocked? TWRP has never been loaded on the phone btw.
Click to expand...
Click to collapse
According to the various laws an unlocked boot loader cannot be used to deny a hardware warranty.
On the other hand just install the stock ROM and lock the BL.
What is BTS ?
I myself have locked bootloader 4 times...just run a oct bts and let it boot up..then if it's boots reboot to bootloader and relock it
Click to expand...
Click to collapse

Categories

Resources