Database Info

[Q]about root/unroot and your warranty (wt19i)

can I root my phone without voiding warranty?
and if I rootit can I unroot it and return to its original state?
thank you

jusleen said:
can I root my phone without voiding warranty?
and if I rootit can I unroot it and return to its original state?
thank you
Click to expand...
Click to collapse
teoreticaly yes, you lose warranty.
but you can unroot it.

Actually technically the answer is NO. Rooting your phone should not in and of itself void your warranty, but the things you can do may and most likely will. For example lets say you root your phone and keep the stock kernel just debloat the stock ROM, and then the volume buttons stop working...unless you did hardware mods it would be under warranty. When I rooted my HTC using the HTCDev method to unlock the bootloader the disclaimer said it MAY, not that it will or does, and a few months after rooting and reading their warning I sent in my phone for warranty repair/replacement with no problems, even though my phone was documented as being rooted. Now if you hard brick your phone flashing a ROM with bad mount points that is a different story altogether.
A few years back I had a Samsung Interceptor that I had rooted and it had an issue with a physical button (Power button I believe), I brought my phone to Sprint and the rep saw it was rooted (before I sprung for Superuser Elite to hide the app). His words to me were that as long as NO hardware mods were done and the phone can be flashed back to a stock state it would still be covered under warranty. Important to note...Carriers will not service a phone with a custom recovery PERIOD, which is why I left the Sprint store and reflashed the stock image to the phone.
My advice to people who are concerned with their warranties is to know exactly how to get it back to stock...before its ever customized. The reason for this should be obvious. And don't let it leave your hands (sent out for repair, or brought to the back for testing) prior to flashing it back to stock

i won't use anything larger than 4"2

ItzCrooK2UxD said:
Actually technically the answer is NO. Rooting your phone should not in and of itself void your warranty, but the things you can do may and most likely will. For example lets say you root your phone and keep the stock kernel just debloat the stock ROM, and then the volume buttons stop working...unless you did hardware mods it would be under warranty. When I rooted my HTC using the HTCDev method to unlock the bootloader the disclaimer said it MAY, not that it will or does, and a few months after rooting and reading their warning I sent in my phone for warranty repair/replacement with no problems, even though my phone was documented as being rooted. Now if you hard brick your phone flashing a ROM with bad mount points that is a different story altogether.
A few years back I had a Samsung Interceptor that I had rooted and it had an issue with a physical button (Power button I believe), I brought my phone to Sprint and the rep saw it was rooted (before I sprung for Superuser Elite to hide the app). His words to me were that as long as NO hardware mods were done and the phone can be flashed back to a stock state it would still be covered under warranty. Important to note...Carriers will not service a phone with a custom recovery PERIOD, which is why I left the Sprint store and reflashed the stock image to the phone.
My advice to people who are concerned with their warranties is to know exactly how to get it back to stock...before its ever customized. The reason for this should be obvious. And don't let it leave your hands (sent out for repair, or brought to the back for testing) prior to flashing it back to stock
Click to expand...
Click to collapse
Then do you know how to get it back to stock after i rooted it??thanks

jusleen said:
Then do you know how to get it back to stock after i rooted it??thanks
Click to expand...
Click to collapse
I can probably point you in the right direction...did you unlock the bootloader or not? I am seeing a few unroot methods for locked bootloaders. If you did unlock the bootloader you will need to lock it back. Also it is important to note that some bootloaders will say *relocked* after relocking them, and not *locked* if it says *relocked* they will know it has been rooted. This is NOT a problem because once again having root access does not void the warranty, but you should be aware that if it says relocked they will know it has been rooted. This link has a root/unroot tool that may help it makes no mention of a specific firmware for your model phone so it should be fine. Also this video should help with the relock procedure but not knowing the phone I would need more specific details. Firmware and method used to root/unlock bootloader if you unlocked it. One of the relock procedures can be see here
*EDIT* I did a little looking and thought you might find this of interest. About midway through there is a section about warranty claims and returns...I didn't sign up so I can't see the links there but it should help .

[Q] Z3 Root Reality Check

