Develop Bugs

Rooting indian htc magic airtel with spl 1.33.0010

Here's a friendly guide for all the people with 1.33.0010 SPL INDIAN VERSION AIRTEL and who would like to switch over to the 1.33.2010 Engineering SPL with Amon_RA's ROM. This has been tested on my Indian HTC Magic, but I do think it will work for other Magics with the same SPL. Remember, this is for 32A only.I tried different options given in xda forum but this method is full proof and now I have a working hero rom on my HTC MAGIC AIRTEL ASIA.
1. Download the latest Android SDK from http://developer.android.com/. Create a folder called "AndroidSDK" on your C drive and extract the contents of the zip file to the folder such that the folders called "tools", "usb_driver" and all are within the "AndroidSDK" folder.
2. On Windows XP : Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
3. Enable Debugging mode on the phone by going to
Menu > Settings > Applications > Developement > USB Debugging
4. Go to http://dl.google.com/android/android_usb_windows.zip and download the ADB drivers for windows.Not needed in HTC Sync 2.04 version as drivers are embedded in it.
5. Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software, select No, not this time and click Next.
Select Install from a list or specified location and click Next.
Select Search for the best driver in these locations. Browse and select the unzipped folder. Click Finish.
6. Go to "Run" in Start and type in "cmd". This is the standard procedure for invoking the Command Prompt. Remember this. Type "cd\" hit enter and then enter "cd AndroidSDK", hit enter. Then cd\tools ,hit enter The command prompt should look like :
C:\AndroidSDK\tools>
Now type in "adb devices" and hit enter. You should see something like this :
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
If you do, everything is great. Disconnect your device.
7. Now go to HTC's global site and download the latest version of HTC Sync(2.04 Version), unzip and install. When you connect your device now, HTC Sync should recognize your phone.
8. Now comes the Gold Card part. Go to http://forum.xda-developers.com/show...99&postcount=1 and follow the guide to create your Gold Card. The 2GB Sandisk one which comes in the box works just fine. If you don't have Android Market, don't fret. Forget about the Steps 3 & 4. Instead, connect your device with the card in it. Invoke command prompt and cd to "AndroidSDK" as told before. Type in "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid". You will get the CID. Follow the rest of the steps from the guide to create a Gold Card.
9. Time for action. Now you gotta get Engineering SPL 1.33.2010(find it on xda forum)- MD5 : 865020FBDFBD9C08950076A701A8A003 Flash this Rom in Hboot mode.
# Copy the required file zip file and rename it sappimg.zip (Do not add zip only rename as sappimg as it is already a zip file.) and copy it to the Goldcard.
# Boot your phone while holding the VOLUME-DOWN key.
# Press the ACTION KEY (=trackball) to start the update.
# Wait until the update completes and press the ACTION KEY (=trackball) to reboot your phone.
10. Now time to create a Nandroid Backup. Download • RAv1.2.1H – (Find it on xda forums) MD5Sum: E08D0A38BCCADAE416F644EE9D370D8B Put it in the "AndroidSDK\tools" folder. Switch off your phone. Hold the Back button and Switch it on. This takes you to the Fastboot mode. Standard procedure. Remember this. Connect the phone to the PC. Invoke the command prompt, cd to "AndroidSDK\tools" and type :
fastboot boot recovery-RAv1.2.1H.img
The recovery image will boot and you'll see the recovery screen in green colour. Wait for 2 minutes. Select the Nandroid Backup option and follow the on-screen instructions to create a backup. Reboot device. And copy over the "nandroid" folder on you sd card to a safe place.
11. Time to flash the HERO ROM Go to myhero-1.12 (find it on XDA forum) I tried flashing other roms but the screen jams at start so this particular rom is working well on my HTC AIRTEL ASIA Rename the file to "update.zip" and copy over to the sd card. Switch off your phone. Hold the Back button and Switch it on. This takes you to the Fastboot mode. Connect the phone to the PC. Invoke the command prompt, cd to "AndroidSDK\tools" and type :
fastboot boot recovery-RAv1.2.1H.img
The recovery image will boot and you'll see the recovery screen. Wait for 2 minutes. Select the Wipe Data option, and follow instructions to Wipe your present ROM. If you don't do this, your phone might not boot after flashing the ROM. Select the Apply sdcard:update.zip option. Follow onscreen instructions to flash the ROM. Reboot. All done. Welcome to Android.....
All credits go to XDA FORUM , and everybody else for their respective contributions.....
PS. Please do chip in with a Thanks if you found this guide helpful and any corrections are welcome.....
PPS. After you flash the ROM, if HTC Sync isn't working, use Google Sync, since the ROM is a Google ION based one.

