Database Users

Moto Z Play | Resources all in one thread

Hey guys
I just thought we should have a 1-stop-guide for our amazing Moto Z Play. Generally people have to look through various threads before obtaining the real info, this thread was created so that people would find the resources easily without wasting time, looking here and there for information.. I will try to update the thread on regular basis as and when the new developments arrive...
Note: I want to thank all the devs for their efforts. None of this is my creation , i just collected & compiled all the info from various sources, credit as usual goes to original devs
PS: The thread is complete now...Just have to add the images for easy understanding...All the info posted here is latest development with correct info...There is no chance you will brick your phone by following this guide unless you do something wrong...
************************************************** ************************************************** ***************
INDEX​************************************************** ************************************************** ***************
Drivers | ADB installer
Unlocking Bootloader (Official Method)
Flashing TWRP and Rooting via TWRP
Back up / Restoring EFS (IMEI)
Restoring original Boot Logo after unlocking bootloader
Installing Xposed Framework
Flashing/ Restoring back to Stock Rom
Changing DPI without root
Remove Ascending Ringtones/Notifications
************************************************** ************************************************** **************
1) Drivers | ADB installer
​1) Motorola Drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installer (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
_______________________________________
​
2) Unlocking Bootloader (Official Method)
​
Files needed:
1) Motorola Drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
Note: Unlocking the bootloader erases all the data on the phone, make a backup of your imp stuff before unlocking
Method:
1) First of all visit this official Moto Unlocking site & register yourself or login via Google
https://motorola-global-portal.custh...-a/action/auth
2) Enable USB debugging & OEM unlock on the phone (Go to settings -> development options (if they do not have it enabled go to settings-> about the phone and below where it says "Compilation number" tap 7 times to activate the development options).. In the developer options, select "OEM unlock" it will ask for password / PIN / pattern and once activated, we look for "Debugging via USB" and we activate it also, then proceed to turn off the phone)
3) Turn on the phone by pressing Vol down + Power button together for 5 seconds until we get a screen like this:
4) Open adb command window and type:
Code:
fastboot devices
If your device appears on the command window you can continue with the guide, if your phone is not listed, install the Moto drivers correctly and verify if adb is working or not...
5) In the same adb command window type:
Code:
fastboot oem get_unlock_data
You will see numbers displayed like this, copy the code and paste it into notepad..Now eliminate the paragraph break so that there is only one line without spaces… Copy the entire code & login into your Moto account…Now paste the code on the same Moto webpage which was given above…
The unlock code will be sent to your registered email. There will appear an email with the number similar to this:
5)Without disconnecting the phone from the PC & without closing the window of the CMD, we return & we put this code:
Code:
fastboot oem unlock (enter code that was provided in the email)
6) You will be asked to re-enter the same command again, re-enter the code to confirm and finally unblock the bootloader
7) After re-entering the command, you will bootloader unlocked message
_______________________________________
3) Flashing TWRP and Rooting via TWRP
​
Note: Custom recovery (TWRP) woks only after unlocking your bootloader… Before flashing this recovery unlock your bootloader and enable USB debugging…
​
Files required:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) TWRP for Moto Z Play (https://mega.nz/#!yZ4lUCYB!-nN0jj2Ws5Z7RNyBT7S8m4gsrdOxTlK3nTjn9zOtx6s)
Method:
1) Download the above recovery, boot the phone in fastboot mode & open adb command window
2) In the adb command window type
Code:
fastboot flash recovery recovery.img
3) After executing the command, disconnect your phone & with the volume + or volume keys - we move until it says "Recovery Mode" . Press the power button to confirm the entry to the recovery.
4) Once you enter the recovery, select the right button & a menu to choose the language is displayed, it only brings Chinese and English so we will put it in English to know what to do.
5) We will see that it asks for a password, it is the same password that you put to encrypt the phone at the beginning when they set up the factory phone and always asks them to turn on the phone, it can be a password / PIN / pattern
6) Once the password has been entered, the recovery main menu will appear, we will go to "Advanced" and then "Install SU", it will ask if we want to root the phone, we accept by sliding and we wait for it to do the process. Then we give in "Reboot System" to restart and the phone will ignite with root
_______________________________________
4) Backing up / Restoring EFS (IMEI)
Note: This works only if you have TWRP recovery... Please backup your EFS using the method below before flashing any rom including stock rom
​
Backing up EFS (IMEI):
Method:
1) Boot the phone into TWRP recovery
2) Go to "Backup"
3) Select EFS
4) Create backup by sliding
5) Once finished, restart the phone
6) After restarting the phone, copy the TWRP folder from the internal memory to the SD, DO NOT CUT and PASTE, just copy with a file browser. Later from the SD card can be copied to the PC
Restoring lost IMEI / EFS:
Method:
1) Boot the phone into TWRP recovery
2) Go to "Restore"
3) Select folder (location where you have kept a backup of your EFS)
4) Restore by sliding
5) Wipe cache and dalvik and start phone normally
_______________________________________
5) Restoring original Boot Logo after unlocking bootloader
​
PS: This is used to remove unlocked bootloader warning when the phone is turned on (the black screen with letters)
Credit goes to : G4liant
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) Original Motorola Bootlogo (https://mega.nz/#!zNIFHBiY!hbdgUwl9oWjrXbirwXKijviWW0nS_06MViU48yHmSD4)
Method:
1) Boot the phone in fastboot mode, open adb window on pc and type
Code:
fastboot flash logo logo.bin
2) Once the flashing is finished, restart the phone with this command:
Code:
fastboot reboot
When you turn it on, we will notice that we have the original motorola boot logo again and that the previous warning does not appear even when the bootloader of our device is unlocked
_______________________________________​
6) Installing Xposed Framework
​
Files needed:
1) [FONT=&quot]Have TWRP installed (If not installed refer to section #3 on this thread)
2) Download latest Xposed Installer.zip (http://dl-xda.xposed.info/framework/sdk23/arm/ )
3) Download latest Xposed Apk (https://forum.xda-developers.com/showthread.php?t=3034811)
Optional: Download latest Xposed un-installer but ARM 32 version not ARM 64 (http://dl-xda.xposed.info/framework/uninstaller/ )[/FONT]
Method:
1) Copy Xposed installation .zip, Xposed uninstaller (optional) and the Xposed APK to the internal memory (the TWRP does not mount the external SD so do not bother copying it to the External Memory)
2) Install the Xposed APK but DO NOT open it.
3) Enter recovery mode and open TWRP, Choose language and enter password to decrypt your device
4) Once the password is entered, the main recovery menu will appear, select "Install" and a file manager will appear, we will navigate the file down and look for the Xposed installer .zip, something like this:
5) Select the Xposed installer .zip and it will open a zip installer, slide to accept the flash of the .zip and wait for the process to finish. Then we give in "Wipe Dalvik / cache" and then to "Reboot System" to reboot and the phone will light up with Xposed already working.
_______________________________________
​
7) Flashing/ Restoring back to Stock Rom
​
IMPORTANT: First locate the firmware for your country / operator / area / continent to avoid changing baseband or other things that make the phone does not work as it should.
Credit goes to: Khanov XDA
Stock Rom links:
[FONT=&quot]Stock China
http://www.filefactory.com/file/6814...LT_CFC.xml.zip
Rogers Canada
http://www.filefactory.com/file/57g6...LT_CFC.xml.zip
Retail Latino America
http://www.filefactory.com/file/6pt8...%20%281%29.zip
Retail Latin America
https://mega.nz/#!WBYX3awb!qR1zitz1O...M1tnq1OwWDYDYA
Retail Europe
http://www.filefactory.com/file/4ora...C_EMEA.xml.zip
Retail Canada
http://www.filefactory.com/file/64wm...LT_CFC.xml.zip
Movistar Colombia
http://www.filefactory.com/file/10sv...LT_CFC.xml.zip.
Verizon
http://www.filefactory.com/file/60ty...LT_CFC.xml.zip
A Repository with several firmwares including Indian:
https://mirrors.lolinet.com/firmware...ison/official/[/FONT]
[FONT=&quot]
Files needed: [/FONT]
[FONT=&quot]1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) Firmware chosen from above links[/FONT]
[FONT=&quot]
[/FONT]
Method 1 (Manually by using adb commands):
1) Boot the phone into fastboot mode and open adb command window on pc
Code:
fastboot devices
This will show us if the phone is correctly connected and installed the drivers, it will detect the PC in fastboot mode and we can continue with the tutorial we will put these commands in the order they are, you can put them one at a time and pressing enter to execute it
Code:
[SIZE=2][B][FONT=Century Gothic]fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash NON-HLOS.bin modem [COLOR=Red]([/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot erase modemst1 [I] [COLOR=Red](can skip this and thus [U]would[/U] prevent loss of IMEI)[/COLOR][/I]
fastboot erase modemst2 [COLOR=Red][I]([/I][/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot flash fsg fsg.mbn [COLOR=Red][I](can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot erase cache
fastboot erase userdata [COLOR=Red]([/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of your data (Internal storage)[/I][/COLOR]
[/FONT][/B][/SIZE][SIZE=2][B][FONT=Century Gothic] fastboot oem fb_mode_clear
fastboot reboot
[/FONT][/B][/SIZE]
Your phone will reboot and will be restored to stock rom
In case an error occurs during OTA, even after doing the above step flash the modem by typing:
NOTE: You will find these files (NON-HLOS.bin, fsg.mbn, adspso.bin etc) along with the systemchunk files you downloaded
Code:
[/FONT][/B][/SIZE][/SIZE][SIZE=2][SIZE=2][B][FONT=Century Gothic]fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
Now reboot the phone and apply OTA... It will succeed
Method 2 (Using software ; RSD lite to flash) :
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) RSD lite (http://rsdlite.com/rsd-lite-download/)
4) Stock Rom from the links provided above
Method:
1) Enable USB debugging
2) Download RSDlite and Stock Rom zip file
3) Open RSDlite and browse button (next to file name textbox)... Find and select "flashfile.xml" from the downloaded zip file (extract the zip file)
4) Boot the phone into fastboot mode and connect the phone to pc; RSD lite shows ID if connected
5) Click start button…Now flashing process has started…It will flash files one by one…Wait for it till it shows reboot…
[FONT=&quot]6) Handset will automatically restart after flashing process completes[/FONT]
_______________________________________
8) Changing DPI without root
​
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
Method:
Note: The DPI used here is 420... You can adjust the DPI according to your own taste... The default DPI is 480
1) Open ADB command window and enter:
Code:
[FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm density 420[/B][/B][/B][/FONT][/B][/B][/B][/FONT]
2) Reboot your phone to apply the effects system wide
Reverting back to stock DPI:
Method:
1) Open ADB command window and enter:
Code:
[FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm density 480"[/B][/B][/B][/FONT] or "[/B][/B][/B][/FONT][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm size reset" (If the 1st one doesnt work or some apps show wrong layouts like Snapchat etc[/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT]
2) Reboot your phone to apply the effects system wide
_______________________________________
9) Remove Ascending Ringtones/Notifications
Files needed:
1) TWRP
2) Ringtones / Notifications mod (http://cloud.tapatalk.com/s/58221f724bc3b/Ascending_audio_fix_motozplay.zip)
Method:
1) Download the mod and copy it to internal storage. Boot the phone in TWRP
2) Select install and locate the file in the file manager... Select the file and flash it
Reverting back to stock (Ascending ringtones):
Method:
1) Download this file [FONT=&quot]https://www.dropbox.com/s/otsir98jjlqnb85/Ascending_audio_stock_motozplay.zip?dl=0https://www.dropbox.com/s/otsir98jjlqnb85/Ascending_audio_stock_motozplay.zip?dl=0
2) Copy it to internal storage & boot the phone in TWRP... Select install and locate the file
3) Select the file and flash it[/FONT]
​

