Database Users

Nexus 7 4.2.1 update crashed

Hi techies,
Last night i have tried to update the latest update of android 4.2.1 (11mb of size) through update manager.
It hang for some time and crashed.. now no display on my nexus 7.
anybody knows how i can recover/flash it... of reset it... pls help...:crying: :crying:
i have tried 30 sec hold the start button but it doesn't help... any other ideas or anyway to HARD RESET... #HELP

remin13 said:
Hi techies,
Last night i have tried to update the latest update of android 4.2.1 (11mb of size) through update manager.
It hang for some time and crashed.. now no display on my nexus 7.
anybody knows how i can recover/flash it... of reset it... pls help...:crying: :crying:
i have tried 30 sec hold the start button but it doesn't help... any other ideas or anyway to HARD RESET... #HELP
Click to expand...
Click to collapse
This is to reset your nexus to complete stock like the day you bought it, so yes you will loose all data!
First follow the YouTube guide to install android sdk, adb, fastboot on computer.
https://www.youtube.com/watch?v=oaNM...e_gdata_player
Then follow this guide to reset your nexus.
Note the bootloader needs to be unlocked which once adb is set up as in guide below the first comand needs to be
Fastboot oem unlock
The guide doesn't mention this.
http://forums.androidcentral.com/nex...e-restore.html
When you have finished
Fastboot oem lock. Will lock your bootloader again.

nexus 7 crashed
Thanks for your update...
I hav already tried this but it shows my nexus 7 does not detect on my computer.
already tried on my Ubuntu and WinXP, all shows the bellow message...
fastboot oem unlock
< waiting for device >
Is any drivers should i install to solve this???

remin13 said:
Thanks for your update...
I hav already tried this but it shows my nexus 7 does not detect on my computer.
already tried on my Ubuntu and WinXP, all shows the bellow message...
fastboot oem unlock
< waiting for device >
Is any drivers should i install to solve this???
Click to expand...
Click to collapse
Did you follow the YouTube video fully? I had to add some paths to windows too.
You can leave the "fastboot oem unlock" command until just before you flash the operating system back on, if you forget and try to flash the operating system it doesn't matter it will just tell you the bootloader needs to be unlocked, this is the part where a small amount of poo came out of me because I had followed the guide past where you use all the erase commands and then though **** how do I unlock my bootloader now everything is wiped! Turns out the fastboot command still works.
Nexus 7 Tapatalk 2

WasherUK said:
Did you follow the YouTube video fully? I had to add some paths to windows too.
You can leave the "fastboot oem unlock" command until just before you flash the operating system back on, if you forget and try to flash the operating system it doesn't matter it will just tell you the bootloader needs to be unlocked, this is the part where a small amount of poo came out of me because I had followed the guide past where you use all the erase commands and then though **** how do I unlock my bootloader now everything is wiped! Turns out the fastboot command still works.
Nexus 7 Tapatalk 2
Click to expand...
Click to collapse
No way... i think its not detect on my Windows nor on Ubuntu. Better i think, gave it to authorized service centers.

remin13 said:
No way... i think its not detect on my Windows nor on Ubuntu. Better i think, gave it to authorized service centers.
Click to expand...
Click to collapse
Oh dear
Nexus 7 Tapatalk 2

Lenovo Z90-7 (VIBE SHOT) - International (ROW) ROM, multilanguage, GAPPS

