Develop Bugs

insurance and rooted device

My nexus 7 is unlocked and rooted etc. I have insurance on it in case of screen damage. If I did drop it and it was damaged would insurance still cover it even though its rooted? I wouldn't see why not but thought I would check.

razormccabe said:
My nexus 7 is unlocked and rooted etc. I have insurance on it in case of screen damage. If I did drop it and it was damaged would insurance still cover it even though its rooted? I wouldn't see why not but thought I would check.
Click to expand...
Click to collapse
Normally the disclaimer said "Warranty is void if you unlock your device", but it's only in case of the problem is caused by the fact of unlocking/rooting the device. In fact they just cover their back ^^.
Your OS cannot break physically your screen (Fortunately ^^). Some people got their devices replaced on custom ROMed devices by Asus. If you want to RMA your device, if your device still running a bit, and to be sure, factory reset and relock your bootloader before sending it.
Sincerely

Cheers, can I unroot and relock all via windows? As in, if the device couldn't be used at all?

razormccabe said:
Cheers, can I unroot and relock all via windows? As in, if the device couldn't be used at all?
Click to expand...
Click to collapse
Yes, you can unroot and relock bootloader all via Windows. You just restore with factory image, and type in fastboot
Code:
fastboot oem lock
If the device is unusable, i mean nothing showing on the screen, i think Asus will not search for unlocking.
A long time ago, i was playing with my San Diego, and bricked it (When i tried to play with the locked bootloader and flash some suckastuff from me) and they accepted it on RMA, fortunately ^^

[Q] Unlocked bootloader, need to send back to HTC

Hi, I just have a simple question. I unlocked my boot loader using the HTC dev tool the day I got the phone. My micro usb port is broken, and my phone is under warranty, however after talking to HTC they say my phone’s boot loader is unlocked. It shows in their system. Is there any way to change that? Relocking my boot loader probably won’t help will it? They say I will not be able to get my micro usb port changed for free even though it is under warranty ($200-$320 cost). If anyone has any suggestions, thanks a lot!

Unroot for sending to service

Hello,
My question to you is, if i'm repairing my phone with sony pc companion , will root capabilities dissapear?
Because i whant to send my phone to service and i'm worried that if i have root the warranty will be denied.
Or can you help me with another option to unroot and make the phone be at factory settings.
Thank you very much.

free2rhime said:
Hello,
My question to you is, if i'm repairing my phone with sony pc companion , will root capabilities dissapear?
Because i whant to send my phone to service and i'm worried that if i have root the warranty will be denied.
Or can you help me with another option to unroot and make the phone be at factory settings.
Thank you very much.
Click to expand...
Click to collapse
are your phone still can boot up? i mean not in brick condition?
if your phone still can boot up, you can flash your phone with stock ftf firmware file with flashtool software and do full wipe data before install. and you can service it safely and no worrie with root warranty

The phone is fully functional, the only problem is my micro usb charging slot wich is not working proprely, and that's why i need to send it to service.
I'm kind of reserved to flash anithing because i'm worried not to break something.
But by doing a repair phone from sony pc companion is not the same thing with flashing the stock ftf with flashtool?

free2rhime said:
The phone is fully functional, the only problem is my micro usb charging slot wich is not working proprely, and that's why i need to send it to service.
I'm kind of reserved to flash anithing because i'm worried not to break something.
But by doing a repair phone from sony pc companion is not the same thing with flashing the stock ftf with flashtool?
Click to expand...
Click to collapse
it's the same, I belive that as long as you haven't unlocked your bootloader it'll be fine but how do you want to flash it when your usb is broken?

I have a locked bootloader so i think i'm good.
It's not quite broken.
It's not charging fast enough , and sometimes it stops charging.
I'm hoping that it's not gonna affect the repair process.
What do you think?

free2rhime said:
I have a locked bootloader so i think i'm good.
It's not quite broken.
It's not charging fast enough , and sometimes it stops charging.
I'm hoping that it's not gonna affect the repair process.
What do you think?
Click to expand...
Click to collapse
I have the same issue, it's not usb fault, there is something wrong with motherboard. It's preatty common problem but I saw case where repair shop told guy to buy new battery and charger, he did it and it didn't helped, then he send it again to repair and they changed his motherboard
well I send my one to service and if they won't fix it i'll put it into trash. This phone makes me angry, hopefully I bought new moto e.

Bootloader does not stay unlocked over reboot

I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?

neree said:
I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
Click to expand...
Click to collapse
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?

sfhub said:
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
Click to expand...
Click to collapse
For the TWRP errors I'll have to get back on when I get back home to my device. For the other part, yes I did enable the unlocking under dev options, and used fastboot flashing unlock (also tried fastboot oem unlock). They both do go through and wipe my device. The bootloader also stats that current state is unlocked after the wipe. However after restaring the device back to bootloader causes the state change back to locked.

Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.