I've been watching the developer board regarding the root and locked bootloader issue, and I've spent hours researching this and have yet to find a solution that's known to work without loss of something, likely a permanent or semi permanent loss. My device is a Z3 model D6616. I'm unhappy with the phone for several other reasons, but haven't owned an un-rooted phone for some time, and prefer keeping this phone if I can root it successfully. Root with stock firmware is my objective and am only interested in responses from people that have themselves rooted (and dealt with bootloader issues) a Z3.
- Root phone installing current T-mobile stock firmware.
- Known loss of function: Sony DRM dependant features/funtion only (from memory, mostly related to camera low light performance and DRM playback issues)
- Other loss of function experienced with stock features, or any other problem with any other app. Especially concerned with root dependant features of Play apps? Also ad blockers?
- Waranty loss (potential) and loss of OTA updates understood.
- Feature/function loss with workarounds or fixed that survive power cycle?
- Expect permament bootlocker inability to relock
- A link to the specific process you used, any problems you encountered whatever the cause. For example it usually takes me at least 3 attempts to root using any complex process, and I always read through 5 times before starting and download every needed file and program in advance.
Again: Sony Xperia z3 D6616 T-mobile
Firmware: 4.4.4 23.0.3.1.123
Software: D6166 R16B
In the past, I've had the most problems when an understood part of a process is not explicitly stated, or I've ignored or misunderstood a step. Plugging and unplugging from usb to PC a typical example. I don't have the technical know how to critique or ignore, so always attempt to follow all instructions without variance. I've had some problems, and most were solved by starting the process again. I hesitate to ask for help since the last time I did that I was attacked for witholding information when asked if I had backed up the phone. Since i didn't have access to the PC at the time of the question I honestly answered I didn't know (since I had attempted to but couldn't confirm). If you've ever answered a question here implying the request or requester is stupid or dishonest, I'm fully aware of my ignorance and my own integrity, and other personality traits, so please ignore this request, which accepts my lack of knowlege and has no tolerance for your issues not previously resolved through your own peaceful and respectful process.
Please only respond if you have personally rooted this specific phone model. If you have not, but know someone who has, please ask them to review this post and respond.

Nobody has rooted this phone without unlocking the bootloader. If you unlock to root, you will permanently lose DRM keys from the TA partition with no way to recover. No current root method works on 4.4.4 on the Z3. No one knows when or if an exploit will be found. We all want root. If you want it now, unlock the bootloader. If you can wait, wait. It's your call either way. As soon as a root method surfaces, best believe it will be in these forums. I'll be waiting with you...

First of all, check *#*#7378423#*#* to see if you bootloader can be unlocked or not.
Coz I think 6616's bootloader is unlockable.

freddy1991 said:
First of all, check *#*#7378423#*#* to see if you bootloader can be unlocked or not.
Coz I think 6616's bootloader is unlockable.
Click to expand...
Click to collapse
This is true. D6616 owner here, T-MO not unlockable yet :/ eagerly awaiting root as well as I really enjoy the z3, maybe even more than my Nexus 6 (gasp, blasphemy!)

Thanks For the Responses
freddy you addressed my concern, exactly. My phone reports:
Rooting Status:
Boot Unlocker Allowed: No
Although variants of the z3 have been bootlocker unlocked and rooted, I have not found a clear claim that was successfully done with D6616 z3. Since I'm a new T-mobile customer, this and their attitude about it are a poor way to start. I have a HTC phone I haven't returned, maybe I can get them to take the Z3 back instead. While I have benefited from and appreciate the great work so many people have done to make our phones usable and available to us, I've seen how carriers, mfgs, and users push good phones to market crippled by junk and unecessarily locked down. it's time to consider the mamufacturers that have been successful building good phones and selling in places like China at much lower prices.
Regarding any loss of DRM, I couldn't care less. This phone takes worse low light photos and video than my rooted Samsung G3, making it functionaly useless to me. Add to that the lack of a rational UI for telephony and IM, and done with Sony.
To be clear, if the bootloader can be unlocked and the phone can be rooted and you have done this yourself, please post.

Well...
I think there is no way you could unlock the bootloader of 6616.
The only way is to wait for the root on locked bootloader.
Check here http://forum.xda-developers.com/showthread.php?t=2940539
But that means you have to stick in the .93 firmware, even if the exploit is also usable for Z3.
Or return your 6616 and buy a 6603 or 6653 variant.

BREAKING NEWS
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598

Man, No bootloader unlock = Useless phone

HORiZUN said:
BREAKING NEWS
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Click to expand...
Click to collapse
Nope.
http://forum.xda-developers.com/showpost.php?p=58468332&postcount=815

I'm similarly confused about this whole thing, this new Giefroot program means we can all potentially get root for our devices, but we still lose the DRM keys right? So that means we can never have the Sony camera/image processing processes back again right?

Thwwack said:
I'm similarly confused about this whole thing, this new Giefroot program means we can all potentially get root for our devices, but we still lose the DRM keys right? So that means we can never have the Sony camera/image processing processes back again right?
Click to expand...
Click to collapse
NO
Unlocking the bootloader = loss of DRM
Rooting that does not involve unlocking the bootloader means you keep the DRM keys

gregbradley said:
NO
Unlocking the bootloader = loss of DRM
Rooting that does not involve unlocking the bootloader means you keep the DRM keys
Click to expand...
Click to collapse
Thanks, I'm new to Android and this is all over my head. To clarify, Giefroot does this without unlocking the bootloader?
It's all pretty frustrating, I gotta say... I'd love to install Cyanogenmod on this, but losing key features on the device is a pretty harsh trade off.

Thwwack said:
Thanks, I'm new to Android and this is all over my head. To clarify, Giefroot does this without unlocking the bootloader?
It's all pretty frustrating, I gotta say... I'd love to install Cyanogenmod on this, but losing key features on the device is a pretty harsh trade off.
Click to expand...
Click to collapse
Yes, giefroot does not unlock the boot. There is only one way to do that and that is to obtaining the code from sony and fastboot it either manually or using flashtool.

Delete

Warranty with T-Mobile

So I have received a "Certified Pre-Owned" Nexus 5 from T-Mobile just a couple days ago. Within the first few hours, I rooted it. At this point I could no longer install (but still received) OTAs, and IIRC that is because the system partition has been altered. I eventually did unroot, but I still could not install OTAs. Now, there is a hardware issue with the phone: it will not vibrate properly anymore. And I have tried those solutions like pressing on the back. So will need to return this phone for a replacement or repair. I have read somewhere that T-Mobile runs a diagnostic tool to check the phone software. My phone is not rooted, and I have not unlocked it or altered the ROM in any way, but will T-Mobile know that my system partition is different? Am I still covered under warranty?

You could just flash the latest entire factory image and relock the bootloader - not sure how Tmobile would be able to tell anything different especially since the nexus 5 isn't a carrier locked device.

janjanrex said:
You could just flash the latest entire factory image and relock the bootloader - not sure how Tmobile would be able to tell anything different especially since the nexus 5 isn't a carrier locked device.
Click to expand...
Click to collapse
I don't plan to unlock my bootloader at all for a while. I unrooted with KingRoot, and now my phone is identical to stock except for a couple of files in the system partition that are traces of the root. I know this because OTA installations will result in an error. But that is the only thing that differs from a stock device. Will T-Mobile be able to access the system partition or somehow force an OTA upon it and find that it was once rooted? This is what I fear. What exactly does T-Mobile do when it receives the phone to make sure it had warranty?

Actually, what I would like to know for my peace of mind is...
Is there any way that T-Mobile can find out that I rooted?

janjanrex said:
You could just flash the latest entire factory image and relock the bootloader - not sure how Tmobile would be able to tell anything different especially since the nexus 5 isn't a carrier locked device.
Click to expand...
Click to collapse
I used the Nexus Root Toolkit to unlock, flash stock, unroot, lock, set tamper to false, etc. I can install OTAs now, and there is no way that I can think that my phone can be seen as altered. Just to confirm:
Is there any way now that T-Mobile will know that I did anything?

Question Relocking bootloader

I've been planning to unlock my bootloader to install TWRP and GSI's on this device but I've seen the warning message you get every time you restart the device. I have plans to sell this device in the future, so I would like to know if there is a way to relock the bootloader or remove the warning message on startup. Thanks.

Yes you can relock the bootloader, the process is done the exact same way that you use to unlock it. The warning message will be removed and you will only be able to flash stock binaries.
But for Samsung phones specifically there is something to note, there is something called an "E-Fuse" that will be "tripped" when the bootloader is unlocked for the first time. There is no way to revert the phone back to a pure factory state after this happens. The feature is called Samsung Knox and it prevents a few (Samsung based) features from working.
You can read a bit here - https://en.wikipedia.org/wiki/Samsung_Knox

I know about tripping Knox. I don't really care about not being able to use Secure Folder or S Health so it's not an issue for me. My main concern is to remove the obnoxious warning when booting the device as it can be intimidating to a non savvy potential buyer. Anyways thanks for the reply.

Buying a used phone. Is the second-hand device trustworthy and safe to use?

[Apologies for being a noob, I tried my best to do the homework]
I want to buy a used Pixel 2 (or Pixel 3). There is some general advice on the internet reminding to check:
(i) for physical damage
(ii) if ESN / IMEI has been blacklisted
(iii) if the device is compatible with a carrier (communication standard, uses SIM and not e-SIM, not carrier locked)
(iv) and warning that the device can break or become blacklisted after the purchase.
All of the above is associated with a risk, which is limited to the amount of money paid.
But my primary concern is the risk from using the second-hand device where privacy is critical (email, online banking, 2FA through SMS). How do I make sure the previous owner hasn't planted a backdoor? If I trust Google, what are the reasonable steps to ensure that the device hasn't been tampered with by someone else? In particular:
(1) How do I check on Pixel 2 that the firmware, bootloader, OS are the original ones?
(2) If the device had been bootloader unlocked and/or rooted, is it possible to restore the original images, re-lock the bootloader to be confident that no one (but Google) will spy on me?
(3) Is there anything I am missing?
(4) Which of these are probably different on Pixel 3 and should be asked on Pixel 3 forum?
I barely understand the difference between the bootlocker and the recovery, and I would appreciate clear answers very much.
Related:
- A related thread mentions telling apart Verizon and unlocked versions of Pixel 2:
Buying Pixel 2 on Craigslist any tips to avoid issues?
Hi, I would like to buy a used Pixel 2 off Craigslist and since I am not familiar with the Pixel 2 I hope you can help me make sure I don't get scammed. I know I need to check that the IMEI is not blacklisted (can run it through the swappa IMEI...
forum.xda-developers.com
- A similar question was asked about Galaxy Note 9. One senior member says "Hell, back in the day we could reset knox counters ... even checking knox isn't a full proof method". Another says "So rest assured if your Warranty Bit is not 0x1 a Custom Binary has never been flashed". I am confused, as there is no concensus.
Bought used. Security concerns?
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything...
forum.xda-developers.com
- Here someone says "Really easy to relock" about OnePlus 5. I wonder if the same is true for Pixels 2/3?
Risk of used phone with unlocked bootloader?
Hey guys this is probably a lame question... does any risk come with buying a phone with an unlocked boot loader? I bought an OnePlus 5 from ebay used in great shape. The seller advised the the phone was rooted with Android 10. When i start the...
forum.xda-developers.com

Reboot the phone, and see if the yellow exclamation mark comes up saying the bootloader was modified.
If you don't see that, it means the Pixel 2 bootloader was never unlocked and a custom ROM was never flashed to the device.
Since all Pixel 2 phones would be out of warranty now, the only way to ensure security is to flash a trusty ROM yourself.

kodina said:
Since all Pixel 2 phones would be out of warranty now, the only way to ensure security is to flash a trusty ROM yourself.
Click to expand...
Click to collapse
Thanks for you response, but I am not sure I understand the last bit. Do you mean I would have to flash a trusty ROM myself because there are no certified service centres that would accept the phone, as the warranty has expired? Or do you mean that there are no automatic updates or supported ROMs because of the end of life or something?

up!

wiltingenthusiasm said:
Thanks for you response, but I am not sure I understand the last bit. Do you mean I would have to flash a trusty ROM myself because there are no certified service centres that would accept the phone, as the warranty has expired? Or do you mean that there are no automatic updates or supported ROMs because of the end of life or something?
Click to expand...
Click to collapse
No, I mean even if the bootloader is locked, even if the original owner never flashed a custom ROM, the device (in theory) could still have had been rooted in the past, unknown apps installed, root removed and you would never know. Hoewever, this is all in theory, but it is possible, and only applies if you are paranoid about security.
Otherwise, reboot the phone, no bootlaoder warning = 99% safe to use.

kodina said:
No, I mean even if the bootloader is locked, even if the original owner never flashed a custom ROM, the device (in theory) could still have had been rooted in the past, unknown apps installed, root removed and you would never know. Hoewever, this is all in theory, but it is possible, and only applies if you are paranoid about security.
Otherwise, reboot the phone, no bootlaoder warning = 99% safe to use.
Click to expand...
Click to collapse
Oh, I see. And a factory reset would not help either, because it does not recover the OS from a reserve copy whose integrity can be ensured, but simply deletes all user data and extra apps, while keeping the rest, which could have been compromised via root access. Therefore, there is no guarantee that the factory reset via bootloader really gets the device to the "factory state". Is that correct?
[Many thanks for your explanation.]

wiltingenthusiasm said:
Oh, I see. And a factory reset would not help either, because it does not recover the OS from a reserve copy whose integrity can be ensured, but simply deletes all user data and extra apps, while keeping the rest, which could have been compromised via root access. Therefore, there is no guarantee that the factory reset via bootloader really gets the device to the "factory state". Is that correct?
[Many thanks for your explanation.]
Click to expand...
Click to collapse
In theory, because I have not ready any news, articles, guides or forum threads where people are claiming they have done it.
So, the only option to ensure things are 1% safer, is to unlock the bootloader and flash a custom ROM yourself, trusting that the ROM dev didn't put anything weird in it. Though, as far as I checked, none of the OFFICIAL ROMs for Pixel 2 have a history of putting in something bad.
So, if you want 100% stability, use the default google ROM after a factory reset, but if you want """more""" security, unlock the bootloader and flash the ROM yourself.