Date: 2015.07.01
Bootloader: unlock method unknown
Custom recovery: none
International (ROW) firmware: Z90a40_USR_S118_1505272046_Q2020131.4_ROW_qpst
Update: Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull
Credits to:
http://club.lenovo.com.cn/lefen/bbs/forum.php?mod=viewthread&tid=223254&extra=page%3D1
http://club.lenovo.com.cn/thread-888477-1-1.html
I've tested it - it works. Multilanguage (look at screenshot - not all languages), GAPPS, no chinese bloatware. NO ROOT.
SD card must be removed during flashing!
Flashing procedure:
1. Download:
- Miflash: Miflash_140509.zip
- firmware version S118: Z90a40_USR_S118_1505272046_Q2020131.4_ROW_qpst.7z
- update to version S208: Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull.zip
Link: https://drive.google.com/folderview?id=0B8CarqWdS9gZfmthcGxKQ2R3YUZCMWhjMWRVTFJZTFJ5dEFsVE51R1M1M3R4em5jTHVDeFU&usp=sharing
2. Disable driver signature enforcement:
Windows 8: http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
Windows 7: http://www.sabrent.com/support/knowledgebase.php?article=14
3. Install Miflash program.
4. Flash new ROM:
- unzip downloaded file with the firmware
- turn off the phone
- hit VOL + and plug USB cable (phone will vibrate once)
- in Device Manager (Control Panel) new COM port should appear: Qualcomm HS-USB QDLoader 9008
- run Miflash, you should see appropriate COM port
- browse folder with downloaded firmware
- click 'flash' and wait (about 180s)
- disconnect USB cable, hit POWER key for about 10s (phone will vibrate)
- phone will restart and load new system. It takes some time - and if it hangs, please hit POWER again for 10s, it will reboot again and it should proceed
5. Update to version S208:
- download file Z90a40_USR_S208_1507141216_Q2020131.4_ROW_OTAFull.zip, rename it to 'update.zip'
- copy to phone memory or SD card
- reboot to recovery (turn off the phone, hit vol +- and hit power)
- install update package (it will take some time), reboot (first start will take few minutes)
6. (Optional) Reflash or return to chinese version:
- in ROW version it is impossible to enter download mode with VOL+ and plug USB cable - you can do this only with ADB command
- turn on the phone, let the system start
- plug USB cable, make sure ADB Debugging is ON
- execute ADB command: 'adb reboot edl'
- phone will restart in download mode
- now you can run Miflash

can bootloader unlock?
please check "Developer options"
there has "Enable OEM unlock" option.
this mean . can unlock bootloader?

u flash it with Z90-7?

simplebaech76 said:
please check "Developer options"
there has "Enable OEM unlock" option.
this mean . can unlock bootloader?
Click to expand...
Click to collapse
I've checked it and rebooted into bootloader. 'fastboot oem unlock' says: FAILED (remote: unknown command)
bl4ckluna said:
u flash it with Z90-7?
Click to expand...
Click to collapse
Yes, I did.

mr.mrcn said:
I've checked it and rebooted into bootloader. 'fastboot oem unlock' says: FAILED (remote: unknown command)
Yes, I did.
Click to expand...
Click to collapse
HMM....maybe can do this one root

It will be appreciated

as anyone been able to flash? Can you take pictures of the second home screen where al the useless bloatware is installed?
thanks.

There is no bloatware, as i wrote in the first post. Just few lenovo and google apps. ROM is much different than chinese version - different dialer, messages, settings...

mr.mrcn said:
There is no bloatware, as i wrote in the first post. Just few lenovo and google apps. ROM is much different than chinese version - different dialer, messages, settings...
Click to expand...
Click to collapse
hey.Bro.i need u check if u click system update。u get any ota？

