Software status: modified; never rooted - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

I noticed that my Droid Turbo shows Software Status: modified, despite never rooting it or unlocking the bootloader. The bootloader is still locked. This is a warranty replacement from Verizon that keeps randomly rebooting on me (despite getting my old one replaced for that same reason). Did the previous owner root it and is that why it says Modified? Will this be an issue if I get the phone replaced yet again?

mastertr said:
I noticed that my Droid Turbo shows Software Status: modified, despite never rooting it or unlocking the bootloader. The bootloader is still locked. This is a warranty replacement from Verizon that keeps randomly rebooting on me (despite getting my old one replaced for that same reason). Did the previous owner root it and is that why it says Modified? Will this be an issue if I get the phone replaced yet again?
Click to expand...
Click to collapse
I've read about other people experiencing this. I doubt that Verizon will care. If they do, get a warranty replacement directly from Motorola instead. It's painless, free and they only inspect for physical damage.

Related

[Q] Sending it in for replacement, but bootloader unlocked

My camera stopped working. Any attempts to use it (via the camera app, goggles, camera 360, etc) gives me a force close.
I called HTC, and they're sending me a replacement, but if the warranty is void, they will charge me a repair fee once they receive the one I have now.
Since it is most likely a hardware issue and not a software, I've heard of instances of HTC letting it slide, but I don't want to pay up to $200 for a replacement motherboard if that's the problem.
Anyway I can improve my chances? I know the bootloader can't be locked.
Flash everything completely back to stock before sending I guess.
thats what ive heard as well, flash stock recovery, boot, data, system
my first Nexus had an unlocked bootloader. I just flashed the Stock ERD2.1 to it and threw it in the box.
Nothing said about it.
My new one, I did the SD card trick in the bootloader to root it without unlocking the bootloader. I guess now-a-days it is a much simpler process.
I have sent 2 phones with unlocked bootloaders into HTC and i haven't been charged anything. For my third phone i justed the root without unlocking bootloader.
well the camera magically started working again, and I already put in my credit card info and the other one is shipped
since it isn't broken anymore, should I be concerned?

S6 edge auto custom binary?

