[Guide] ALLDOCUBE X NEO Flash Class 101 - Device Reviews and Information

Hello and welcome here.
I’m Warren, an X NEO user from Mainland China .
X NEO is a great device that opens all low-level permissions to users, but it is undeniable that it is far more difficult to flash than Xiaomi's devices, especially the logic of the A/B partition。
Fortunately, through the help of many people, I successfully overcome many difficult problems, and now I decided to write a Thread like a guide book to integrate some basic knowledge of the flash to X NEO.
Each part of this post will contain the following:
a) Materials needed for flashing
b) Instructions for flashing steps
c) Possible problems and solutions

Attention !!
a) I will spend some time (maybe a few days?) to update everything
b) All content is written in simplified Chinese and translated into English by Google translation machine for reading. This is due to forum restrictions
c) Due to the use of machine translation, the grammar and vocabulary are unavoidably rigid, and I don’t want to manually proofread him for the time being. Because I don’t have enough energy, I have written the original document as closely as possible to the English writing logic
d) I understand English, so I can send out any questions or private messages without worry
e) The content of the post is my own original, but many materials and ideas are provided by users at home and abroad, including several masters from XDA and hardware forums. I just did some trivial sorting and reproduction work, here Thank them for their hard work
f) Have fun

#0 Preparation
Step 1 Download materials & prepare environment
This part is very important, it will be directly related to the success or failure of subsequent work (because of lack of necessary environment or materials)
How to do?
1. Save the file in this MEGA address: HnwhAIhJ#uVaWZIzUOUcAIwAbcrNMsg
2. Download ADB
3. Unzip (you can move the unzipped folder to any place you like)
4. Remember this path. Anytime I say "Run an ADB command/open ADB input", you can open this path, right-click on the blank space of the folder to open the command prompt book and enter the command.
5. Download Magisk on github
Step 2 Flash your device to the Chinese version of the firmware
a) This is because the Chinese version of the firmware is more modifiable than the overseas version
b) The following content will be based on the "200522" firmware (I know this is not the latest, but the updated version has not been confirmed by me)
c) If you insist on downloading the latest firmware, you can go to the official website of Cube China
How to do?
1. Download "XNeo(T1009)-Android9.0-200522-Firmware&Tutorial.rar" in the "Firmware-China" folder of MEGA and unzip it
2. Follow the official instructions in the folder (documents in the root directory) to flash the firmware
note:
a) The device can and can only be flashed in Qualcomm 9008 mode (the official data cable supports this function)
b) The official instruction book is in simplified Chinese, if you don’t understand Chinese, translate it
Step 3 Confirm ADB environment and OEM unlock
How to do
1. Open ADB
2. Type "ADB" and press Enter (the self-check information indicates that the environment is established successfully)
3. Turn on the tablet
4. Enter Settings-System-About Tablet
5. Click the version number until the floating prompt appears
6. Go back to the upper level (system) and enter the developer options
7. At this time, "OEM Unlock" should be opened automatically and cannot be changed
8. Click to open "USB debugging" and connect to the computer to activate the function according to the prompts
9. Click to open "Verify App via USB" to activate the function

#1 Official system customization
a) First of all, the official version of the system is a typical simple ASOP system based on Android 9. It is not much different from third-party customized systems such as Los to a certain extent. If you don’t want to be too tossed, you can use it directly after optimization according to the following guidelines
Step 1 Brush into third-party REC (TWRP)
a) N/A
How to do it?
1. Download "TWRP-CUBE_X_Neo-20200522.img" in the "TWRP" folder in MEGA
2. Copy to the path of ADB
3. Open ADB
4. Type "adb devices" and press Enter
5. Type "adb reboot bootloader" and press Enter
6. Type "fastboot flash boot_a .\recovery.img" and press Enter
7. Enter "fastboot flash boot_b .\recovery.img" and press Enter
8. The flashing completion prompt is displayed twice
9. Now that TWRP has been successfully swiped in, you can enter the recovery mode through the volume button and power button
note:
a) Flashing into a third-party REC will cause OTA failure (over-the-air upgrade is not possible)
Step 2 Flash into Magisk
a) Have Root permissions
b) Flash into the module
c) Conveniently flash into the XP framework
How to do?
1. Enter rec
note:
a) You can use the same method to flash in GAPPS components (Google and download by yourself) to use GMS components and related services
b) Magisk version 21.0 is recommended, which is beautiful and will not automatically fail
c) Recommended modules: font module, scheduling module (search and download by yourself)
Step 3 Flash into the XP framework
a) Use certain software/modules that require special permissions and environments
How to do?
1. Open Magisk
2. Go to the online module library that comes with Magisk
3. Find the Riru-Core module to download and install
4. Find the Riru-EDxposed module to download and install
5. Restart the phone
6. Install and open Edxposed Manger (Google and download by yourself) to activate the module
7. Restart the phone
8. Success
note:
a) Edxposed chooses the YAHAFA version instead of the SANDHOOK version
b) Recommended modules: Youtube background playback related, exercise count modification related, camouflage location related, social software beautification and additional functions related
Step 4 Install auxiliary software
a) Green Guardian: Clean up the background and make 4G memory run smoothly (GooglePlay recommends buying genuine)
b) Streamlined version of fluid gesture software (increase system-level full-screen gestures)
c) Force to rotate the old version of the software (add system-level software horizontal screen support)
d) The download links of the above two apps are too low and I can’t send them out. You can get them by private message
Step 5 Uninstall pre-installed third-party software
a) Complete through a third-party software manager
b) The system software can also be appropriately streamlined (pay attention to safety)

Related

[ROOT - ZS570KL] ZenUtil + everything you need to root the Z016D quickly and easily!