mr.mrcn said:
There is no bloatware, as i wrote in the first post. Just few lenovo and google apps. ROM is much different than chinese version - different dialer, messages, settings...
Click to expand...
Click to collapse
Mi phone came in multilanguage version (I'm from France), so this ROM is for me right? It's the same with no bloatware?

bl4ckluna said:
hey.Bro.i need u check if u click system update。u get any ota？
Click to expand...
Click to collapse
HEY. OTA option is there in the about phone - System update.
No new updates at the moment though.

bl4ckluna said:
hey.Bro.i need u check if u click system update。u get any ota？
Click to expand...
Click to collapse
System Update says 'your system is the latest version".
orate.cl said:
Mi phone came in multilanguage version (I'm from France), so this ROM is for me right? It's the same with no bloatware?
Click to expand...
Click to collapse
No, probably you have chinese version with added languages. Post screenshot with firmware version.
But you can flash this ROM anyway.

Thats it

It's chinese version.

I'm getting and error in miflash when i click "flash":
"the system cannot find the file specified.(0x80070002. Open serial port "\\.\COM10")"
---------- Post added at 11:46 AM ---------- Previous post was at 11:43 AM ----------
weird thing also it does not vibrate when i plug it.
also this (the COM changed because i change of USB port):
PD: your links to disable the driver thingy are wrong, can you fix them pls.

using 32 bit or 64 bit windows? Should work with 32 bit.

sjsu said:
using 32 bit or 64 bit windows? Should work with 32 bit.
Click to expand...
Click to collapse
64bit

That must be the issue. MIflash tool only works with 32 bit windows.

sjsu said:
That must be the issue. MIflash tool only works with 32 bit windows.
Click to expand...
Click to collapse
What about windows vista, my wife's windows is vista 32.

sjsu said:
That must be the issue. MIflash tool only works with 32 bit windows.
Click to expand...
Click to collapse
It works with 64-bit - I flashed it on Win 8.1 64-bit.

[Q] Permanent problem with Unlocking Bootloader Nexus S

Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!

alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:

It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse

alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked

Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too

demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!

alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..

UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.

Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.

Q Mobile X 32
bootloader oem unlock problem
plz help

Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923

Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32

Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?

Here's what the guide says...

Root Lenovo Yoga Tab 3 pro

Hi all,
Is there already a way to root the brand new Lenovo Yoga Tab 3 pro?
I want to buy it, but I can't imagine having an unrooted device...
Envoyé de mon LG-H815 en utilisant Tapatalk

Up?

misteurz said:
Up?
Click to expand...
Click to collapse
i have no idea not having access to such a device, but considering the similar hardware with the YT2 model (well better a little but not by that much) it should work with the exact same method uset for YT2. so yes 99% that it's root-able (maybe even unlock-able, someone on your thread asked me, yet he did not sent nothing no files when asked so i don't know much about the internals of YT3)

Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?

misteurz said:
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
Click to expand...
Click to collapse
there are other ways of knowing whether that or maybe even other new commands work, i would need from someone to send me a dump of his fastboot partition so i can check inside (my bet is that what works on YT2 willdo on YT3 too... and i am pretty sure it will work up to YT100 knowing how Lenovo works )

I don't have the tablet yet, so I can't have the files you need. Who has the yoga tab pro 3?

I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet

Shug69 said:
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Click to expand...
Click to collapse
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab

ionioni said:
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
Click to expand...
Click to collapse
Hallo,
Thank you for your work. I have a little bit afraid of this method .
Too bad that there are so few users here . But the Tab is still so new.
Perhaps an even experiencer user dares. Sorry !!!
At Weekend i will take your method and send you the file.

Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.

Shug69 said:
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Click to expand...
Click to collapse
we tried. it was rejected by the bios right from start and never even got the chance to load (that message means just that).
somehow, someway we must get a fastboot image so we can see what can we use (grab from the tab or from stock rom).
i've seen your stock rom avail yet i don't know if they are legit (they seem). also is a payed one.
one more try:
go in fastboot (droidboot) mode and try and see what these commands will output (to see if at least one is still valid):
fastboot flash /tmp/some_small_file some_small_file (use a real file ofcourse, to see if we can still write to the device)
fastboot oem unzip
fastboot oem fastboot2adb
fastboot oem factory2tmp
(they won't do nothing in this config, yet we'll be able to see if meaybe one is still working, ie it doesnt say 'unknown command')

Flash file gives cannot load,; the others give unknown command.

Shug69 said:
Flash file gives cannot load,; the others give unknown command.
Click to expand...
Click to collapse
try again the fastboot flash (i edited the syntax in the prev post)
however, i think that a droidboot.img will make things a lot more easier
so whoever grabs a stock rom...

So, @Shug69, did you try the edited commands?
Envoyé de mon LG-H815 en utilisant Tapatalk

Been travelling. Can try tomorrow but I agree we need to find a ROM. The site ionioni linked to may be legit but 25 bucks to find out seems a bit steep.
ok. back at pc - sure i'd bricked it there - ran 'fastboot oem unlock' and it unlocked the bootloader. woudnt boot normal though afterwards and it took several reboots after ' fastboot oem lock' to get past the Lenovo logo. Device is wiped of course

My experience has been a little different so far. Just picked up the tablet today.
I toggled Allow OEM unlock and enabled debugging in Developer Options. I installed the Lenovo Suite software (which was really just a driver pack) then ran adb reboot bootloader to reboot. It got me to a Lenovo splash.
fastboot oem unlock didn't work for me. It gave me an error message:
Code:
fastboot oem unlock
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.005s
Running fastboot oem unlock-go worked immediately and the tablet rebooted to the typical Android factory wipe screen. Could be coincidental, but I got an OTA notice after I did the whole first-time Android setup. I denied the update, but copied down the update name: YT3-X50F_S000015_150917_ROW_TO_YT3-X50f_S000016_151002_ROW

Hey everyone, kingroot now works to root the yoga 3 8".

Not on the pro unfortunately.

?
Envoyé de mon LG-H815 en utilisant Tapatalk

Thank you
ElrosMinyatur said:
Hey everyone, kingroot now works to root the yoga 3 8".
Click to expand...
Click to collapse
Great news. I have confirmed that it works using my non-Pro Yoga Tab 3 8". Do I need to keep the Kingroot app installed after I have unroot device? The only issue I have is updating the SU binary in SuperSU. More to come after I debloat my device.
Thank you once again.
Spunky168
"The Original Taepo Dong"

Unlocking the Bootloader for F8132 Xperia X Performace

To root your Sony X Performance phone ( I have the F8132 ) You must do this procedure till maybe in the future there is another method.
Unlock bootloader on Xperia X Performance
1) download the ADB-drivers utility here that you will need to install the drivers which enable flashmode to work on your pc. You will also need the Sony Performance X driver so your computer will connect to it properly here
2) Go here to download Android Studio Software which allows you to pen a cmd line and program the phone in flashmode. To save you lots of time and trouble, again, my instructions are much better and help you navigate to the places you need to be so this goes well. Disregard the Sony instructions because you will most likely ask yourself many questions and will not find answers.You will need to properly install the Android studio software to get it working the way you need. Upon install, check off Android SDK and Android Virtual Device. Click next. It takes a while to install. Open the software after it has been installed. It will tell you " No Android SDK found. Click next. Click next again to install the two prechecked updates which are Android SDK Platform and API25" ANdroid 7.1.1 (Nougat). Then click finished to start the install of those 2 updates. It will download files from the internet. This will take a while. Click inish when its done downloading. At the welcome window of Android Studio click on the "configure" button. Choose SDK Manager. There will be 3 tabs at the upper midline of the window. Choose the "SDK Tools" tab. Check off "Google USB Driver and Google Web Driver. Usually these drivers will not work to get your phone in fastboot mode. This is why I have instructed you to install the Flashtool-
drivers utility. Nonetheless, click on these and click on apply. Click accept the click next to download and install this update. Click finish after it has installed then click ok to close the software.
3) On your device, turn on USB debugging and turn on OEM Unlocking by going to Settings, then about phone. Go all the way down to build version and tap on it about 7 times. This will unlock Developer Options menu. To go into Developer Options once it is unlocked goto Settings, then Developer options . This menu is where you must turn on usb debugging and OEM Unlocking to proceed with the procedure.
4) After you have turned on usb debugging, turn your phone off. After its turned off, hold the volume down button while plugging the phone into your pc. Your computer should install drivers that will enable Flashmode.
5)Go here to have Sony give you the unlock code. Input your email address to get the code emailed to you with instructions. It takes just a minute to get the unlock code. DO NOT attempt
to unlock your bootloader with some other method. Odds are its a scam or virus or both and you will be screwed. Follow the steps to get the unlock code by putting in your IMEI
then you are suggested to follow my steps to unlock the bootloader. Keep the Sony page open for reference because once it is closed, you will have to redo the email process and
IMEI process again to get the same code. Youre unlock code never changes.
6) goto the file location C:\Users\PC-User\AppData\Local\Android\sdk\platform-tools where you will open a cmd prompt you must open a cmd prompt in only this folder to make this work. to do so , once in that specific folder
hold down your right mouse button and clock on the shift key then release the mouse button. This will open a pop up window where you can choose to " open command window here"
7) when the cmd window opens, copy and paste this "fastboot devices" directly AFTER the ">" symbol and paste it in the command line with no spaces. It should look lik this.
.........C:\Users\PC-User\AppData\Local\Android\sdk\platform-tools>fastboot devices.........
8)press enter button, your computer should respond in the cmd line with something that looks like this
......CB512A697c fastboot.......
This lets you know that your phone is in the correct mode and ready to be programmed.
9) to unlock your bootloader you then copy and paste directly the cmd code Sony gives you from there website "fastboot -i 0x0fce oem unlock 0XXXXXXXXXXXX" . It will look like this C:\Users\PC-User\AppData\Local\Android\sdk\platform-tools>fastboot -i 0x0fce oem unlock 0xxxxxxxx... The 0xxxx's are YOUR SPECIFIC Unlock code given to you by Sony. DO NOT get this from another other website or software otherwise you will probably be infected with some kind of virus of worse on your phone or computer.
10) press enter to intiate bootloader unlock procedure
11) once bootloader unlock is successful you will see the cmd line spell out this "OKAY [ 1.165s] finished. time: 1.168s" The seconds mean nothing. You do want it to say OKAY!
12) reboot the phone and you will see an annoying warning that cant be undone, which says " your device has been unlocked and cant be trusted" No big deal but very annoying. The phone will work but you will see this everytime you reboot the phone.
13) It takes a while, several minutes, maybe 5, to have the phone bootup. When it does, you will see everything is in a weird language. You need to choose which language you want. to know which menu you must choose, just click on the very first down pointing arrow in the middle of the screen. A menu pops up and you can then choose the language you want. After choosing a language clock ok. Youre done!
Instructions to install TWRP so you can backup and restore your phone here