sfhub said:
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
Click to expand...
Click to collapse
LG (or whatever company it is that does it for them here) installed the new board. I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader. Was just wondering if I completely missed something that might cause the device to do this so I could either use it again by myself or sell it as fully functioning Nexus device.

neree said:
I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader.
Click to expand...
Click to collapse
That's a good call. Actually I wouldn't mess around too much with the phone if you are going to sell it.
Just make sure you remove any pin/pattern/password from the phone and to be extra safe, remove your google account from the phone *PRIOR* to factory reset or you will run into Factory Reset Protection (FRP) where you will have to give the buyer your google account and password so they can do first install and switch to their own account.

XA2 sdcard reader issue

I have an XA2 that does not like sdcards. I have tried 3 different ones and get the command volume partition error. All 3 cards check out fine on pc and work in my other phones. Did the formatting on pc and all other supposed "fixes" that I could find out there. One trick that made a difference was placing tape on the tray to push the card closer to the pins. That made it to where the phone didn't see the card at all. One piece of scotch tape. So I'm guessing from this that there is a problem with the pins? I've looked at youtube video of the disassembly of this phone and doesn't look any harder or easier than others. So.... any thoughts? I thought at first it was software, but did a software repair and that didn't change anything. Anybody else have this issue and what did you do if anything? Be nice to have more than 32g of storage. I can use otg storage but that's cumbersome as opposed to having it internal.

bobsright said:
I have an XA2 that does not like sdcards. I have tried 3 different ones and get the command volume partition error. All 3 cards check out fine on pc and work in my other phones. Did the formatting on pc and all other supposed "fixes" that I could find out there. One trick that made a difference was placing tape on the tray to push the card closer to the pins. That made it to where the phone didn't see the card at all. One piece of scotch tape. So I'm guessing from this that there is a problem with the pins? I've looked at youtube video of the disassembly of this phone and doesn't look any harder or easier than others. So.... any thoughts? I thought at first it was software, but did a software repair and that didn't change anything. Anybody else have this issue and what did you do if anything? Be nice to have more than 32g of storage. I can use otg storage but that's cumbersome as opposed to having it internal.
Click to expand...
Click to collapse
Hi
If you have already tried to format the SD, and it seems like as if there is a problem with the pins, so don't disassemble the phone and use your warranty to give the phone back to Sony. If you will try to disassemble the phone, you will 99% lose your warranty.

faby GT said:
Hi
If you have already tried to format the SD, and it seems like as if there is a problem with the pins, so don't disassemble the phone and use your warranty to give the phone back to Sony. If you will try to disassemble the phone, you will 99% lose your warranty.
Click to expand...
Click to collapse
Thanks, but I bought the phone used and I doubt it's still under warranty. Bootloader is unlocked and rooted too.

bobsright said:
Thanks, but I bought the phone used and I doubt it's still under warranty. Bootloader is unlocked and rooted too.
Click to expand...
Click to collapse
How did you repair software with unlocked bootloader?
If I were you, I would try to COMPLETELY put the phone back to stock (locked + unroot) and hope that Sony won't give you problems...
If you start disassembling the phone there may be many problems because you aren't an expert, so I would take the risk to pay (in Italy there is a 15€ ticket in case you are out of warranty for some reasons but you have already sent the phone to the repair service)

Repaired it with EMMA. Bootloader cannot be re-locked.

bobsright said:
Repaired it with EMMA. Bootloader cannot be re-locked.
Click to expand...
Click to collapse
Yeah you can. Firstly install ADB and fastboot drivers. Then connect the phone and type:
adb reboot bootloader
On reboot completed execute:
fastboot oem lock
Or, if it doesn't work:
fastboot flashing lock
Or, if it doesn't work:
fastboot oem relock
Then:
fastboot reboot
Then repair software with Sony PC companion
Done:highfive:

From the Sony site:
If I change my mind later on, is there any way to restore my device?
No. Once you have unlocked the boot loader, you will not be able to revert the device back to a locked or original state or restore the DRM security keys. You can however use the Flash tool for Xperia™ devices to flash a generic Sony ROM, although it will not receive automatic software upgrades.
https://developer.sonymobile.com/unlockbootloader/

bobsright said:
From the Sony site:
If I change my mind later on, is there any way to restore my device?
No. Once you have unlocked the boot loader, you will not be able to revert the device back to a locked or original state or restore the DRM security keys. You can however use the Flash tool for Xperia™ devices to flash a generic Sony ROM, although it will not receive automatic software upgrades.
https://developer.sonymobile.com/unlockbootloader/
Click to expand...
Click to collapse
I know what there is written, and yes, you can't restore DRM but I have relocked bootloader twice on my previous device.

Right, that's what the quote I posted said.
Mute point anyways. Not returning to Sony. Just looking for others who may have had this issue and if indeed it is the reader or a firmware issue and what, including tearing phone apart, did people do to resolve it.