ZenUtil was created for use with the Zenfone 3 Deluxe Special Edition ONLY.
Hello everyone my name is Sandman45654. I would like to share a little root utility I put together in my free time over the last couple of weeks. After not having much luck with the root packages/images I found here on XDA and the internet in general I decided to create my own solution! ZenUtil was created specifically for the Zenfone 3 Deluxe Special Edition (SD821) and has been tested on seven different computers. Four physical and three virtual machines. Operating systems from Windows 7 through the latest Windows 10 build have all been tested. Two machines even had fresh Windows installations with no prior ADB driver installations and Wi-Fi set to disabled to ensure drivers were in fact installing and not downloading! This package includes EVERYTHING to get the job done quickly and easily!
Screenshots:
View attachment 4270854 View attachment 4270855 View attachment 4270856
View attachment 4270857 View attachment 4270859 View attachment 4270860
Features:
1. Completely menu driven CMD file! Typing or remembering commands is not required.
2. ZenUtil is able to create a support files (help/uninstaller/log files) dynamically.
3. Install Asus ADB Drivers. Fastboot drivers are also installed but not enabled by default. Instructions below.
4. Install the Asus UnlockTool v1.1 onto your phone.
5. Push the SuperSU 2.82 zip file into \sdcard\ in preparation for rooting.
6. Push just about any file or folder, even over network shares into \sdcard\. Supports drag & drop too!
7. Able to boot TWRP 3.1.1-0 without flashing.
8. Able to boot included stock Asus recovery image (v5.15.44.2562) without flashing. Boots upside down for some reason but works.
9. Reboot into the recovery that is currently installed.
10. Reboot into Fastboot mode.
11. Exit out of Fastboot mode. No more holding for power button for days!
12. Able to flash TWRP 3.1.1-0
13. Flash/restore stock Asus recovery image. It does not boot upside down when flashed.
14. Remove any lock screen PIN/Password/Pattern. Useful after restoring a Nandroid and getting "Incorrect PIN" error.
15. ADB transfers are check and verified as either successful or failed.
16. ADB transfers are also logged with date/timestamps and shown automatically on error.
17. The ADB log file is deleted on each launch to keep it small, clean, and simple.
18. Confirms before any "permanent" actions are completed. (Flash / Pin Removal / Uninstall)
19. Maybe more to come...
ZenUtil will be updated with the latest image files for the foreseeable future regardless.
Included files and versions with notes.
ADB Files = 1.4.2 Minimal (Preferred for logging)
Asus Stock Recovery = Z016_1-WW-5.15.44.2562_recovery.img
Asus UnlockTool v1.1 = UnlockTool-9.0.0.29_ZS570KL_PRO.apk
TWRP = twrp-3.1.1-0-Z016-20170826.img
NO LAG ON BOOT with this version of TWRP!!! I was also able to create, wipe, and restore without the issues of previous versions. Might this be the one?!
Finishing Fastboot driver installation.
Your phone must be connected and in fastboot mode before you are able to install the drivers.
1. Right click on the start button and select "Device Manager" or WinKey+R>devmgmt.msc>enter
2. Right click on "Android" with a yellow ! next to it and select "Update driver".
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of available drivers on my computer"
5. Select "ASUS Android Device" and click next.
6. Select "ASUS Android Bootloader Interface Version: 8.0.0.3 [3/16/2015]" and click next.
7. Click "Yes"
8. Click "Close"
A HUGE thank you goes out to Judago for creating CmdMenuSel!
Downloads:
Download ZenUtil v1.0
Fastboot Help Files (with pics)
hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP
alkis68 said:
hello
I have the ASUS Zenfone 3 Deluxe ZS570KL (Z016S)
but I can not do it ROOT
if it does HELP
Click to expand...
Click to collapse
According to the page below that phone has the Snapdragon 820 and not the 821. So there is high likelihood that this would fail. If the included Twrp is compatible across both phones you could install the bootloader unlock tool from Asus website and then finish rooting with Zenutil. I cannot however say for certain that Twrp would be compatible.
https://www.mobosdata.com/asus-zenfone-3-deluxe-z016s#
Any chance of getting this uploaded again, it's no longer available

[Guide] Enable external Bluetooth for LineageOS (serranoltexx)

The goal of this thread is to help you enable external Bluetooth support for Lineage 14.1. You would want this for example in case you need Bluez tools like l2ping for a BlueSmack attack.
Notices:
I am in no way responsible for any damage you do following this guide. Every step is done at own risk.
The only drawback of this method is that the creation of BT sockets will instantly return and never block so that an application must first wait a few seconds on itself.
I know that this method is far from perfect. I spent 70+ hours to make this work even though I'm not a C# developer. If you have a better method feel free to share it.
Please find some useful files as attachments.
Requirements:
1. The ability to build for your device using Lineage source
2. A fully prepared and ready-to-build directory with Lineage 14.1 source (Refer to this guide in case you do not know what to do)
3. An S4 mini and a compatible USB-togo-cable with external powering.
Steps:
1. Start with a terminal in the root directory of the source
2. Update the repo using "repo sync"
3. go to "kernel/samsung/msm8930-common". This directory will be named "kernel directory" by now on.
4. execute "./make_defconfig samsung_serrano_defconfig"
5. in the config enable everything to be built-in in "Networking support/Bluetooth subsystem support"
6. now go to "Bluetooth device drivers" and check "HCI USB driver" to be built-in
7. save and exit
8. go to "net/bluetooth" in your kernel directory and edit hci_core.c
9. find the method "hci_register_dev" and comment out these 2 lines in it:
if (!hdev->destruct)
return -27;
10. open "l2cap_core.c" in "net/bluetooth" in your kernel directory
11. find the method "l2cap_sock_connect"
12. go to the end of this method and remove the "bt_sock_wait_state" call before "wait:"
13. add these two lines where you removed the call from the step above:
sk->sk_state = BT_CONNECTED;
sk->sk_state_change(sk);
14. Finally, build the source and flash to your device. Before you flash make sure you have an emergency copy of a fresh Lineage build on your device in case something with the USB drivers goes wrong
15. Get the app "Linux deploy" and setup Kali Linux.(I tried it with this OS but any other Linux based OS is likely to be working, too)
16. Boot into Kali, plug in your Bluetooth stick and enjoy your working external BT!
Useful Links:
https://wiki.lineageos.org/devices/serranoltexx/build
https://null-byte.wonderhowto.com/h...android-device-with-wireless-adapter-0162943/

[Tutorial] Install Windows 10 for ARM32 on your Surface 2