Ok so this s6 i have had for less then 1 month is becoming a huge hassle. First it kept restarting by itself even during bootup. Sent in for repair samsung said nothing was wrng with it and sent it back... Got it back first startup it rebooted... Then after uaing it to 2% i charged it up and booted the phone, got a message "unauthorized att softwsre detected". Went to att they tried to reflash didnt help, told me to go to bestbuy samsung kiosk, they tried to reflash nothing... Told to call samsung and they would fix it, sent it in and they said thwy cant do anything cause its rooted. What can i do? And how did this even happen.
Did you buy it new, or used?
Brand new was orderd from att direct.
I actually have a video of the system saying it was custom then after i rebooted it went back to offical.
Actually starting to think samsung repair rooted the phone cause they couldnt repair it...
I'd contact Samsung again, explain the situation, and see if they'll replace it.
Tried they said cause its rooted they can't even touch it and since its rooted it voids the warranty and any connection to them... like WTF? My friend is on the phone with some manager at samsung right now :/. But my hopes are low. How does a company like this have such retarded policies. They can't even check the phone if its actually rooted...(they said they can't touch it cause the knox counter was tripped) I assume the binary somehow got messed up, hardware related? I bet if they just checked the software it would be official with chunks of code missing or something. I have video proof of it going from custom to official by itself without me having it plugged into anything. I have no clue who i can go to about this issue anymore, Phone is brand new (one month) and im still paying for it under ATT Next program...
Have AT&T check the serial and imei of the phone against your original order. Perhaps you got sent back the wrong phone from the repair depot? AoN
I checked the serial once i recieved it, it was the correct phone. I have video proof of it "rooting" it self. Basically the phone said it was custom then it a d it was offical after i rebooted it.(of course this was taken in two videos but u can see the time so no tampering could have occured.)
https://m.youtube.com/watch?v=WpxGI644OXA
https://m.youtube.com/watch?v=XJva5kmFLjE
So i figured out why it says i have a custom software... The BestBuy Samsung Rep flashed the wrong build to my device. They flashed "G925AUCU1AOE2" which i don't think is released yet or at least not pushed to my device. So any suggestions to what i can do? They cased my warranty to be voided and i still have the restarting issues.

stuck on bootloader

Hey guys..so my moto x gen 2 whent on the blink a month ago the same day google did there ota update..
called motorola and made me go thru tons of combinations to restore it..
it seems like there is a corrupt image..so sent it out for repaire..
telus says that there is a broken chip and charged me 150$...
so refused since the phone is almost new and looking new also..
sent it to a local ubreakifix...they say they scanned the phone has nothing broken at all it is firmware related but only moto can flash it...
so called moto and complained..lol they gave me a pre-paid pkg to there repaire center,,(furture tel)..
got the phone back not repaired saying tampered boot [email protected]#$%%
i know that the web site says the warrantie is voided when boot loader is unlocked..but even the 3 reps from moto and telus never mentioned it...
so long story short it is not repaired and woundering if there a way to recover,flash or what ever..
1-tried the volume up power combos.gets to recover recovers but does not reboot.
2 -went thru all features one by one and still does not reboot...
This is why I don't bother rooting mine. There seems to be too many issues with these phones that you just never know when you'll be required to return them for a warranty repair.
true never again..sticking to my Samsung...i just want to repair it for my son..

Boot loop replacement phone

My phone finally got the boot loop error my phone mfg date is may 2015 but my concern is I've sent my phone to lg it's out of warranty and is rooted will lg just send it back since it's rooted or actually fix my phone. If anyone has this happens to them please let me know your end results thank you
Sent from my iPhone using Tapatalk
bleedingthru said:
My phone finally got the boot loop error my phone mfg date is may 2015 but my concern is I've sent my phone to lg it's out of warranty and is rooted will lg just send it back since it's rooted or actually fix my phone. If anyone has this happens to them please let me know your end results thank you
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
its unknown.. they may fix it they may not. sometimes with warranty and root no fix.
Ya it's been out of warranty for a year so I'm keeping my fingers crossed lol thanks for the reply
Sent from my iPhone using Tapatalk
i just got my second warranty replacement device TODAY(I am grandfathered into the original $10 per month Jump!/insurance program)
the first time was back in Oct, the G4 went into bootloop and would not fully power on. would at most show the LG boot logo and then repeat. I had an unlocked bootloader, a custom recovery, and a custom rom in place. there was no physical damage. phone worked fine until the bootloop.
result: tmobile warranty replacement. never heard anything regarding any software modification/rooting/bootloader unlocking.
the second time, phone started acting up and having random reboots and sometimes freezing. then it appeared to be stuck in a bootloop, but would sometimes attempt to load the boot animation, and once or twice actually loaded the custom rom I was running, but would then freeze within minutes of operation. Bootloader was unlocked, custom recovery, custom rom.
This time, because I was able to get it to boot long enough without tinkering with the device at all..... I was able to stay booted long enough to initiate a LGUP .kdz install which returned the device to stock. i was then able to adb reboot bootloader, and oem bootloader lock. so the phone had zero signs of ever being "tampered" with.
of course the thing turned on today while i was in store, loaded up as if it was a fresh install. I assured the customer serice rep that it was having issues, and that I would not be replacing the device under warranty if needn't be.
result: tmobile warranty replacement.
he laughed at me and smiled, as if i were a typical samdung, i mean typical Tmobile customer who didnt know anything abut my device.
ElfinJNoty said:
i just got my second warranty replacement device TODAY(I am grandfathered into the original $10 per month Jump!/insurance program)
the first time was back in Oct, the G4 went into bootloop and would not fully power on. would at most show the LG boot logo and then repeat. I had an unlocked bootloader, a custom recovery, and a custom rom in place. there was no physical damage. phone worked fine until the bootloop.
result: tmobile warranty replacement. never heard anything regarding any software modification/rooting/bootloader unlocking.
the second time, phone started acting up and having random reboots and sometimes freezing. then it appeared to be stuck in a bootloop, but would sometimes attempt to load the boot animation, and once or twice actually loaded the custom rom I was running, but would then freeze within minutes of operation. Bootloader was unlocked, custom recovery, custom rom.
This time, because I was able to get it to boot long enough without tinkering with the device at all..... I was able to stay booted long enough to initiate a LGUP .kdz install which returned the device to stock. i was then able to adb reboot bootloader, and oem bootloader lock. so the phone had zero signs of ever being "tampered" with.
of course the thing turned on today while i was in store, loaded up as if it was a fresh install. I assured the customer serice rep that it was having issues, and that I would not be replacing the device under warranty if needn't be.
result: tmobile warranty replacement.
he laughed at me and smiled, as if i were a typical samdung, i mean typical Tmobile customer who didnt know anything abut my device.
Click to expand...
Click to collapse
See what I'm worried about is my phone had. Been out of warranty since November of 2016 so I'm wondering if they are gonna charge me or even fix it since im rooted
Sent from my iPhone using Tapatalk
bleedingthru said:
See what I'm worried about is my phone had. Been out of warranty since November of 2016 so I'm wondering if they are gonna charge me or even fix it since im rooted
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
mine was only considered warranty replacement via Tmobile Jump!+Insurance(maybe thats why i pay the extra $12 a month?)
..... really cant comment on any other type of situations.
good luck

Sent out for warranty repair, now permanently locked bootloader

Just a warning for those who have an unlocked Pixel that you want to send in for repair.
I bought a 4xl that was a Google refurb in excellent condition. Bootloader was unlockable. I had lineage 19 on it for a while, but there was an intermittent touch issue on the screen.
So I reloaded the latest factory firmware, relocked the bootloader, and sent it in for warranty repair. They did repair it under warranty and sent it back.
Now OEM Unlocking is permanently disabled. I have a nice shiny repaired phone that I can't unlock.
EDIT: Decided to connect it to the internet but still no dice. BUT a few reboots later, the OEM unlock toggle suddenly enabled. Not sure why it did that - I've never had that happen before. It was either grayed out or not - no way for a user to change that ever.

Categories

Resources