Thanks for the help, however I get this in the command screen
FAILED (remote: Command not allowed)
I do not get this phone from carrier, and have unlock bootloader allowed = yes , why would this happen to me
edit: everything is fixed now, only problem left is I'm stucked at MM

KWOKSFUNG said:
Thanks for the help, however I get this in the command screen
FAILED (remote: Command not allowed)
I do not get this phone from carrier, and have unlock bootloader allowed = yes , why would this happen to me
edit: everything is fixed now, only problem left is I'm stucked at MM
Click to expand...
Click to collapse
Maybe try Flashtool

ontwerp said:
Maybe try Flashtool
Click to expand...
Click to collapse
I've fixed this problem now
however just flashing the ftf normally wont help
u have to flash the ftf with exclude system.sin
then flash system with system.img
whoever want the system.img can just ask me

KWOKSFUNG said:
I've fixed this problem now
however just flashing the ftf normally wont help
u have to flash the ftf with exclude system.sin
then flash system with system.img
whoever want the system.img can just ask me
Click to expand...
Click to collapse
Can I have your FB/line? Thankss

I don't have X performance yet but I wanna ask a quick question: Will it lose its DRM key and lose camera quality after unlocking bootloader like the older models?

loveyoulovemetn said:
Can I have your FB/line? Thankss
Click to expand...
Click to collapse
PM
dont worry about flashing nougat though, flashing ftf normally will work now on updated flashtool

evildog1 said:
I don't have X performance yet but I wanna ask a quick question: Will it lose its DRM key and lose camera quality after unlocking bootloader like the older models?
Click to expand...
Click to collapse
bump this question as I think the answer is "Yes, it will lose"

huangjs said:
bump this question as I think the answer is "Yes, it will lose"
Click to expand...
Click to collapse
Damn then i'll wait until someone found root exploit.

evildog1 said:
Damn then i'll wait until someone found root exploit.
Click to expand...
Click to collapse
I saw on gfan DRM key can be "regenerated".
However, it's not the one you had before unlocking.
But who cares as long as it will let Sony engine works.

Unlocked bootloader allowed NO!
Is there a Root trick for the Device Lock Bootloader?
I use SOFTBANK series (DOCOMO).