Hi guys, following the recent release of a Windows 10 ARM32 install tutorial in Chinese to install it on the Surface RT 1 and Surface RT 2, I've decided to come and try my luck by using google translate to follow the procedure and then decided to refine it and to make it into this tutorial for the Surface 2 (The procedure for the Surface 1 should not be much different aside from the files you have to use but as I don't have one, I haven't tried out the files for it...).
Download: https://yadi.sk/d/mnCUeGKWm1XTXA
Requires:
- The files available in the Yandex Repo
- A recovery USB Disk for Surface 2: Surface2_BMR_20.2.19.0.zip (https://support.microsoft.com/en-hk/help/4023512/surface-creating-and-using-a-usb-recovery-drive)
- A keyboard
1. Copy the following files from the yandex repo to the root directory of your recovery disk:
- Disabling_UAC.reg
- SecureBootPatch.zip (extract it)
- APPX1.rar (extract it)
- surface2_win10_zh_cn_new.wim
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
- Camera_fix.reg
2. Boot into Recovery mode (insert the recovery disk, hold the "vol dow" button then press the "power" button and release the "vol down" button when the surface logo appears)
Open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\sources\install.wim /applydir:c: /index:1
3. Reboot the device and Disable UAC, then run "Disabling_UAC.reg" as admin and reboot the device once again
Once the device has rebooted open regedit and go to "HKEY_LOCAL_MACHINE\BCD00000000" select "BCD00000000", click on file and select "unload hive"
Once this is done extract "SecureBootPatch.zip" and open the "SecureBootPatch" folder to run "InstallPolicy.cmd" as admin and then reboot the device once again (l If the secure boot debug policy interface appears after restarting, it means normal. Select accept and install to install)
Open a command prompt as admin and enter the following command to enable test mode :
- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
4. Now we can start serious business and install Windows 10 on the device, to do so, we'll start by rebooting the device in recovery mode (Check the lower right corner to indicate that secureboot is not configured correctly and it will succeed)
Once in recovery mode open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\surface2_win10_zh_cn_new.wim /applydir:c: /index:1
5. Plugin your keyboard and reboot the device, you should get an error message related to the boot configuration, at this moment press shift+f10 and open regedit
Go to the following registry entry: HKEY_Local machine/SYSTEM/Setup/Status/ChildCompletion and then select the "setup.exe" entry, modify it to "3", exit regedit and commandline and click "Ok" on the error dialog box, the device should reboot(don't reboot the device in any other way), and configure correctly now
Configure the system the way you want it
Once on the desktop open a powershell command prompt and type in the following commands:
- slmgr.vbs /upk
- slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
- slmgr /skms kms.03k.org
- slmgr /ato
- slmgr /skms zhang.yt
Your device is now activated
6. We must then proceed to install the runtime environment and store app
Select the APPX1 folder and copy it to the Desktop, open it and select "APPX.ps1",and choose "Run with powershell", once done press "enter" reboot the system, go back to where you were and do the same with "AppxBundle.ps1"
Then Select "Microsoft.windowsStore.appxbundle" and install it (this will install a chinese version of the Microsoft Store (better than nothing I guess? Maybe someone can provide and english version?)
Finally install the following files from the root of your recovery disk:
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
7. Now all we need is a few tweaks to remove usability quirks and then your device will work like a shine :
7.1. You might have noticed than when you boot your device you get a message telling you that the licence is about to expire and that you also get a paging file error popping up at every login, this kinda ruins the experience, so we're gonna get rid of those.
- To remove the licensing popup first it go to " C:\Windows\System32" and take ownership of "LicensingUI.exe", then rename it to "LicensingUI-old.exe"
- To remove the paging file popup just manually set the page cache to 16 MB min and 512 MB max.
(Thanks to betanu701 for indicating us these tricks)
7.2. We're also gonna get totally rid of the Chinese language pack to favor any language you might want, this will also change the Store language to whatever language pack you put in.
- Go to Settings>Time & language>Region & language, and then set the whatever language pack you want as the default and remove the Chinese one (that's of course if you don't speak Chinese ^^)
(Thanks to ShotSkydiver for this trick)
7.3. We'll also make the camera work simply by applying the "Camera_fix.reg" registry entry as admin.
Your device is now ready to use.
Bonus: You can download and install the following apps from our fellow community member _CNR_, you'll get a bunch of stock apps that'll work for this build like mail, maps, solitaire...etc and Office 2013, here's the link : https://mega.nz/#F!ivwlHKaZ!hFwEHZnyw_nNTe4b3TN4wA
Quirks: at the moment I am getting a paging file error at every login along with an expired version warning, if anyone knows how to get rid of those two things, that'd be very helpful, I'd update the tutorial and mention your help in here of course...
(Edit: the quirks have been ironed out thanks to fellow community members)
I think this is only the beginning, we can probably improve this, first of all, we need an english store app (done), we'll also need to get rid of the error and warnings at every bootup(done), then we'll need to compile some apps and update existing ones and then list them, I hope the community on this forum will be helpful for these tasks :angel: For the time being enjoy what you get
Will this work in Asus winRT?
Enviado desde mi G8441 mediante Tapatalk
notass said:
Will this work in Asus winRT?
Enviado desde mi G8441 mediante Tapatalk
Click to expand...
Click to collapse
No, there are two images available, one made for the Surface 1 and one for the Surface 2, maybe it could work if you make a custom image from the leaked build but certainly not that way...
Hey !
I do have a problem with the "bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on" step... it don't work for me I don't understand why..
Are there any difference in the procedure for the Surface RT, other then using the corresponding W10 image?
Kiba85 said:
Are there any difference in the procedure for the Surface RT, other then using the corresponding W10 image?
Click to expand...
Click to collapse
No difference, if you try, tell me if you can install the secure boot patch and if the command "bcdedit ....." works for you. Because i'm stuck at this step
First off, thanks for the guide; it worked perfectly for my Surface 2! Also, I stumbled across a simple way to get the Store to display in English rather than Chinese: just go into Settings, then Time & language, then Region & language, and then set the English language pack as the default (optionally you can also remove the Chinese language pack as well). From there, open the Store, and it'll be in English!
AlGaib said:
Once this is done extract "SecureBootPatch.zip" and open the "SecureBootPatch" folder to run "InstallPolicy.cmd" as admin and then reboot the device once again (l If the secure boot debug policy interface appears after restarting, it means normal. Select accept and install to install)
Open a command prompt as admin and enter the following command to enable test mode :
- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
Now we can start serious business and install Windows 10 on the device, to do so, we'll start by rebooting the device in recovery mode (Check the lower right corner to indicate that secureboot is not configured correctly and it will succeed)
Click to expand...
Click to collapse
I would like to give a little warning to people following this guide - don't try to see what happens if you flash the Win10 WIM without having secure boot disabled. I just did that, and my Surface 2 is now bricked. If you want to be super sure that SecureBoot is off, run this cmdlet in PowerShell: Confirm-SecureBootUEFI
If it returns True, SecureBoot is still enabled.
I have an official Windows RT 8.1 recovery stick from Microsoft (but I also tried to make my own stick from the provided ZIP), but when I try to boot into Recovery (Volume Down + Power), I get the following error:
"A required device isn't connected or can't be accessed.
Error code: 0xc000000f"
When I just turn on the Surface, the boot fails, because the Windows 10 installation I flashed fails the SecureBoot test:
"The digital signature for this file couldn't be verified.
File:\Windows\system32\winload.efi
Error code: 0xc0000428"
Bloody hell, I was looking forward to having a more functional Surface and I ended up with a bricked one. Not sure what else can be done, when it refuses to boot even from official recovery stick :crying:
AlGaib said:
Following the recent release of a Windows 10 ARM32 install tutorial in chinese, I've used google translate to follow the procedure and then refined it, here is my tutorial for the Surface 2...
Download: https://yadi.sk/d/mnCUeGKWm1XTXA
Requires:
- The files available in the Yandex Repo
- A recovery USB Disk for Surface 2: Surface2_BMR_20.2.19.0.zip (https://support.microsoft.com/en-hk/help/4023512/surface-creating-and-using-a-usb-recovery-drive)
- A keyboard
Copy the following files from the yandex repo to the root directory of your recovery disk:
- Disabling_UAC.reg
- SecureBootPatch.zip (extract it)
- APPX1.rar (extract it)
- surface2_win10_zh_cn_new.wim
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
Boot into Recovery mode (insert the recovery disk, hold the "vol dow" button then press the "power" button and release the "vol down" button when the surface logo appears)
Open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\sources\install.wim /applydir:c: /index:1
Reboot the device and Disable UAC, then run "Disabling_UAC.reg" as admin and reboot the device once again
Once the device has rebooted open regedit and go to "HKEY_LOCAL_MACHINE\BCD00000000" select "BCD00000000", click on file and select "unload hive"
Once this is done extract "SecureBootPatch.zip" and open the "SecureBootPatch" folder to run "InstallPolicy.cmd" as admin and then reboot the device once again (l If the secure boot debug policy interface appears after restarting, it means normal. Select accept and install to install)
Open a command prompt as admin and enter the following command to enable test mode :
- bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
Now we can start serious business and install Windows 10 on the device, to do so, we'll start by rebooting the device in recovery mode (Check the lower right corner to indicate that secureboot is not configured correctly and it will succeed)
Once in recovery mode open a command prompt and type the following commands:
- diskpart
- list disk
- sel disk 0
- list part
- sel part 4
- for quick fs = ntfs override
- exit
- dism /apply-image /imagefile:d:\surface2_win10_zh_cn_new.wim /applydir:c: /index:1
Plugin your keyboard and reboot the device, you should get an error message related to the boot configuration, at this moment press shift+f10 and open regedit
Go to the following registry entry: HKEY_Local machine/SYSTEM/Setup/Status/ChildCompletion and then select the "setup.exe" entry, modify it to "3", exit regedit and commandline and click "Ok" on the error dialog box, the device should reboot(don't reboot the device in any other way), and configure correctly now
Configure the system the way you want it
Once on the desktop open a powershell command prompt and type in the following commands:
- slmgr.vbs /upk
- slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
- slmgr /skms kms.03k.org
- slmgr /ato
- slmgr /skms zhang.yt
Your device is now activated
We must then proceed to install the runtime environment and store app
Select the APPX1 folder and copy it to the Desktop, open it and select "APPX.ps1",and choose "Run with powershell", once done press "enter" reboot the system, go back to where you were and do the same with "AppxBundle.ps1"
Then Select "Microsoft.windowsStore.appxbundle" and install it (this will install a chinese version of the Microsoft Store (better than nothing I guess? Mybae someone can provide and english version?)
Finally install the following files from the root of your recovery disk:
- Microsoft.NET.Native.Framework.1.1.appx
- Microsoft.NET.Native.Runtime.1.1.appx
Your device is now ready to use.
Quirks : at the moment I getting a paging file error at every login along with an expired version warning, if anyone knows how to get rid of those two things, that'd be very helpful, I'd update the tutorial and mention your help in here of course...
I think this is only the beginning, we can probably improve this, first of all, we need an english store app, we'll also need to get rid of the error and warnings at every bootup, then we'll need to compile some apps and update existing ones and then list them, I hope the community on this forum will be helpful for these tasks :angel: For the time being enjoy what you get
Click to expand...
Click to collapse
To get the Store in english: Start > Settings > Language > Region & Language > Remove chinese
To get rid of the popup (old Windows version): C:\Windows\System32\LogonUI.exe > Right Click > Properties > Security > Advanced > Owner...Change > Add your username > Check Names. Close all popups and rename the file to whatever you want
Do i have to Downgrade to 8.0?
I have a problem. I cant disable Secure Boot. Therefore this command doesn't work:
bcdedit /set {default} testsigning on && bcdedit /set {bootmgr} testsigning on
I already launched SecureBootPatch 100 times. I get the screen on boot where I need to press Agree.
I completely restored with USB recovery Windows 8 RT. Non success
this doesn't change anything. Secureboot stays on.
Avonlady said:
I would like to give a little warning to people following this guide - don't try to see what happens if you flash the Win10 WIM without having secure boot disabled. I just did that, and my Surface 2 is now bricked. If you want to be super sure that SecureBoot is off, run this cmdlet in PowerShell: Confirm-SecureBootUEFI
If it returns True, SecureBoot is still enabled.
I have an official Windows RT 8.1 recovery stick from Microsoft (but I also tried to make my own stick from the provided ZIP), but when I try to boot into Recovery (Volume Down + Power), I get the following error:
"A required device isn't connected or can't be accessed.
Error code: 0xc000000f"
When I just turn on the Surface, the boot fails, because the Windows 10 installation I flashed fails the SecureBoot test:
"The digital signature for this file couldn't be verified.
File:\Windows\system32\winload.efi
Error code: 0xc0000428"
Bloody hell, I was looking forward to having a more functional Surface and I ended up with a bricked one. Not sure what else can be done, when it refuses to boot even from official recovery stick :crying:
Click to expand...
Click to collapse
Hmmm... are the flash drives formatted to Fat32? I don’t really understand how applying an image could cause this much damage...
Do you get any options when you try to boot into 10? If you can find a way to get to the command line, you can restore a Windows RT image from the restore disk
Evandarkfire said:
I don’t really understand how applying an image could cause this much damage...
Click to expand...
Click to collapse
It's quite simple, really. The sole purpose of SecureBoot is to prevent booting of non-signed operating systems. Like this leaked Windows 10. And since I removed the recovery partition (containing command prompt, etc.), the device is now toast. And yes, the recovery sticks are FAT32.
Avonlady said:
It's quite simple, really. The sole purpose of SecureBoot is to prevent booting of non-signed operating systems. Like this leaked Windows 10. And since I removed the recovery partition (containing command prompt, etc.), the device is now toast. And yes, the recovery sticks are FAT32.
Click to expand...
Click to collapse
Are you sure you booted from usb stick? You should still be able to boot from usb. I broke my efs partition, but could still boot from usb stick and recover everything.
I have to ask and I'm sorry for sounding like a noob..... but will this tutorial work for a Microsoft surface 2 running 8.1rt? I saw theres another post that says windows rt but I'm confused...... also when one of the requirements is a keyboard does that mean a USB keyboard or can the type keyboard work?
Fix quirks
Quirks : at the moment I getting a paging file error at every login along with an expired version warning, if anyone knows how to get rid of those two things, that'd be very helpful, I'd update the tutorial and mention your help in here of course...
Click to expand...
Click to collapse
To solve the 2 quirks. For the page caching. Manually set the page cache to min 16 MB and max 512 MB.
For the Build is about the expire. Go to C:\Windows\System32. Find the file LicensingUI.exe. Take complete ownership. Then rename it to LicensingUI-old.exe (or anything).
That will prevent the popups from showing up
Anybody have a working adblocker for the included version of Edge? Also does anybody where to get one of the old UWP arm32 versions of Kodi? They've all been removed from the official servers. Other than that it's amazing, so much better than 8.1!
Avonlady said:
I would like to give a little warning to people following this guide - don't try to see what happens if you flash the Win10 WIM without having secure boot disabled. I just did that, and my Surface 2 is now bricked. If you want to be super sure that SecureBoot is off, run this cmdlet in PowerShell: Confirm-SecureBootUEFI
If it returns True, SecureBoot is still enabled.
I have an official Windows RT 8.1 recovery stick from Microsoft (but I also tried to make my own stick from the provided ZIP), but when I try to boot into Recovery (Volume Down + Power), I get the following error:
"A required device isn't connected or can't be accessed.
Error code: 0xc000000f"
When I just turn on the Surface, the boot fails, because the Windows 10 installation I flashed fails the SecureBoot test:
"The digital signature for this file couldn't be verified.
File:\Windows\system32\winload.efi
Error code: 0xc0000428"
Bloody hell, I was looking forward to having a more functional Surface and I ended up with a bricked one. Not sure what else can be done, when it refuses to boot even from official recovery stick :crying:
Click to expand...
Click to collapse
When I first attempted to flash win10 on my device I did not follow completely the chinese tutorial and therefore I had not disabled secureboot, the Tablet wouldn't boot but I could easily just reflash win8.1 from a recovery drive, your issue sure sounds weird my friend... I'm sadly not knowledgeable enough to help you solve this
Cnnrduncan said:
Anybody have a working adblocker for the included version of Edge? Also does anybody where to get one of the old UWP arm32 versions of Kodi? They've all been removed from the official servers. Other than that it's amazing, so much better than 8.1!
Click to expand...
Click to collapse
I'd love to find a working adblocker too, I really don't understand why ublock won't work, this kindof thing should be platform agnostic, how weird... Also we need to start a thread with a collection of usable software...
Edit: I've updated the tutorial and thanked the users who indicated us how to iron the quirks out, Win10 ARM32 bits on the surface 2 is now as usable as it can get, we just need to make a collection of useful apps and list them (find some and compile others) and everything will be as great as it can be...
Will this work if my surface 2 is running 8.1rt?
---------- Post added at 03:00 AM ---------- Previous post was at 02:57 AM ----------
AlGaib said:
When I first attempted to flash win10 on my device I did not follow completely the chinese tutorial and therefore I had not disabled secureboot, the Tablet wouldn't boot but I could easily just reflash win8.1 from a recovery drive, your issue sure sounds weird my friend... I'm sadly not knowledgeable enough to help you solve this
I'd love to find a working adblocker too, I really don't understand why ublock won't work, this kindof thing should be platform agnostic, how weird... Also we need to start a thread with a collection of usable software...
Edit: I've updated the tutorial and thanked the users who indicated us how to iron the quirks out, Win10 ARM32 bits on the surface 2 is now as usable as it can get, we just need to make a collection of useful apps and list them (find some and compile others) and everything will be as great as it can be...
Click to expand...
Click to collapse
Would there. E any possible way of making a video tutorial????
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
AlGaib said:
When I first attempted to flash win10 on my device I did not follow completely the chinese tutorial and therefore I had not disabled secureboot, the Tablet wouldn't boot but I could easily just reflash win8.1 from a recovery drive, your issue sure sounds weird my friend... I'm sadly not knowledgeable enough to help you solve this
I'd love to find a working adblocker too, I really don't understand why ublock won't work, this kindof thing should be platform agnostic, how weird... Also we need to start a thread with a collection of usable software...
Edit: I've updated the tutorial and thanked the users who indicated us how to iron the quirks out, Win10 ARM32 bits on the surface 2 is now as usable as it can get, we just need to make a collection of useful apps and list them (find some and compile others) and everything will be as great as it can be...
Click to expand...
Click to collapse
Would there. E any possible way of making a video tutorial????
trollingwhovian said:
Will this work if my surface 2 is running 8.1rt?
---------- Post added at 03:00 AM ---------- Previous post was at 02:57 AM ----------
Would there. E any possible way of making a video tutorial????
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
Would there. E any possible way of making a video tutorial????
Click to expand...
Click to collapse
I don't have time or the ressources to do that, sorry, also I don't wanna redo the whole thing again on my device just to make a video tutorial, the text one is good enough...

Noob Bootloader Unlock Guide: Answers to several questions and solutions to problems.

***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
Saved
Update:
How to fix SafetyNet failure:
Get Root
-Follow this link: https://forum.xda-developers.com/oneplus-7t/how-to/magisk-auto-root-tool-oneplus-7t-pro-t4079355#post82221323
This is hands down the easiest root method I have ever seen for any device. HUGE shoutout to @daxiaamu and @mauronofrio for this!
Install Magisk Manager
On Your phone go to https://github.com/topjohnwu/Magisk/releases/
and download the latest version of Magisk Manager.
Allow unknown sources> install
Update Magisk
Once in Magisk Manager it will prompt you to install some updates for our phone. Install them and let it reboot.
Install Magisk Hide
Open Magisk>Three lines in top left corner>Downloads>MagiskHide Prop Config>download>install
Test
Once your phone has rebooted open Magisk>SafetyNet Check Status>Prosper!
Thank you to the Magisk team for making this hands down the easiest experience I have ever seen on Android and to @daxiaamu for making a truly one-click install that works flawlessly!
This should be pinned, but I have ctsProfile: false.
Is that expected?
lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
lucfig said:
This should be pinned, but I have ctsProfile: false.
Is that expected?
Click to expand...
Click to collapse
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good
C4sp3R911 said:
Thank you, it took a while to write was a little discouraged with the lack of response lol. To fix cts error:
Open Magisk>settings>turn off magisk hide
Magisk>Downloads>MagiskHide Props Config> Download and reboot
Magisk>Settings>Turn on MagiskHide
Test again should be good
Click to expand...
Click to collapse
Hope it gets more visibility, is the most detailed and easy to follow instructions.
I figured that out. Without riru or edxposed the Magisk hide works great.
otto888 said:
If you have the bootloader unlocked, yes. Magisk won't be able to hide the lock/root status from SafetyNet once Google fully rolls out their updates to SafetyNet/Play Services.
https://twitter.com/topjohnwu/status/1251712525843918853
Signing ROMs with custom keys and relocking may be a possibility, but I haven't tested anything on the 7T, and I'm staying locked until official support ends since the days of passing SafetyNet with root/unlocked bootloaders appears to be over.
Click to expand...
Click to collapse
We were able to fix it through MagiskHide. Both methods above worked.
Hey guys, I just received my OP7T today (upgrading from the 5T), and I see that there's no official TWRP yet. I've been looking around to see if it's worth it to root the phone already.
Is the rooting already stable enough, or should I wait a couple more months for full modded roms to come out? 'cause I really enjoy having the root features that some apps offer, but I also definitely need MagiskHide to work so my bank app won't have any issues with the unlocked bootloader.
If the guide above is up to date and working like C4sp3R911 posted, I'd be down to try it today.
Could I still use the the following command if OEM Unlocking is grayed out in Settings? Thanks.
"fastboot flashing unlock"
or
"fastboot OEM unlock"
What?... You need to learn a bit more before messing with bootloader unlocking, fastboot flashing unlock is not a command and will do nothing... Check yourself before you wreck yourself as the saying goes,
If it's greyed out doesn't that mean the BL is already unlocked?
C4sp3R911 said:
***Warning: I am not responsible for bricked or broken devices, warranties, computers, etc. This is your phone and your free will to follow the below steps and you bare the full burden of any consequences.***
A note for the Moderators: I am aware that the information I am about to provide exists outside of this thread. The purpose of this is not for redundancy or to clutter the forum. I am making this thread because I had to go to SEVERAL different sources to find these solutions and pull pieces from each. Hopefully, this is comprehensive enough to help someone who may have been in the same boat I was in. This is truly Noob friendly and intended for someone just beginning in the Android community, because of this it is painfully detailed. Hopefully, you will allow it to stay up.
The purpose of this thread is to address several issues I ran into while attempting to unlock my bootloader as well as address questions I personally had that I couldn't find answers to by using myself as the test dummy. Those items are as follow:
1) ADB was not functioning properly with Windows 10.
2) My Windows 10 laptop could recognize my OneTouch 7t in ADB devices but could not recognize it in Fastboot. Windows 10 wouldn't let me install the drivers that come pre-loaded on the OnePlus 7t.
3) After Unlocking the bootloader I hit a "checking info" loop with Google.
4) Does unlocking a bootloader on the OnePlus 7t cause any Safety Net Issues?
5) What does a SafetyNet failure result in?
6) Will every app work with an unlocked bootloader?
Solutions and answers:
1) This is going to be a detailed process but in the end, you'll have universal ADB and fix your windows issues:
If you decide to unlock the bootloader IT WILL WIPE EVERYTHING. This includes photos, apps, music, etc. So start by doing a backup:
-Settings>search "switch">OnePlus Switch>Backup & Restore> New Backup
-Copy that backup folder to your computer by plugging the phone into the computer> settings>search "USB">USB preferences>select file transfer>On your computer open up HD1905>internal shared storage>copy the "opbackup" folder to your computer (this will take a while)
Now to get Developer options:
-On your phone>settings>about phone>Tap build number until it says you are a developer
-Settings>system>developer options>turn on USB debugging
Getting ADB set up on your computer:
-Download and install SDK Platform-Tools for Windows: https://developer.android.com/studio/releases/platform-tools
-on Windows>Open up Command Prompt (run>cmd>enter)>Type sysdm.cpl> hit enter
-Go to the advanced tab in the window that pops up> environment variables>path>new>browse.
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok
Testing ADB:
-Open a new Comand Prompt in Admin mode. To do this Open run type "cmd" and then hit Ctl+Shift+Enter and click ok to the pop-up
-Plug your phone into the computer
-In Command Prompt type "adb devices" and hit enter
-You should now see your phone ID
-Type "adb reboot bootloader" and hit enter
-Your phone will reboot into bootloader
-Type "fastboot devices" and hit enter
-If your ID does not show up go to step 2 without changing anything (ie. stay in Command Prompt with the phone plugged in at the bootloader menu)
2)-This step fixes the driver issue that likely causes problem #1.
Get the newest Android drivers:
-Download and install Android Studio: https://developer.android.com/studio
-Launch Android Studio
-Configure>SDK Manager>SDK Tools>Google USB Driver>Apply>Ok
-At the top, it will say SDK path I highly suggest you copy that or write it down you will need it soon.
-Click Finish and close Android Studio
Installed drivers for fastboot:
-Open any folder and then select "view" at the top of the window and check the box that says hidden files then close the window.
-windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>browse>go to the folder location>next>finish
If that doesn't work and you get "Windows was unable to install driver" error do the following:
-click search for updated drivers on windows update>a new window will come up> Update and restart your computer
-Once back on and updated>windows key+x>device manager>right click on the phone with the orange exclamation point>update drivers>browse my computer>let me pick from a list>Android Bootloader interface>next>once finished, close the window.
To Test if this fixed the issue:
open an Admin Command Prompt and type "fastboot devices" and hit enter, you should now see your phone's ID.
WARNING: IF YOU DO THE NEXT STEP YOUR PHONE WILL BE FULLY WIPED. ENSURE YOU MADE A BACKUP!!!
Now to unlock the bootloader:
-In Admin Command prompt type "fastboot oem unlock" and hit enter
-On your phone use the volume keys to select "unlock the bootloader" then use the power key to select it.
Congrats your bootloader is now unlocked. Now for the problems you may face once it's back on
3) If you hit the "checking info" Google loop follow these steps:
-Go to Settings> Battery> Battery Saver>Turn off when fully charged>Select OFF,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Reset app preferences> reset Apps,
-Go Settings> Apps&notifications>See All ## Apps>3 Dot menu>Show System
-----Select Google play store >Storage & cache>Clear Storage
-----Press Back
-----Select Download manager> Storage & cache>Clear Storage
-----Press Back
-----Select Google play services> Storage & cache>Clear Storage>Clear All Data
-Go to Settings >Accounts> Google Account name/ Names> 3 Dot Menu> Remove ALL Accounts
-Restart device
-Connect to Wifi
-Go to Settings >Accounts>Add Account>Google
4) Yes, unlocking your bootloader on the OnePlus 7t results in a "CTS Profile Match=false" failure in SafetyNet
5)From what I can tell this SafetyNet failure doesn't really cause too many issues but time will tell and I will update this accordingly.
6) I tested the known problem children ie. Google pay, PokemonGo, and Snapchat. All were good. The only exception I ran into was Netflix. It will not work with an unlocked bootloader. There may be ways to resolve this but I haven't tried them yet as this is all without Root. I will update this post when I find solutions.
Again I know that most of this can be found but it took me a decent amount of digging. More importantly, a lot of the stuff was implied knowledge that many of us already have but a newcomer wouldn't. Hopefully, this is useful to the new and old alike feel free to ask questions below as I will be continuing to test stuff further.
Click to expand...
Click to collapse
Just bought the op7t pro and followed your guide step by step, but still fastboot devices does not show nothing to me
Tried in 2 different windows pc with same results, don't know how to do now
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
doncheadlesdriveway said:
Having trouble getting adb setup on my computer. Specifically here:
-Now find where you installed the SDK platform-tools and select the folder that says "platform-tools"
click ok>ok>ok-
In "Environment Variables" popup, I select "path" in the top field, then click "new". The next popup is "New User Variable". Here, I've clicked "Browse Directory", as well as "Browse File", but each time I click platform-tools and click OK, the OK in the "New User Variable" popup is greyed out. I've tried even clicking on a subfolder to platform-tools, just to see if that 2nd OK would be active, but it isn't. Any help is much appreciated.
Click to expand...
Click to collapse
Great. Thanks for the help.

