Database Develop

[q] help restoring to stock

Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.

nigerson said:
Ok so I rooted my galaxy note3(about a month ago), but today when I turned it on the phone instantly installs a new update without my permission and takes away my root. This would be fine, but now my phone says "custom" when booting up and it is not rooted anymore. How would I be able to take away the "custom" boot image? I am seriously considering selling att GN3 at this point(tired with ATT bs and lack of any info on updates) and opting for a nexus 5. My only problem is that people will be turned off by my previous evidence of rooting my device because it says "custom". I essentially would like to return my phone to all stock settings.
Click to expand...
Click to collapse
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.

powdered_donuts said:
Try simply rebooting. That worked for me after unrooting via odin one click on mi9. The first boot showed custom wich confused me but after just a reboot it went away. I think it softbooted after odin and didnt run through the whole process.
If not then the only option currently to remove custom is to re root using kingo then use xposed to fake custom system status. The latter would be shady however if you plan to sell the device.
Click to expand...
Click to collapse
Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)

http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)[/QUOTE]
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx

powdered_donuts said:
http://forum.xda-developers.com/showthread.php?t=1574401QUOTE=nigerson;47504941]Sorry to bother you, but I am not too familiar with how to do this. Would you be able to show me some sort of step-by-step guide which I would be able to use? Also how do I check if I'm on mi9 and not something else(because I currently have the most updated firmware on my phone)
Click to expand...
Click to collapse
The most updated is mj5 if you took the ota update that hit recently. You can check by going to settings then about phone then look at the last 3 digits of the baseband.
To install xposed go to the link at the top it pasted there on my tablet for some reason. Instructions are there for installation.
download the xposed installer apk. You must be rooted. Use kingoapp for that if necessary. Open xposed installer and go to framework. Install the most recent framework. Then go to download. Download cosmetic device status normal modification. Use that to remove the custom padlock. Reboot. Hit thanx [/QUOTE]
So, I am on mj5 right now since I got the OTA update and I am no longer rooted because of this. How can I flash to stock or reroot and install xposed? Or am I ****ed?
*EDIT USED KINGO INSTALLED FRAMEWORK ALL IS GOOD IN THE HOOD *

[Q] Rooting disables NFC?

I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.

goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.

goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip

I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.

I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.

goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.

simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.

goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.

simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).

jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.

simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?

jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.

simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.

jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.

simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)

Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.

I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.

lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.

I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).

Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.

[Q] Need Help with cusotm recovery and root

I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?

cnoevl21 said:
I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?
Click to expand...
Click to collapse
no that does not matter because you are able to unlock your bootloader so android version dose not matter.
when installing your recovery you are running the CMD commands with your phone in bootloader mode correct.
if you are in bootloader mode and still having issues here are a couple things you can try.
1. Restart the phone
2. try a different USB port
3. restart ADB
4. Check drivers
you already know this but once you flash your recovery make sure you boot into the recovery before booting back into android.
if you get it installed Root is simple just download the SuperSU flashable zip and flash it via your custom recovery.
lmk if you are still having issues and we will look into other issues

thanks!
I ended up deleting everything (adb, sdk, fastboot, etc) and redownloading everything. So that got me able to install twrp, but when i tried to boot into recovery it would turn off the phone. Then I realized that in download mode you scroll down to recovery, then hit vol up to select. I am coming from galaxy nexus where the power button is select. So was i figured this out, i got into twrp and installed superuser, so i am rooted now. Time to find a 4.4.4 rom (may have to wait for a stable one since its pretty new) so i can get rid of all this bloatware. I can freeze some of it in titanium, but a lot of it I'm not sure what it does, again, Ive been on samsung for the past 5 years lol. Thanks again for the help.

4.4.4 isn't new. If you want all the Motorola features, stick with a stock-based rom or stock. I prefer stock with Xposed.

Being on vzw, I would recommend Krypton. It's based off the Verizon image and has a lot of bloatware removed. Xposed will get you about all the customizations you might want past that.

i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.

cnoevl21 said:
i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.
Click to expand...
Click to collapse
Right now Android L or 5.0 Roms are New and buggy. Most 4.4.2 and 4.4.4 roms are stable.
Me personally i like Stock with Xposed and gravity box installed, then i use Titanium Backup there is a battery thread somewhere that list what can and can't be removed. just be careful what you remove or you will end up like me with no active display but everything else about my phone is perfect so i dont want to go back to stock and redo everything.
after xposed and TBU i normally find a launcher i like, then maybe a lock screen but i think i ended up with stock. then i find a Text MSG app i like and other little add-ons to make my phone just for me.
here us a list of what i am running on my Stock Sprint 4.4.4\
LockScreen - Stock but tweaked with GravityBox
Launcher - Google Now Launcher
Text App - Google's Messenger App
Gesture Shortcut Menu - Lazy Swipe( i just found this app about a week ago and so far i love it, it allows me to have a very clean homescreen)
everything else changed on my phone is done threw Xposed and gravity Box.
Here are some App's you might want to check out.
AirDroid
Google Calender(if you use a calendar)
Google Keyboard(my keyboard of choice)
GSam Battery Monitor
Lazy Swipe(listed above)
Lucky Patcher(for thous pesky trial apps)
Pushbullet( alternative app for transferring all kinds of files to and from your device)
Zedge(ringtones and wallpapers)
I also attached some screenshots nothing fancy like i said but i love it and its perfect for me
The first one is my lockscreen, second one is my launcher homescreen, Third one is Lazy Swipe just one of the three tabs.
anyways hope this helps get you started post your setup once you get everything set up to your liking
Good Luck