[Root] Junsun Android 5.1 Rear View Mirror (A930/A931) Tutorial

Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
Root Pack: https://drive.google.com/open?id=11poc-Pr30J_aPmhVJktuqZx1H9fkX371
Firmware: https://drive.google.com/open?id=19zUz_piQ6aiO_uGCQTmKpC9ErAR5-4xZ
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!

great tutorial, really appreciate it

locale?
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again　
Do you need to change settings with build props etc?

otan032 said:
Thanks
seeing the A930P mt6735 root here, reboot after root language becomes us and timezone becomes China
I think I'm back to the default, but if you change the language, time zone to Japan and then restart it, it will go back to the default again
Do you need to change settings with build props etc?
Click to expand...
Click to collapse
Hmm.. could you give me some more information? Did you install Magisk or just use the temporary root with KingoRoot?
You could probably edit the build.prop to get the correct results by changing the "en" to "jp" for Japanese (or the whatever region). However, I'm not sure why yours is resetting to default after reboot? Mine always retains the settings after restarting. So if you could give me a little more information, I'll see if I can figure out what's the problem.

Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!

iamrance.asa said:
Hello all XDA Developers and site visitors,
I recently picked up a Junsun A931 Rear View Mirror on AliExpress and didn't see any forums on it. So, I decided to write my own about how I managed to gain root and install Magisk. Links to all the files will be included.
This works for Junsun's A930/A931 with Android 5.1. The process will probably work for other Rear view Mirrors with MTK chips, you will need to have access to the boot.img and scatter file for your device.
**Disclaimer: Proceed at your own risk! Although this worked for me without issues, there is always a chance of bricking your devices/making your device unusable. I am not responsible for your device(s).
Instructions:
1. Install MTK Drivers provided.
**I only have the ones for Windows. Mac/Linux, I couldn't find any MTK drivers for you.
**If you have trouble installing drivers, try turning off "signed drivers" in Windows Recovery.
2. Attach device to computer via USB cable.
3. If computer doesn't recognize device when it's fully booted:
-Go to "Set Up"
-Slide over to "Other" tab
-Scroll down to "Version"
-Click on "Version" until it brings up a menu (Same principle as Developer Mode, except it pop's up a menu)
-Click on "USB Host"
-Select "USB Device" (the one that has "adb" in the description)
**If this doesn't work, then try switching USB ports on your computer. It only ever works on my USB 3.0 ports.
4. Install Kingoroot on PC.
5. Launch Kingoroot and let it recognize your device, then click "Root."
** This is only a temporary root. It will reset every time you shutdown/restart. If that's what you want, stop here. Otherwise, continue on.
PERMANENT ROOT:
6. Open your choice of ADB on your PC. (I used Minimal ADB and Fastboot)
-Type "adb devices" to see if your devices is recognized and listed.
-Type "adb install [location of magisk.apk on computer]"
**replace "[location of magisk.apk on computer]" with location of magisk.apk (provided in RootPack.zip). This can be done by just dragging the file into adb or you can type the address from Windows Explorer.
-Type "adb push [location of boot.img for device] /sdcard/download"
**replace "[location of boot.img for device]" with location of boot.img for YOUR DEVICE. USING A BOOT.IMG FOR A DIFFERENT DEVICE WILL MOST LIKELY RESULT IN YOUR DEVICE BEING BRICKED!!! That being said, I have provided the software for Junsun A930/A931 for Android 5.1. If you have a different device, you will need the boot.img for it.
-Type "adb install [location of file explorer apk]" or install an file explorer from the Playstore, etc.
**replace "[location of file explorer apk]" with file explorer of your choice. I used ES Explorer.
7. Now open Magisk on the Rear View Mirror. (Make sure you're either connected to WiFi or Data)
**Be sure to grant it SuperUser Permission from Kingo SuperUser.
- Click "Install" next to "Magisk is not installed"
- Click "Install" on propt that pops up
- Choose "Select and patch a file" option.
- Scroll down and click on Es Explorer (or the file explorer you chose)
- Now go into the "download" folder and click the "boot.img"
- Click the option "File way"
**The "Normal Android Way" option kept failing for me.
- Let this complete.
8. Go back into ADB on the PC
- Type 'adb pull "sdcard/download/magisk_patched.img" C:/Downloads'
**You can replace "C:/Downloads" with whatever location you want to pull the file to on your computer.
9. Launch SP Flash Tool on your PC (provided in RootPack.zip)
-Load Scatter File by clicking the "Scatter-loading" button next to "Scatter-loading File" in the "Download" tab.
**This can be found in the firmware that I've provided, IF you have the Junsun A930/A931. If you have a different device, load the scatter file for it, instead.
-Now unclick all the boxes.
-Now click the box for "location" on the "boot" aisle.
-Select the "magisk_patched.img" that we just made from C:/Downloads or wherever you saved yours. Click "Open."
-It should have now have put the location of your "magisk_patched.img" file in the "location" box and the box next to the "boot" aisle should now be selected again (If not, make sure it is. Also, that it is the only one selected)
-Now click on the "Download" button (with the Green Arrow) at the top.
-Hold the home button the Rear View Mirror and click "Restart" (be sure to keep the mirror connect to the computer via USB)
-Now let the bar at the bottom finish.
-When it's done, there will be a pop-up that says "Download OK"
-Your device will restart
10. In your Mirror, launch Magisk Manager.
-Congratulations! The Magisk Installed option should now be green and you should have permaroot! Enjoy!
**You can now uninstall Kingo SuperUser.
Links:
**I am unable to add links due to how new my account is. For the files as of now, search "[Root] Junsun Android 5.1 Rear View Mirror A930/A931 " on YouTube and all the links are in the description. I will update here as soon as time allows.
A BIG THANK YOU TO THE DEVELOPERS AT MAGISK, KINGOROOT, MINIMAL ADB AND FASTBOOT, MTK DRIVERS, SP FLASH TOOL, XDA, AND EVERYONE ElSE WHO ATTRIBUTED TO THIS THROUGH DEVELOPMENT OF PROGRAMS USED! IF THIS WAS HELPFUL, BE SURE TO THANK ALL OF THEM!
Click to expand...
Click to collapse
Also, just adding more info to my post above.
I've tried contacting Junsun directly and thru AliExpress, they weren't helpful and just advised this feature isn't supported.
Apparently the USB port can be used for flashing firmware, but no other information.

rochbaz said:
Great write up! Thank you.
I ended up picking a diff model Junsun /w 2gb RAM and am having issues with the USB port:
aliexpress : /item/32844242296.html
It won't recognize any USB devices, so assuming the drivers are missing or it's disabled permanently somehow. This unit is not powered thru USB port, there are separate 12v +/- to hardwire in. I've tried multiple USB cables as well.
I tried USB sticks for storage, but my actual intent is to hook up a USB DAB+ antenna like I'm using on another vehicle's Android
HeadUnit:
aliexpress: item/33003465623.html?spm=a2g0s.9042311.0.0.5ad74c4dUcy6j9
I just need basic USB drivers and 5V output on the USB port, any ideas on how to get this working or add drivers onto the existing ROM etc.?
Thanks!
Click to expand...
Click to collapse
So MTK usually doesn't recognize in Windows the traditional way. You'll need a MTK program or the ADB/Fastboot. Since I don't have this model, I have no way to test it but I would look around the settings to see if there are some extra settings menus like developer mode. In the A930, they have extra menu by clicking the "version" and tapping it multiple times (not Android's but Junsun's custom one).
The driver's that I provide here: https://drive.google.com/file/d/11poc-Pr30J_aPmhVJktuqZx1H9fkX371/view?usp=drivesdk
Should work for your model since it uses the same processor. It should be able to recognize it on start but if it doesn't recognize it when it boots up then there's probably something in settings that will enable it to. It will probably be hidden since it's most likely only for developers who were working on the rom.

Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..

Monkandi said:
Hello I've just rooted my junsun A930 alps-1.6.91 with Dr. Fone root, it showed device as ASUS A10 but rooted no problem and so far seems permanent..
Click to expand...
Click to collapse
Thanks ! It works! I try many times with Kingoroot, but allways fail. My mirror is recognized as MediaTek FX. It is android 5 . Is there any options to upgrade it to newest Android version?

Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck

I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.

Monkandi said:
Hello I'm looking for upgrade or custom rom myself, if I find anything I will let you know, but we're already in the best place XDA for it to happen... Good luck
Click to expand...
Click to collapse
It depends on if anyone will spend the time to build an update rom or port for that device. If you send your device info, someone might end up working on it for you

nejcov said:
I ask on Junsun Official Store and their answer: "Our equipment cannot upgrade the system. The system is fixed in the device..." So , no solution from official.
Click to expand...
Click to collapse
I doubt it will ever have the support for the most current Android version. Most devices like this don't receive updates from official channels and the product isn't popular enough for most developers to have it.

updating fail due to power failed
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework

ajish110 said:
I am using 4G Junsun A930 model DVR (1GB RAM) I have lost my framework "alps.l1.mp3.v2.95_t98_v2.1.10" I try to flash "full_E08_KM_4G_9.35_WJ_EN_1.6.91" but failed. any possibility to flash my dvr or get "alps.l1.mp3.v2.95_t98_v2.1.10" framework
Click to expand...
Click to collapse
Contact them and ask for the firmware for your device. They will most likely send you it. Flash it instead.
Then follow the steps I outlined but using the firmware they sent you instead. That is if you want root.

I requested but they are not respond
---------- Post added at 10:22 AM ---------- Previous post was at 10:10 AM ----------
Orginal firmware ony we can flash in mtk mt6753 chipset? No other solution? I try miracle tool it shows mt 6753 then try to read boot8 after tool auto shutdown

Do you have a picture of the back of your device?
I don't know of any other tools/methods. There's some other programs for MTK development but they won't be much help in this case. You'll need to get the stock firmware back before anything. There's no programs to find suitable software nor is there a cross-reference. There is also no custom roms for these devices. Thus, why root and Magisk integration is such a positive.

drive.google.com/file/d/1Q9v9S_F3OXGp5h-ekh_yAdtJAk246ukY/view?usp=drivesdk
---------- Post added at 11:34 AM ---------- Previous post was at 11:33 AM ----------
drive.google.com/file/d/1Q0Jsw5QbNm2NRsE9vPAr1nXd8_7s_dja/view?usp=drivesdk

There was no access so I requested it

Ok now added

[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...

HD and WiFi Voice and Video Calling on XT2041-4 with Verizon

Prerequisites:
You must bootloader unlock your XT2041-4.
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
As far as I'm aware, this only applies to XT2041-4 on Verizon Wireless.
To be clear, the XT2041-4 is the "US Retail" or "Unlocked" (carrier unlocked) version of the Moto G Power. It's available from Best Buy, Amazon, etc. If you bought your Moto G Power from a Verizon store (or the Verizon website) you have the XT2041-7 and you should already have WiFi and HD Voice and Video calling. It's found here:
Settings -> Network & Internet -> Advanced Calling
The XT2041-4 does not have this menu available, so we're going to flash the Verizon ROM onto the Retail phone. Here we go.
Download and install the latest Motorola drivers:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Plug your phone into your PC with the factory USB cable and make sure you get all the necessary drivers installed. From your phone, select "Android System - Charging" in the notifications bar and change to "File Transfer". This should prompt Windows to install another driver.
Make sure you have the latest platform tools. This includes the latest adb.exe and fastboot.exe for use with fastbootd:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the latest Verizon image for the XT2041-7 from Lolinet:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Once downloaded, extract the zip file, so you're left with a file folder something like ths:
XT2041-7_SOFIA_VZW_10_[version]_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_CFC.xml
We'll call it your rom folder.
To make life easy, lets copy the required android utilities into this folder for flashing. Open up your platform-tools folder and copy the following to your rom folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
With your rom folder open, grab the entire folder location from the address bar and copy to your clipboard.
Click your start menu and type cmd, and open up Command Prompt.
Once you have the command prompt open, change directory to your rom folder:
Code:
cd [rom folder location]
All you have to do is type "cd", then space, then right click your mouse button to paste the folder location that you copied in the last step.
Hit enter to change directory.
Now your Command Prompt can call files from within your rom directory.
Now type:
Code:
adb devices
Watch your phone for the authorization dialog. Check the box and grant authorization. If it doesn't work, try unplugging your phone and plugging back in to get the drivers installed, then try again. The Command Prompt should return the serial number of your Moto G Power.
Now type:
Code:
adb reboot bootloader
And make sure your device reboots into bootloader mode.
Now type:
Code:
fastboot reboot fastboot
Make sure your device reboots into fastbootd. If this command doesn't work, you don't have the latest version of android platform tools.
Now type:
Code:
fastboot reboot bootloader
Your device should reboot back to bootloader mode. If everything is working so far, proceed to this thread and follow steps 4-7.
Moto G Power flashing guide
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9) Requirements: * Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and...
forum.xda-developers.com
Ignore steps 1-3 since you're using a different rom. Wiping userdata is optional - this will reset your phone to factory settings. Follow step 8 at your own risk - this resulted in a boot loop for me.
That's it! Once your phone boots up, you should have Advanced Calling in the Network & Internet settings menu. To gain root access, it seems as though Magisk doesn't work properly on the Moto G Power (someone correct me if I'm wrong). When attempting to patch the boot image, Magisk says "Downloading" then "Download Complete" instead of the typical "Flashing...". It still outputs some kind of image file, but flashing this file resulted in a bootloop for me. Maybe I'll try to patch the boot image from another device at some point, but for now I have WiFi Voice and Video calling on my (my wife's) XT2041-4. And she probably doesn't need root access anyway...

@clevertrevor777
Thank you for the guide. Is it possible to relock the bootloader afterwards or does this brick it?

Good question. Someone else would have to chime in on that. Why lock it anyway?

@nu_ninja
I got a Moto G Power from Google Fi and I was able to relock the bootloader right after following this guide. I did so before I booted it up initially. OEM Unlocking was still checked in developer options even after I locked the bootloader, so I can unlock it again later as needed.
Thank you Mr. Clever Trevor for figuring this out and sharing.

I have unlocked bootloader for my 2041-4. I have tried several VZW roms but it says boot failed each time. My question is when I type adb devices it says listing devices, but says "List of devices attached ___" and nothing happens with my phone. Thanks for the guide I hope I can get it working. Should I be using android 10 or 11 ROMs??

You really don't need to flash another rom just to enable volte and wifi calling, there just a few build.prop edits if you have root or this twrp flashabe zip: https://github.com/khrj/volte-fix
For manual method root or no root, open up /system/build.prop with root explorer or adb pull it to your pc add this snippet to the end and save it or adb push back making sure it has read/write permissions and voila volte and wifi calling will be enabled in the settings, works for custom roms as well.
Code:
# volte
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.data.iwlan.enable=true (disable if problems with wifi calls)
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Reboot the phone and check the settings or you can then dial *#*#4636#*#* and under phone information see if you have VOLTE provisioned.

How To Guide CPH2451 Rooters Please refrain to g96818 guide to Improve the Init_boot method.

Hey guys, i have tested the new method posted by g96818 and it works perfect.
Since he has more experience than me with OnePlus rooting I'll delete this post soon.
My fear is the future proofing of my method and i understand that his method is better in the case of future updates and less risky.

Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.

hitzzzzzzzz said:
Finally!. Excited to see the rooting movement beginning let's go. Would have tried but I've got CPH2447.
Click to expand...
Click to collapse
Hey man, but there is a full OTA for that, you just need to subtract the info you need from it.
Since i dont have that device, i dont want to tell you what to do.

Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451

scott.hart.bti said:
Nice. It'd be fantastic too if we could use this as a ongoing reference for future OTA's. Have someone drop by and post a patched init_boot image everytime a new OTA comes out and keep track of them for the CPH2451
Click to expand...
Click to collapse
Yeah that's true that would be nice.

Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device

scottlam1 said:
Adb connect works better than adb pair from wireless debugging adb connect then adb shell then run reboot bootloader command For me it would connect with pair but not recognize my device
Click to expand...
Click to collapse
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable

blasbenoit said:
I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me and other guys in this forum.
Important notes to consider: A big thanks to azsl1326 he got us the Patched Init_boot to make this possible.
-You need to unlock the bootloader of your device. This means you'll lose the data ect ect ect.
-People are losing Netflix access after this process, right now we haven't found a "cure" for this, but is pretty normal if you have root a Oneplus device before, when i found the fix i'll edit this right away.
-I'll write this for experts and newcomers a like just in case so they don't have to start asking for simple questions.
-After the root some people have the issue that they cant use security like passwords, fingerprint...ect ect. (as of now the only fix they have is to reset everything and doing the rooting again for 2+times). If i find the "cure" i'll let you guys know.
Spoiler: Issues connecting your device to the PC?
To some people the USB debugging is not working at all, because the phone turn it off after you try to use it or connect it to the PC.
I personally had this issue so i just workaround it. This is what i did:
1- Connect the OnePlus to the same network as your PC.
2- Turn On Wireless debugging on your OP11 and select Pair device with pairing code:
3- Then use this on your PC after you open CMD of course:
Then put the code you have.
The check with this command to see if it is connected:
Now that it is connected you can enter bootloader and connect it to your PC in that mode normally with:
OK now back to the deal:
1- Download the latest platform tools from here:
-Unzip it and put it in the desktop for easy access.
2-The bootloader
Spoiler: Unlock the Bootloader
Step 1 - Unlocking Bootloader:
1.A - Enable OEM Unlocking:
1. Open Settings Application -> About device -> Version -> Tap on Build Number 7 times
2. Open Settings Application -> Additional Settings -> Developer Options
3. Enable OEM Unlocking
4. Enable USB Debugging
1.B - Entering Bootloader
The bootloader must be unlocked in order to flash the recovery.
Ensure the device is connected to the computer via ADB by entering the following command
Code:
adb devices
The output should be something similar to this:
{
"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"
}
(note the device name on the left will not be the same)
Reboot into the bootloader by entering the following command:
Code:
adb reboot bootloader
1.C - Unlock
Once entered, enter the following command:
Code:
fastboot flashing unlock
WARNING: THIS WILL WIPE ALL DATA ON THE DEVICE
Use the volume keys to select unlocking, and then use the power button to confirm.
Once complete, enter the following command:
Code:
fastboot reboot
You will now have to go through the device setup.
Repeat steps 1.A and 1.B to enter back into the bootloader
3- Flashing the Init_Boot.img
In this case i'll provide the already patched Init_boot.img for A07!!! so you don't have to look for it, is attached to this thread.
Download the img and put it in the same folder as the platform tools for easy access.
Spoiler: Magisk Canary
After you enter the device.
1. Dowload the Magisk Canary version from this link:
2. Install it on you device.
Spoiler: Opening CMD (Command Prompt)
After you got everything in place open the platform folder and type CMD on the location box, then press Enter.
If that doesn't work, just open CMD and type:
CD and write the location of the platform folder to get it to work.
Now to the "flashing"
Enter the bootloader like before to start, now type this:
The above command should automatically flash the init_boot to both the slots. However, if you face any issues while executing that command, then you could also manually specify the slots while flashing. Like this:
And
4-Restart your phone and check the magisk canary app that everything is OK.
Spoiler: Bypassing Safetynet
This is optional; however, highly recommend
Note, due to the nature of Safetynet, this can change at anytime and may begin failing in the future.
A - Repackaging Magisk
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Hide The Magisk App"
4. Enter New Application Name
5. Click OK and wait
6. Uninstall original Magisk APK if it has persisted
B - Enable Zygisk & Deny List
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Enable "Zygisk"
4. Enable "Enforce Deny List"
C - Configure Deny List
it is recommended to add any application you would like to hide from Magisk here
1. Launch Magisk Manager
2. Tap Settings Icon (Top Right Corner)
3. Tap "Configure DenyList"
4. Tap the 3 dots in the top right and select "Show System Apps"
5. Select the following applications:
~ Android System
~ Google Play Store
~ Google Play Services
~ Google Services Framework
D - Delete App Data
1. Launch Settings Application
2. Select Apps
3. Select App Management
4. Clear data for the following apps:
~ Google Play Store
~ Google Play Services
~ Google Services Framework
5. Reboot the device
E - Flash Universal Safetynet Fix
1. Download the Universal Safetynet Fix
2. Launch Magisk
3. Select Modules
4. Select "Install From Storage"
5. Select Universal Safetynet Fix
6. Wait for Flashing to complete
7. Reboot
Download a safetynet check just to be sure.
And thats pretty much it, if you guys find some issues after the root, please post them here so i'll start adding more and more info about it for future references and fixes.
Click to expand...
Click to collapse
You are so helpful! This worked flawlessly!

ChrisFeiveel84 said:
adb and also the fastboot drivers installed? and USB debugging activated?
and only adb works over wifi , fastboot only with usb cable
Click to expand...
Click to collapse
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key

scottlam1 said:
Yeah fastboot still has to be hardwired I'm just going by my experience that pair function didn't work for me adb connect did wireless you still put in the IP and port but no pair key
Click to expand...
Click to collapse
i never use adb over wifi sorry

Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first

ChrisFeiveel84 said:
unrooting before the update is actually only needed if you do the update via incremental update (e.g. eu and india get full firmware packets) so you don't need to unroot first
Click to expand...
Click to collapse
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated

H4X0R46 said:
Mine is the USA model CPH 2451, I updated my phone to A.07 already by normal means, my bootloader is still locked, so I haven't even begun to mess with it YET. This might cause issues with my lock and fingerprint I'm assuming? Just wanna be sure I'm understanding this correctly. Thanks man for all your help! Much appreciated
Click to expand...
Click to collapse
I didn't have an issue with my lock screen and stuff. I also didn't do anything to the phone other than unlock bootloader and root. Once I did this my lock screen and fingerprint and stuff wasn't an issue at all. Maybe I got lucky.

H4X0R46 said:
Do you by chance have the stock unpatched init_boot.img? When you say that you have to redo the whole root process a couple of times to get screen lock working, uprooting would be flashing a stock init_boot yeah?
Click to expand...
Click to collapse
The password issue has nothing to do with rooting, it is caused by unlocking the bootloader. Before you do any rooting, first lock and unlock the bootloader 3 times. After the third time, you can set the password (or pin, or pattern/etc) and THEN do the actual rooting.

Do you have boot.img instead i rather have temp root

i accidentally pushed the patched init boot img to phone before updating, now i keep getting failed system update, any way to revert back to original A06 init_boot.img so i can take update and then come back and root

SappyHanger said:
Do you have boot.img instead i rather have temp root
Click to expand...
Click to collapse
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.

blasbenoit said:
Sorry m8, they haven't release the full IMG yet, just incremental, unless you are in (UPDATE A06), i can tell you where to get it for that one.
Click to expand...
Click to collapse
can you point me to the init boot image on A06, i accidentally pushed the patched a07 version to a06 w/o updating to a07

So I did the above and magisk turns into a green android icon and won't start. It did start before I flashed the init boot.... ?? Tried to re-install magisk, same thing. green icon.....
Do I need to sideload magisk? (adb sideload Magisk-v25.2.zip) ???