reserved...

reserved

Nicely work

Really nice thread. Just one thing...
Could you credit me for the modified logo.bin?
https://forum.xda-developers.com/showpost.php?p=69273602&postcount=37

Can I flash logo.bin zip in twrp?

Nope, has to be unzipped and flashed in fastboot, which shouldn't make much of a difference, as it has only to be done once. No need for reflashing after switching your custom rom.

G4liant said:
Really nice thread. Just one thing...
Could you credit me for the modified logo.bin?
https://forum.xda-developers.com/showpost.php?p=69273602&postcount=37
Click to expand...
Click to collapse
Sure man...Edited the OP... :good: Actually i found it on another site it didnt mention anyone so i posted like that only....Anyways nice work

Thanks and very useful.

Hey guys, it takes an incredibly long time to download the stock ROM, anybody have a solution for this? It also just stops and says 'network error' at 0.3gb. So I can't unbrick my phone really.

coolkingler1 said:
Hey guys, it takes an incredibly long time to download the stock ROM, anybody have a solution for this? It also just stops and says 'network error' at 0.3gb. So I can't unbrick my phone really.
Click to expand...
Click to collapse
More firmware found here https://mirrors.lolinet.com/firmware/moto/addison/official/
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime said:
More firmware found here https://mirrors.lolinet.com/firmware/moto/addison/official/
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found a good mirror at the Rooting thread but thanks!

TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.

abhilash_s_j said:
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
Click to expand...
Click to collapse
Nope works fine for me...anyways here is the direct link:
https://mega.nz/#%21yZ4lUCYB%21-nN0jj2Ws5Z7RNyBT7S8m4gsrdOxTlK3nTjn9zOtx6s

Thank you for the effort

Thanks for your work!
Sent from my Nexus 6 using XDA-Developers Legacy app

TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
---------- Post added at 01:37 AM ---------- Previous post was at 01:14 AM ----------
After flashing the original firmware of my device, there is no network signal, i cannot make calls, cannot use data, in general the SIM does not work. Does anyone knows how to solve this?

kkarora said:
TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
---------- Post added at 01:37 AM ---------- Previous post was at 01:14 AM ----------
After flashing the original firmware of my device, there is no network signal, i cannot make calls, cannot use data, in general the SIM does not work. Does anyone knows how to solve this?
Click to expand...
Click to collapse
Check your IMEI, I think that you have lost It.

Hitachy said:
Check your IMEI, I think that you have lost It.
Click to expand...
Click to collapse
Yes IMEI is showing 0. How to restore it back...?

kkarora said:
Yes IMEI is showing 0. How to restore it back...?
Click to expand...
Click to collapse
If you have a twrp backup, restore It. If you don't have, assistance.

Asus zenfone 2(ZE551ml/ZE550ml)UNLOCK, UNBRICK, CUSTOM RECOVERY, FIX IMEI....and more