what is that clock/weather widget? Thats pretty sick

http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506

nhizzat said:
http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506
Click to expand...
Click to collapse
yup that is correct enjoy

error while flashing recovry in cmd ....
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!

commuditi said:
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!
Click to expand...
Click to collapse
well first thing when u are posting for help you need to include more info. Like for starters what error are you getting so we can figure out what you are doing wrong. post your error and we will go from there.
Thanks

I do not want to take OTA system updates...

I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?

LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.

LaTropa64 said:
I've unlocked the bootloader and rooted the phone with the help of the Nexus Root Toolkit by WugFresh.
I now have it setup just how I want it and I don't want an OTA to kill root or change anything so something stops working (phone isn't for me, but I've set it up just right for someone with special needs).
I've read conflicting information on whether or not an OTA will actually install on a rooted phone or not. Some things say that it won't if you've changed anything at all while others say it might be possible.
Is there some system file I can rename or something to ensure the phone doesn't get a system update unless I do it manually?
Click to expand...
Click to collapse
Root solved your problem ha ha

simms22 said:
no matter how many times you will try to update via ota, you will not be able to. if any files change from stock, any at all, you wont be able to install an ota. especially with root.
Click to expand...
Click to collapse
And sometimes, even if one is 100% stock, those pesky OTAs won't install.

cam30era said:
And sometimes, even if one is 100% stock, those pesky OTAs won't install.
Click to expand...
Click to collapse
right. any system file changes prevent install.

Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?

Install a custom recovery. Done. OTAs require the stock recovery in order to flash files.

LaTropa64 said:
Awesome. Thanks.
Will it even attempt to install an update, and if so, does it only attempt once and then give up so you don't get stuck in a loop?
Click to expand...
Click to collapse
itll only attemp if you let it(it needs your approval to update), otherwise itll only tell you that an update is available. if you let it, itll try, but fail. if you boot up, youll be where you were before.

Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?

LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
you can always look at your android version in aboy phone, to see if it updated or not.

LaTropa64 said:
Apparently I rooted it incorrectly because it was able to update. I just got a call and the phone had rebooted and went through optimizing X of X apps and now many of the tasker profiles I had set are no longer working.
It wouldn't have optimized a bunch of apps if it hadn't updated the OS, or no?
Click to expand...
Click to collapse
You'll find update or not optimizing apps happens a lot especially if you clear cache etc...
Your fine otas can't install with root
Just flash twrp it will cone in handy incase you brick it one day you'll have twrp to fastboot fix or sideload a rom to recover from.
ONE NOTE: Never ever ever relock your bootloader with the toolkit you'll be screwed. Always leave bootlaoder unlocked. I just had to rma manufacturer phone replacement I relock mine with toolkit and couldn't flash stock firmware or oem unlock again.
Sent from my LGMS769 using XDA Free mobile app

simms22 said:
you can always look at your android version in aboy phone, to see if it updated or not.
Click to expand...
Click to collapse
I'll take a look the next time I get over there. It's not my phone, I just set it up for someone with accessibility issues and wanted it to stay the same as the day I set it up but apparently it's not done that.

I've just gotten the phone and am confused as hell

(stock firmware)
1) How do I enter recovery mode? I need to install Xposed and I can't figure out how to boot into this.
2) Why is the advanced reboot disabled? I went through all of the developer options and it's just not there :-O

Root?
You did root your phone?

WalrusInAnus said:
(stock firmware)
1) How do I enter recovery mode? I need to install Xposed and I can't figure out how to boot into this.
2) Why is the advanced reboot disabled? I went through all of the developer options and it's just not there :-O
Click to expand...
Click to collapse
The XZ's are nothing like any Sony phone before. Sony have given developers the finger with this boot partition, You can't just Root you phone any more. Unlocking your phone destroys a partiton and the DRM keys are gone forever. The good news is that there's a fix that fools the phone into thinking the keys are still present.
Yes it's possible to load recovery and exposed. You need to unlock the phone first, then (retro)flash .75 firmware, as that is the only one that works with Xposed. Then I would use Xperiafix to mount TWRP and Magisk and the drm fix. Once Magisk is installed you can use the Xposed Magisk module.
It's a long complicated road compared to the old phones and having done it, I'd say the advantages are not worh the effort.

Oh ****, what the hell It's the only higher end compact phone out there, so there's no alternative for me.
I already unlocked the bootloader and now my camera is ****ed, and apparently it's impossible to relock it.
Unfortunately I don't understand anything you wrote in your post. I've dealt with Samsung phones until now and that's piss easy.
What does "mount twrp" mean? What is Magisk?
I managed to install TWRP but it asks for a password, so I think something went tits up there.

WalrusInAnus said:
I think something went tits up there.
Click to expand...
Click to collapse
Read the Xperiafix thread, this will help you find the drivers you need to connect to the phone via ADB. (Hint: Google ADB drivers). Geting the drivers to work with your phone is fiddly because a) Windows10 lies to you when it says it's installed the drivers and b) Windows then chooses the wrong drivers when you plug your phone (running twrp) in.
Buy Xperiafix. Yes there are free versions to be found but getting everything to work is fiddly as f*ck and I'm going to guess you want the easy option.
Install the drivers, follow instuctions on Xperiafix, easy.
Your TWRP is asking for the pin number you set to unlock your phone.