[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D

[GUIDE] IMEI / Connection Repair on Asus Zenfone 2E ZE500CL Z00D
I am writing this guide because I recently recovered a bricked ZE500CL and after flashing around so many different files I lost my IMEI and connection abilities. After a little research and some thought I easily repaired my IMEI and restored my connection abilities. Just follow the steps below. I don't have this phone long and I am still learning so some of these steps might not be needed. Nevertheless it DOES work if you follow it properly.
What you will need:
1) Asus Flash Tool - https://drive.google.com/open?id=1n7tJr7lAlPnL8-nmK8f5kGmDHbRv5gxo
2) Asus Phone Drivers - https://drive.google.com/open?id=11XLRW5pEScYdBYwh0vDM-Wup9orGPWDf
3) Debug Service Firmware - https://drive.google.com/open?id=1ISofitM3yhYpu46JD0KWGLXybvtLQyAy
4) Intel Phone Tool - https://drive.google.com/open?id=1dQjjlHjWs8tDrfNU_ikgesKK2uKaTyXt
5) Intel Drivers - https://drive.google.com/open?id=1hE9j35VMOD5QGHjDy_aM2vVCs2PVOOm1
6) ADB / Fastboot Tools - https://drive.google.com/open?id=1nbAS8k4JMAXG8YH2qIFHpRjX60TTlYIt
7) IMEI Number - You should have this. If not generate one based off another ZenFone 2E Z00D's IMEI.
8) ZenFone Root Tool - https://drive.google.com/open?id=1NHf516Yex9KfsnufVNz0vkchJWCiMHo2
9) Root File Browser (ES File Explorer, Root Browser etc) - Get from the internet, place on your phone via MTP file transfer or push/install it in adb.
NOTE: If you choose the first way you will have to go into your debugging app in the applications. It will be the one with the magnifying glass and says Asus Log something on it. I no longer have the Service Firmware installed so I can't remember. You will find it though. Once you do go in and find the usb settings and just change modes and you will see the drivers install and device ASUS_Z00D or something similar should appear in device manager under devices. If it fails to load make sure you have the correct ASUS Drivers installed and if that doesn't work the last way is to select the ( ! )Driver and then manually install the USB MTP Device driver which will fix the issue.
10) Factory Folder Backup (This MIGHT not all be needed, still checking to make sure.. for now include it) - https://drive.google.com/open?id=1fvH0QdrzLFM34vsm2KNfQBU5fr8eSM14
First Step:
Download everything above and then install 6,2,5,4 (Install the drivers that come with Intel Tool before installing it. You should be prompted during installation) and then install 1.
Second Step:
Open Asus Flash Tool and make sure your phone is connected to the computer and you are in fastboot mode.
You can get there 2 ways. (1) Turn the phone off, hold Vol+, then push the power button, and when you feel it vibrate release the power button while holding Vol+. (2) Open command prompt and enter "adb reboot bootloader" (this is if you're adb is setup system wide, if not navigate to your SDK Tools folder and enter there).
Flash the Debug Service Firmware you downloaded. Check WIPE to wipe before flashing.
Once you see the phone boot up goto the next step.
Third Step:
Open Intel Phone Tool and follow this guide here to fix your IMEI! -
NOTE: You can skip the setprop commands he enters into adb shell in command prompt. This firmware already has the COM Port opened and USB Debugging enabled for you.
Fourth Step:
Now you will need to root your phone using the Root Tool I linked in the beginning (Do not worry about upgrading the SuperSU Binary.) Next you will need to install a root browser on your phone like ES File Browser, Root Browser etc. Something that allows access to root / hidden files. Navigate to /Factory and /Config and backup these two in their entirety to your MicroSD card or computer. Replace your factory with mine if it is empty and doesn't contain the files in the steps below. Now comes time to edit. Makes these changes to the files. (I am not 100% sure which all DO need to be made so I just modified most all of the values.)
These instructions are thanks to @BORETS24
I have changed them a tad as our handset differs from the one he wrote them for. I am still not entirely sure if everything needs to be copied/modified. Don't have a lot of spare time on this handset to figure out everything. I just know from testing this will get your phone functioning again.
Serial number, WI-MAC, BT-MAC repair instructions
(You will be replacing everything after step 5. Below explains what to edit.)
1. If you have an empty factory partition, use the archive, replace factory folder with archive version to root file system via file manager, ES File Explorer or others (root required and root browsing required of the application). Serial Number, WiFi MAC, BTMAC, colorID you may see on box from phone (or make up something for each value). .. you can generate the WiFi MAC based off these Unassigned? Assignments - 00:90:4C, 00:09:4C or just make one up based off a random Assignment from here - https://regauth.standards.ieee.org/standards-ra-web/pub/view.html#registries. For the Bluetooth - 22:22:AF or something you find on the previous site. You can check easier after you generate here - http://www.coffer.com/mac_find/. For color ID I left mine the same as what is in the factory.zip which is Silver.
2. Then open and edit factory/PhoneInfodisk/bt_addr.conf- this BT MAC, replace 00:00:00:00:00:00 numbers to your MAC.
3 Then open and edit factory/PhoneInfodisk/colorID- color code of your phone. For example silver is 6J.
4. Then open and edit factory/PhoneInfodisk/PhoneInfo_inf- 6F0000000 (yours will be 12 numbers) replace to your serial number, 1C002C... change to you BT-MAC, 00B72... change to your WiFi MAC, 6J change to your color code, RU... change to US,EU,CN,TW,RU (do not think this matters much). I changed mine to US I think.
5. Then open and edit factory/PhoneInfodisk/ssn- enter your serial number replacing 0000000. (12 numbers)
6. Then open and edit factory/wifi/mac.txt- enter your WiFi MAC replacing 00000.
Fifth Step:
Open Asus Flash Tools and flash desired build of RAW firmware over the Debug Service Firmware. I suggest the latest WW firmware which is ver .126. From here you can stay on this firmware after replacing the files below or surf around XDA and find out what customized ROMS are available for this phone. Personally I unlocked my Bootloader, flashed TWRP, flashed .126, flashed Resurrection Remix 5.8.4 ? on Nougat 7.1.1 and then flashed a SU. RR I wouldn't recommend as it is buggy and neither would I of MoKee as it is buggy as well. I am fixing the bugs in RR so it runs fine as I particularly like RR over others since it comes pre installed with a horde of features so you can customize your handset to your hearts desire.
1. Install a root File Browser and root your phone again.
2. Replace /config with your backed up /config.
3. Replace /factory with your backed up /factory.
4. Reboot.
Now check everything in settings and make sure it looks right. All should look A-OK except for serial #. I am still working on that and will edit this once I finish. Layout of our phone is different than the one I took files from. You might have to replace the file again if you flash certain custom ROM's. I flashed RR and didn't have to.
EDIT: After a few reboots I seem to lose my MAC's again and the serial (unknown) is replaced by Medfield1534DD97. Both WiFi and BlueTooth still work though. You just have the random default generated MAC's. I can live with that as long as it works. Though if anyone can shed some light on this issue or anything else I would be extremely grateful.
Enjoy Your Phone!
-------------
For the Asus Zenfone 2E ZE500CL Z00D I will be uploading in the near future somewhere an organized package compiled of all recoveries, roms custom + stock firmware, root, bootload unlockers, tools, apps and guides all together so you can easily download and skip the time consuming research I had to endure. It is around 10GB. I am officially done learning this phone now. It has been a long 3 days and now it is time to ship it out to a buyer. =]
XDA: noidodroid

Categories

Resources