This document ALSO provides knowledge about android system work flow
The following Steps will help and resolve issues related with Zenfone 2 Series,
Do remember that most of the steps which are provided here are not automated, So have patience.
This guide will help you Recover Completely bricked mobiles - You are responsible for you own actions
We will try to do
1. adb and fastboot installtion
2. Unlock Bootloader
3. Custom Recovery Installation
4. Root Device
5. Unbrick (Asus Zenfone 2 ze551ml/ze550ml ONLY)
6. Recover lost IMEI's and Device Serial number( Of course the valid one Which is mentioned for your device ) (Asus Zenfone 2 ze551ml/ze550ml ONLY)
7. Recover serial number, mac, bluetooth address (Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________
*************************** 1. adb and fastboot installtion ********************************
____________________________________________________________________________________________​
used for Basic troubleshooting and updating android system
In windows just copy these four files into windows(c:/windows) folder or install it in windows folder
AdbWinApi.dll AdbWinUsbApi.dll adb.exe fastboot.exe
Download Link https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
For Linux refer distribution guide
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
********************************** 2. Unlock Bootloader ************************************
____________________________________________________________________________________________​If you are on Android L(5.x) Asus provide boot loader unlock tool you can download it from asus.com
Doing so will make your device warranty void. or you can use custom bootloader unlock
if you are on Android M(6.x) Asus doesn't provide any tool to unlock for Android MM
You should use custom bootloader unlock you can follow the procedure provided by the unlock tool
FAQ
Can we relock device ?
YES
Why we need to unlock bootloader ?
Bootloader is a program which will allow your device to load Android OS
Why Bootloader is locked ?
To protect the devices from unauthorized access to third party. More of Business tactics
How to
Download the file from https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!Ux9HlCzA zip file which corresponds to your Device
follow the instructions provided in the zip file
The successful of that unlocking process conclude that your device bootloader is unlocked, but its not ROOTed
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************************** 3. Custom Recovery Installation *******************************
____________________________________________________________________________________________​
There are majorly two custom recoveries used
* CWM - clock work MOD
* TWRP - Most flexible recovery mode ( more than just recovery)
you can download cwm from link (search google)
and TWRP from https://twrp.me/Devices/
once you downloaded the binary file from respected link provided
boot the device into fastboot mode
Follow Steps (only Asus Devices)
--------------------
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* fastboot devices - (in Computer prompt) wait till your device listed
* fastboot flash recovery filename(cwm.img or twrp.img) - it will take 20-50 Sec to complete
* press vol+ or Vol- until you see recovery mode on the screen and press power button
Once all the steps completed successfully you should be able to see the custom recovery screen
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
************************************ 4. Root Device ****************************************
____________________________________________________________________________________________​
Everyone who started using android device they all come across the word "ROOT" soon or later.
No wonder, whoever have root access to device can do wonders on android device. Root is nothing but having administrator privilege to make system wide changes, changes applied using root will applied without any question. no more, no less. whatever happens to device(system) you are your own, "SU" is nothing but "super user" and root is a super user which is from UNIX and Linux.
After unlocking android device bootloader, you need to patch su(binary file) command into android system which will allow you to run commands from adb shell prompt as root user.
There is no universal procedure to ROOT device, everything depends on the android device company, so based on manufacturing company you can google and get your device ROOTed
To root your Ze551ml/Ze550ml
Tools Required
---------------
Unlocked Bootloader Asus Zenfone 2(Ze551ml/Ze550ml)
SuperSU-2.78SR1-zf2_6.0.1.zip (Google search SuperSU-2.78SR1-zf2_6.0.1) download the zip file which has zf2 in filename or try https://www.yadi.sk/d/vVk0Qd-Ow7fdK
Custom Recovery (TWRP or CWM)
Steps to Root Device
---------------------
# copy SuperSU-2.78SR1-zf2_6.0.1.zip file into sdcard
# adb reboot recovery
OR
* Turn off the mobile, Press and hold the volume UP button, Then press and hold the power button until device vibrates release only power button, once you see the ASUS logo release the Volume button
* press vol+ or Vol- until you see recovery mode on the screen and press power button
# From TWRP main screen select install
# Browse and select SuperSU-2.78SR1-zf2_6.0.1.zip from sdcard
# select reboot
# adb shell
# su ( allow the permission from superSU app on mobile)
That concludes you are at root prompt (Device Rooted successfully)
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
*************************************** 5. UNBRICK *****************************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
____________________________________________________________________________________________​
Cause
----------------
Custom or Wrongly flashed ROMS
Most of the time unlock bootloader and ROOTing device leads to bricked mobile
Symptoms of bicked Device
------------------------------
1. Black Screen - You can sense vibrations only, from the device when you press power button but nothing on the screen(Unless screen hardware faulty)
2. Vibrations - Device keeps on vibrating at same interval of time (usually every 5-10 mins loop)
Tools required
-------------------
- Xfstk windows application (google search "xfstk-downloader_v1.7.0")
- Intel Soc windows driver (google search "iSocUSB-Driver_v1.2.0")
- xFSTK_ZE551ML-sal358-amtech.vn.zip do (google serach "xFSTK_ZE551ML-sal358-amtech.vn" download the zip file which contains 3 bin files)
- Asus user UL-Z00A-xx-x.xx.xx.xxx-user.zip you can download this zip file from asus website (https://www.asus.com/in/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/)
- partition.tbl (https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB)
some files are located at https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Remember the windows operating system will block some of the drivers from loading on windows 7, 8 or 10 just override that, install the driver first, Intel Soc windows driver after that install Xfstk windows application
How to Steps
--------------
* Open XFSTK Downloader, Click MRD tab A0 / B0 + A0 + CRC Tab, scanning shows Moorfield in device list.
* Click Options--> modify settings check Enable Override and change GP Flag overide value 0x800000807. Click OK.
* Change value of Device detection timeout to 120
* FW DNX should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* IFWI should point to ifwi.bin (browse and locate)
* OS DnX dont make any change to this field
* OS Image should point to droidboot_dnx.img.POS_sign.bin (browse and locate)
* Click Begin Download (Remember Once you see Scanning ....... device detected:1 which will be changing 0 to 1, couple of times wait till you see download sucessful before that mobile screen goes on and off let it continue for couple of minutes usually (2-5 mins) later you see 4 color strip on mobile screen and it enter into fastboot mode if you see that, your device is unbricked. if you dont see fastboot mode just turn off your mobile and try to enter into fastboot mode using volume up (press and hold) and power button(Press and hold release only power button when device vibrates)
* extract UL-Z00A-xx-x.xx.xx.xx-user.zip into a folder and copy partition.tbl into same folder open command prompt in that folder
* Run these commands one after another on every sucessful completion of command
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
* select Recovery mode using volume up or down key and press power button
* When you see android logo on the screen press and hold power button, press and release volume up key then release power button
* select sideload using voulme key and press power button
* on computer enter adb devices, should show connect device
* Run command adb sideload UL-Z00A-xx-x.xx.xx.xx-user.zip and enter, this command will take minimum 20-30mins to complete
if everything goes well your device is back to life, Congrats
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
******************** 6. Recover lost IMEI's and Device Serial number **************************
(Asus Zenfone 2 ze551ml/ze550ml ONLY)
IT's ILLEGAL TO TAMPER IMEI RELATED INFORMATION AND IT IS PUNISHABLE OFFENCE
THIS IS JUST AN OVERVIEW AND
FOR KNOWLEDGE PURPOSE ONLY​____________________________________________________________________________________________​Its mobile user's NIGHTMARE when they see Wrong IMEI and serial number
Cause
---------------------------
Custom or Wrongly flashed ROMS
Symptoms of Wrong IMEI and Serial Number
-------------------------------------------
Unable to connect to network even though mobile boots properly and works normally
How to Check
---------------
When you run adb devices from your pc its shows device serial number
IMEI can be checked in Settings --> About --> Status --> IMEI information OR
Call Dialer enter *#*#4636#*#* and select Device Information
Tools required
-----------------
Digma_SoFia_IMEI_recovery.rar (Google search "Digma_SoFia_IMEI_recovery file contains contains Digma software and windows driver)
IntelAndroidDrvSetup1.10.0.exe (Google search "IntelAndroidDrvSetup1.10.0") IntelAndroidDrvSetup1.10.0.exe
Rooted Device
links
Digma - https://yadi.sk/d/30q9w4KJjvgHd
IntelAndroidDrvsetup - https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw!0483WIxB
Steps :
* To identify the com port turn on your device and run command adb shell(from computer command prompt)
* Run su
* your device should be rooted so it will give su prompt(#)
* Run setenforce 0
* Run setprop system.at-proxy.mode 1
* Install IntelAndroidDrvsetup and intel mobil family imc1 driver which is included in Digma software ( This is the hard part to setup as windows driver installation restrictions and identifying com ports on usb interface make sure these software and driver installed properly)
* after successful installation of driver and Phonetool run Phonetool
* settings --> Phonetool check RTS and DTR on select your phone com port listed in port list click ok
* click on update info (Should say success connecting to port)
* Click modes --> security click on show advanced options
* Click unlock
* Click on personalization programming tab
* scroll down and click add button
* add your mobile phone imei number (only first 14 digits) again add one time if you mobile is dual sim phone
* Click Execute (will take upto 60 sec)
* if above all steps completed without any error, just reboot your phone and check your imei number should show your real imei numbers
Note some times you needs to flash imei number after setting setprop system.at-proxy.mode 3 to flash 2 imei number just try until both imei show correctly on you mobile check your imei number by dialing *#*#4636#*#*
HIT THAT THANKS BUTTON IF IT HELPS
____________________________________________________________________________________________
**************** 7. Recover serial number, mac, Bluetooth address **************************
____________________________________________________________________________________________​
Refer https://forum.xda-developers.com/showpost.php?p=66877096&postcount=28 Thanks to BORETS24

Thanks, helped a lot.

Unsure of what happened to my phone
Hey, I was trying to root my zenfone 2 ZE551ml by following a youtube video. It asked me to first put superSu.zip inside the SD Card which I did. Next - unlock the bootloader of my phone by downloading an zip which has an unlocker.bat file. Then it asked me to flash TWRP recovery using fastboot which I also did and then to boot into twrp and install the supersu.zip. I did everything but the last step, as when i tried to boot into the recovery to use twrp, the phone restarted, came to the white asus screen, stayed there for a very long time and then went back into the bootloader.
At this point I got frustrated and thought of reinstalling everything. So I downloaded the zip file for the latest firmware, flashed recover, boot and droid boot and then when I restarted the phone to go into the recovery, the white asus screen just keeps on repeating itself. The device keeps on shutting down and then restarting but never goes past the white asus logo screen where it says "powered by android", doesn't even let me get into fastboot.
I am new to all this and any help from anyone is highly appreciated. Thanks

error loading partition.tbl? edit: now im stuck on "cannot load fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin "

after doing these steps
fastboot oem erase_osip_header
fastboot oem erase_token
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase APD
fastboot erase ADF
fastboot oem wipe splashscreen
fastboot oem stop_partitioning
fastboot flash splashscreen splashscreen.img
fastboot flash token bom-token_ann_a0-mofd_v1-ze551ml.bin
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin (Note This file is located in ifwi.zip)
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
when i reboot and select recovery i cant load recovery , it opens bootloader
how to install recovery

Hi, good day.
I am having 0 response when I hit this command. setprop system.at-proxy.mode (number) Do you know why ?
Device is rooted, since I've unlocked the bootloader using the ASUS app.

Fastboot erase config....
After that I stucked at boot logo
Used xfstk then aft but stucked at boot used fastboot commands for flashing system all gonna smooth but stucked at boot...
Used recovery to sideload marshmallow ... succeed. But also stucked at boot ..unlock boot loader flash TWRP flashing custom rom also stucked at boot logo... PLZZ help me guyzzz
And it shows error in TWRP
Unable:to mount Config(invalid argument)

I'm on step, Run setenforce 0, but it returns an error message, "Couldn't set enforcing status to '0': Permission denied". Please advise. Thank you in advance!

[Z2/Z2 Plus] [Z2131/2] Ultimate Bootloader Unlock & TWRP Install Guide

There are many guides for unlocking bootloader and installing TWRP and there are many misconceptions redarding these.
This is the ultimate guide put together to clear all those.
*Use Mozilla Firefox to get the unlock_bootloader image* Chrome isn't working due to bugs in site
Things you need:
1. ZUK Z2 (Z2131/Z2132) [Obviously]
2. "unlock bootlader.img" from developer.zuk.com
3. Minimal ADB and Fastboot from Here
4. Latest TWRP from Here
5. If you want to root download SuperSU from Here
6. MI Flash Tool from Here
Unlocking bootloader factory resets the device, so backup your files before hand.
Getting the Unlock Image:
This one thing is a big problem to attain for many users.
1. Head to developer.zuk.com (Use Chrome to translate the page)
2. Click Login and use the following details
Username: [email protected]
Password: zukaccount!
Account doesn't work anymore, but you can easily create an account now.
(Login before heading to unlock page)
3 .Click Unlock at the top.
4. Click NEXT on Step 1.
5. Select Z2 from dropdown list.
6. Type in your Serial Number. (You can find it at Settings > About > Status > Serial Number)
If you have a 6 character serial number, add two zeros at end
If you have a 7 character serial number, add one zero at end
7. Give your email ID (Gmail works too)
8. Accept the conditions and click NEXT.
9. A Dialog Box opens up stating that you will recieve an email with the bootloader image.
10. Check your Inbox and Spam folders.
Unlocking Bootloader:
1. Install Minimal ADB and MI Flash (to ensure you get all drivers)
2. Place the "unlock_bootloader.img" in the fastboot installation folder.
3. Run following commands.
(a) adb devices [Your device should be listed, if not, check drivers]
(b) adb reboot bootloader
(c) fastboot -i 0x2b4c flash unlock unlock_bootloader.img
You should see this:
"target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.037s]
writing 'unlock'...
OKAY [ 0.053s]
finished. total time: 0.090s"
(d) fastboot -i 0x2b4c oem unlock-go
You should see this:
"OKAY [ 0.041s]
finished. total time: 0.041s"
(e) fastboot reboot
4. You should end up with an unlocked bootloader.
Installing TWRP:
1. Place TWRP downloaded from official site in the fastboot installation folder.
2. Run the following commands.
(a) adb reboot bootloader
(b) fastboot -i 0x2b4c flash recovery twrp.img
(c) fastboot reboot
3. You have successfully installed TWRP
Rooting using SuperSU.zip
1. Place the downloaded "SuperSU.zip" into the root folder of phone to. (That would be easy to find while installing)
2. Reboot to TWRP
3. Select Install and locate SuperSU.zip
4. Swipe to flash.
You should end up with a unlocked and rooted Z2.
Comment for flaws or if you want me to add more info at a specific step.
Note:
If you get a message saying "Daemon started succesfully" re-run the previous command.
TWRP Links:
TWRP 3.1.0
TWRP 3.1.1
TWRP 3.2.1
Thanks to Balraj at zukfans.eu for Login Details
Goodluck Unlocking :good:
Hit thanks if this helped you.

And finally a guide for newbies like me btw is there any tool to unlock bootloader and flash ROMs like other devices?

AkumDX said:
And finally a guide for newbies like me btw is there any tool to unlock bootloader and flash ROMs like other devices?
Click to expand...
Click to collapse
Happy that this helped you. I don't​ think there is any tool for unlocking and flashing (I think you are refering to ODIN for Samsung). But you can use QPST or MI Flash to flash Stock ROMs.

i stuck in second step
2. Place the "unlock_bootloader.img" in the fastboot installation folder.?????
where is this location
please help me
i can go in adb mode but i cant find the location
I FIND IT i am soo nood

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i cant unlock bootloader :crying: :crying:
---------- Post added 4th June 2017 at 12:33 AM ---------- Previous post was 3rd June 2017 at 11:54 PM ----------
fix it

MacGyverLarisa said:
i stuck in second step
2. Place the "unlock_bootloader.img" in the fastboot installation folder.?????
where is this location
please help me
i can go in adb mode but i cant find the location
I FIND IT i am soo nood
Click to expand...
Click to collapse
Generally it is Program Files or Program Files (x86) > Minimal ADB and Fastboot

zakaria12 said:
i cant unlock bootloader :crying: :crying:
---------- Post added 4th June 2017 at 12:33 AM ---------- Previous post was 3rd June 2017 at 11:54 PM ----------
fix it
Click to expand...
Click to collapse
Did you fix it? If not check if you have given your serial number correctly on unlock request page. You need the device specific image

sammessi10 said:
Generally it is Program Files or Program Files (x86) > Minimal ADB and Fastboot
Click to expand...
Click to collapse
Thank you for your response
After a little thought
I Put it inside the folder that I start to adb mode and it works perfectly

Is it possible to regain warranty after locking bootloader or is the warranty lost ?

Hi is it possible for any one to upload the TWRP.img file ?
I tried it with the one which is in twrp (twrp-3.1.1-0-z2_plus) app however its not working.
It showed flash completed however its still loading old recovery.
i'm currently on android 7 with boot loader unlocked.
Thanks

zakaria12 said:
i cant unlock bootloader :crying: :crying:
---------- Post added 4th June 2017 at 12:33 AM ---------- Previous post was 3rd June 2017 at 11:54 PM ----------
fix it
Click to expand...
Click to collapse
how did you fix that?

aditya1999 said:
how did you fix that?
Click to expand...
Click to collapse
i just request the bootloader Unlock image again because its was Damaged and i flash it and its work

coolsid8 said:
Is it possible to regain warranty after locking bootloader or is the warranty lost ?
Click to expand...
Click to collapse
Yeah it is possible to regain warranty. Flash the stock firmware with QPST or Miflash

akash.mahadeshwar said:
Hi is it possible for any one to upload the TWRP.img file ?
I tried it with the one which is in twrp (twrp-3.1.1-0-z2_plus) app however its not working.
It showed flash completed however its still loading old recovery.
i'm currently on android 7 with boot loader unlocked.
Thanks
Click to expand...
Click to collapse
Try to flash 3.1.0 first and then 3.1.1

zakaria12 said:
i just request the bootloader Unlock image again because its was Damaged and i flash it and its work
Click to expand...
Click to collapse
Thanks I did the same.

Thanks for the guide. Pls do add that ZUK Z2 is not recognized as a device in fastboot.
So one must specify the OEM id . The code is "-i 0x2b4c " for Zuk Z2. So any command fastboot must be suffixed with the following code: -i 0x2b4c

My device doesn't gets detected in fastboot mode by my pc. I have tried all drivers of Lenovo and other manufacturers drivers but it can't detect my device in fastboot mode. But it detects the phone in adb and gets booted to fastboot mode and when i run the command fastboot -i 0x2b4c flash unlock unlock_bootloader.img.
It shows waiting for device . Please Help anyone!.

mity_dev said:
My device doesn't gets detected in fastboot mode by my pc. I have tried all drivers of Lenovo and other manufacturers drivers but it can't detect my device in fastboot mode. But it detects the phone in adb and gets booted to fastboot mode and when i run the command fastboot -i 0x2b4c flash unlock unlock_bootloader.img.
It shows waiting for device . Please Help anyone!.
Click to expand...
Click to collapse
Same with me.. i think it's beacause of nougat as this method is working fine with marshmallow.

sammessi10 said:
There are many guides for unlocking bootloader and installing TWRP and there are many misconceptions redarding these.
This is the ultimate guide put together to clear all those.
Things you need:
1. ZUK Z2 (Z2131/Z2132) [Obviously]
2. "unlock bootlader.img" from developer.zuk.com
3. Minimal ADB and Fastboot from Here
4. Latest TWRP from Here
5. If you want to root download SuperSU from Here
6. MI Flash Tool from Here
Getting the Unlock Image:
This one thing is a big problem to attain for many users.
1. Head to developer.zuk.com (Use Chrome to translate the page)
2. Click Login and use the following details
Username: [email protected]
Password: zukaccount!
(Login before heading to unlock page)
3 .Click Unlock at the top.
4. Click NEXT on Step 1.
5. Select Z2 from dropdown list.
6. Type in your Serial Number. (You can find it at Settings > About > Status > Serial Number)
If you have a 6 character serial number, add two zeros at end
If you have a 7 character serial number, add one zero at end
7. Give your email ID (Gmail works too)
8. Accept the conditions and click NEXT.
9. A Dialog Box opens up stating that you will recieve an email with the bootloader image.
10. Check your Inbox and Spam folders.
Unlocking Bootloader:
1. Install Minimal ADB and MI Flash (to ensure you get all drivers)
2. Place the "unlock_bootloader.img" in the fastboot installation folder.
3. Run following commands.
(a) adb devices [Your device should be listed, if not, check drivers]
(b) adb reboot bootloader
(c) fastboot -i 0x2b4c flash unlock unlock_bootloader.img
You should see this:
"target reported max download size of 1610612736 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.037s]
writing 'unlock'...
OKAY [ 0.053s]
finished. total time: 0.090s"
(d) fastboot -i 0x2b4c oem unlock-go
You should see this:
"OKAY [ 0.041s]
finished. total time: 0.041s"
(e) fastboot reboot
4. You should end up with an unlocked bootloader.
Installing TWRP:
1. Place TWRP downloaded from official site in the fastboot installation folder.
2. Run the following commands.
(a) adb reboot bootloader
(b) fastboot -i 0x2b4c flash recovery twrp.img
(c) fastboot reboot
3. You have successfully installed TWRP
Rooting using SuperSU.zip
1. Place the downloaded "SuperSU.zip" into the root folder of phone to. (That would be easy to find while installing)
2. Reboot to TWRP
3. Select Install and locate SuperSU.zip
4. Swipe to flash.
You should end up with a unlocked and rooted Z2.
Comment for flaws or if you want me to add more info at a specific step.
Note:
1. Unlocking bootloader factory resets the device, so backup your files before hand.
2. If you get a message saying "Daemon started succesfully" re-run the previous command.
TWRP Links:
TWRP 3.1.0
TWRP 3.1.1
Thanks to Balraj at zukfans.eu for Login Details
Goodluck Unlocking :good:
Hit thanks if this helped you.
Click to expand...
Click to collapse
Bro I have some questions
1st does Z2 (Z2131) custom ROM could be flashed on Z2 Plus(Z2132)?
2nd of yes then what is brushed ROM

shridhan varadkar said:
Bro I have some questions
1st does Z2 (Z2131) custom ROM could be flashed on Z2 Plus(Z2132)?
2nd of yes then what is brushed ROM
Click to expand...
Click to collapse
1. Yeah... Both the ROMs are interchangeable.
2. I never heard of it but if you are talking about Bshuy ROM, then it's a bloatfree stock ROM.
PS: Please don't quote the whole OP

Back to Stock all in one - enable dm-verity, lock bootloader, flash latest OOS

I wanted to create a guide which is as simple as rooting a OnePlus 3T. I don’t know if it will work with the OnePlus 3. I’m not responsible for anything. You’re doing it on your own risk, so only do it if you know what you will do, now! It may brick your device.
This is the way it worked for me. I do not guarantee it will work for you!
READ THE WHOLE INSTRUCTIONS FIRST BEFORE YOU DO ANYTHING​
What we do:
- Flash TWRP
- Flash an old version of OOS
- Enable dm verity
- Relock the bootloader
- Flash the latest stock rom
What you need:
- Computer (Windows 7 or 10)
- USB Cable
- about 1 hour of your lifetime
YOU WILL LOOSE ALL YOUR DATA - ALSO THE INTERNAL STORAGE WILL BE DELETED (pics, music and all the stuff stored there)​
Download to your computer:
Latest TWRP for OnePlus 3T
https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
and
latest OOS from OnePlus for your 3T
http://downloads.oneplus.net/
THE USB DRIVERS MUST BE INSTALLED ON YOUR COMPUTER​
Download to the phone:
4.0.2 OOS Stock rom (post #2)
https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308
Flash TWRP:
1. Start your phone in fastboot mode (don’t connect to your PC yet!)
2. Open CMD as Admin (Windows start-menu - type “cmd”, right-click, run as administrator)
3. connect your phone
4. rename the file to “recovery” (don’t type “recovery.img” manually, only “recovery”)
5. type command “fastboot devices” -> device will be listed
6. command “fastboot flash recovery C:\Users\...\recovery.img” (the path where it’s stored)
7. done -> boot to recovery
8. disconnect your phone - leave CMD open
Flash OOS 4.0.2
1. Go into TWRP
2. wipe “System, Data, Cache, Dalvik”
3. Install OOS 4.0.2
4. reboot into fastboot
Enable dm-verity:
1. connect your 3T when it’s back in fastboot
2. type in CMD “enable dm-verity”
3. done - keep CMD open and the phone connected
Relock the bootloader:
1. type in CMD “fastboot OEM lock”
2. Warning message on your phone will pop up -> choose “yes” on your phone by using the volume buttons to lock the bootloader (keep CMD open)
Update to the newest OOS via “sideload”:
1. VOL down to boot into recovery
2. choose “Install from ADB”
3. “Upgrade Android from USB?” -> “Ok”
4. rename the OOS zip file to "update"
5. type in CMD “adb sideload C:\Users\...update.zip”
6. done
7. reboot the device - it will take about 10 minutes, DO NOT INTERRUPT THE PROCESS
Finish
Take your time! Don't do it if you're in a rush.
Please give me feedback if it worked for you or if I have to change something.

enable dm-verity doesnt work
"enable is not recognised..."

chowchillacharlie said:
enable dm-verity doesnt work
"enable is not recognised..."
Click to expand...
Click to collapse
Did you check if the device is listed in fastboot?
You can also try the command "disable" and then "enable"
Sometimes you may need to do it first, even if it's disabled

Thanks for your threat. I tried this but had to do a couple things differently.
I think enabling/disabling dm-verity works only with old firmware.
What I used:
* 4.0.2 firmware from this threat https://forum.xda-developers.com/oneplus-3t/how-to/firmware-modem-collection-flashable-zips-t3565535
* latest oneplus recovery and rom https://downloads.oneplus.com/
* the recovery can be downloaded from a link on the bottom of the rom download site.
I started with twrp and a custom rom.
You need usb debuging enabled and adb and fastboot installed
What I did:
* I did a Nandroid backup, and copied the sdcards content to my computer, because the following completely wiped my phone
"adb pull /sdcard /path/to/my/drive/"
* flash 4.0.2 firmware, with trp
enter adb sideload mode in twrp and
"adb sideload firmware.zip"
* fastboot flash oneplus recovery
"fastboot flash recovery recovery.img"
* using onplus recovery and sideloading installed latest oneplus rom
enter adb sideload and
"adb sideload oneplusrom.zip"
* did a factory reset in oneplus recovery and cheked if my phone would boot
* entered fastboot mode
"fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity"
"fastboot oem lock"
after that my phone got wiped again, and the next boot took a long time
Then the phone was completely stock

Wanted to post to say thanks to roor7 and WhataHulk - had a rooted 3T I wanted to sell following an upgrade (best price requires the phone to have no sign of root!), and this was the only method that worked for me to enable dm-verity.
As a quick note, I followed roor7's guide, but got the same error message as chowchillacharlie. After sme playing about I found the simplest soultion was using the CMD line provided towards the end of WhataHulk's guide, i.e. - "fastboot oem disable_dm_verity", then "fastboot oem enable_dm_verity". For me, roor7's guide swapping the type "enable dm-verity" in CMD with "fastboot oem enable_dm_verity" worked a treat.
Sorry if that is all incredibly obvious to most people!
Thanks again gents.

How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL​
Hey everyone,
It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.
You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
How to bootloader unlock and root the Nothing Phone 1​After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:
Step 1: Unlock the Nothing Phone 1’s bootloader​
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.3) binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
[NOT A MANDATORY TO UNLOCK CRITICAL, IT'S FOR ME BETTER TO NOT USE THIS COMMAND, THIS COMMAND COULD BE THE REASON SOME PEOPLE HAVE BRICK OR NOT WHEN GO BACK STOCK NOS]
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Step 2 - Rooting your Nothing Phone 1 with Magisk​With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
Depending of your model, you have Global or EEA (European) firmware availables.
You can download the latest full OTA firmware package here.
Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
Download and install the Magisk app on the Nothing Phone 1.
Open the Magisk app and tap on the Install button.
Choose Select and Patch a File. A file manager will pop up.
Select the boot image that you pushed earlier and let Magisk patch it.
Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
Reboot the Phone 1 into the bootloader: adb reboot bootloader
Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
Reboot the phone: fastboot reboot
Open the Magisk app and your Nothing Phone 1 should be rooted.
Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.​
-=o#0#o=-​
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.​
Spoiler: Relock the bootloader of your Phone(1)
menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
#root #nothingphone

Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -​
Click to expand...
Click to collapse
Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding
STEP 1: What you need and read before the process.
It’s really important for a process without problems
Install Android SDK and the Platform-tools folder
Download the Nothing OS version you need (see this post)
Extract the "payload bin" file from the rom
Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
Unlock the bootloader of your Phone(1) (see this tutorial)
STEP 2: Boot the bricked phone 1 into Fastboot mode
Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.
Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.
In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.
STEP 3: Format the device via Fastboot
1.Go to the platform-tools folder where the extracted ROM is located.
2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
3.Now run the following command to perform a factory reset (optional but recommended)
Code:
fastboot -w
STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
Don't forget to check your command line before validating it, because often a small error blocks you!
Spoiler: Command Lines
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
flash fastboot dsp dsp.img
flash fastboot dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img fastboot
fastboot flash product product.img
fastboot flash qupfw qupfw.img
flash fastboot shrm shrm.img
flash fastboot system system.img
flash fastboot system_ext system_ext.img
flash fastboot tz tz.img
flash fastboot uefisecapp uefisecapp.img
flash fastboot vbmeta vbmeta.img
flash fastboot vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash vendor_boot vendor_boot.img
flash fastboot xbl xbl.img
fastboot flash xbl_config xbl_config.img
Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
Code:
fastboot reboot
Well done , you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands.
I hope this tutorial has helped you find your Phone(1).
Thanks

Reserved

FILES FOR NOTHING OS - (stock-boot, etc. )
UPDATE 15/12/2022
Stock_Boot for Nothing OS here
Be carefull, be sure to select the good Stock Boot "Global" or "EEA" for your device.​

Extract Payload.bin via Payload Dumper Go
To start, download the payload-dumper-go 1.0.0 from Github [Credits: XDA Member @ssssut].
Then extract it to any convenient location on your PC. The file name will be something like payload-dumper-go_1.0.0_windows_amd64.
Rename it to payload-dumper-go.
Next, download the liblzma-5.dll file and transfer it to the same folder where the payload-dumper-go.exe file is located.
After that, transfer the payload.bin file to this folder as well.
So, from now on, you should have the 3 files payload-dumper-go.exe, payload.bin and liblzma-5.dll in one folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to the address bar of that folder, type "cmd" and press Enter. This will launch the command prompt window.
Type the command below to extract the payload.bin file:
Code:
payload-dumper-go payload.bin
The extraction process will now begin and will only take a few seconds.
Once this is done, all extracted files will be placed in a folder named extract_date_time which is created in this directory like this name : extracted_20220731_145751
The process is very simple and very fast. Anyone can do it. So don't hesitate, you have everything you need to do this yourself.
it's up to you now
If this has helped you, and if you appreciate my help.
Thanks

Is it possible to relock the bootloader?
Is it possible to relock the bootloader on an third party ROM?

@Sib64 does the device keep Widevine L1 when the bootloader has been unlocked?

Krullendhaar said:
Is it possible to relock the bootloader?
Click to expand...
Click to collapse
Yes.
Krullendhaar said:
Is it possible to relock the bootloader on an third party ROM?
Click to expand...
Click to collapse
No.

Could you also do a tutorial on how to update the OS when you're rooted?

I hope to find an EDL QPST full rom... better to stay safe and restore It in any case...
Mod is coming...

I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Is rooting success with 1.1.0 Rom?

Naveenakash said:
Is rooting success with 1.1.0 Rom?
Click to expand...
Click to collapse
I didn't try it with an actual app, but it was showing properly in Magisk. But bootloader needs to stay unlocked.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Did you fix that issue?

Naveenakash said:
Did you fix that issue?
Click to expand...
Click to collapse
I didn't. I'm trying to factory reset the phone, but I can't seem to flash the ROM from bootloader.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.

No matter from which partition (A/B)
lba810701 said:
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
Click to expand...
Click to collapse
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.

ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
And what if you flash back the original bootloader to over the unlocked one, and after it you close it, not the modded one?

ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
Also, doing a factory reset from recovery doesn't relock the bootloader either.

I've tried now to sideload the .zip but it seems that even the supposed 1.1.0 full OTA zip available in the other post is older than my current ROM, so it can't be flashed like that. I'll have to wait for the next update.