Database Users

Redmi 3 Pro Considerations - Flash global ROM with BOOTLOADER LOCKED

I've tried some things on my Xiaomi Redmi 3 Pro and I want to share them if helpful for someone.
I've done all this with Xiaomi.eu Rom and SMIUI
///// I'm not accountable for any problem on your phone, do it at your own risk! \\\\\​
1 - Button combinations (unplugged from pc):
vol+ & vol- & power = force shutdown if in fastboot or download mode, if powered-on it's a restart
vol- & power = from switched-off phone goes in fastboot (from there you can launch another combination: vol+&vol- while launche cmd: fastboot.exe reboot)
vol+ & power = preload\ bootload mode (the yellow screen where to choose recovery\ fastboot\ download mode)
2 - For any type of problem \brick \ bootloop be sure before about this:
A) if you run the phone in fastboot mode, check if you can see it in fastboot command line from pc (cmd: fastboot devices)
B) if you run the phone in download mode, check if you can see it from miflash
If these point are ok this means the pc is ready to see the phone if you softbrick it or it goes in bootloop.
You will be always able to run it in fastboot mode, then download mode, an flash any rom to the phone that works.
3 - What you need?
Install last version of MiFlash, here a guide: http://en.miui.com/thread-272376-1-1.html
Install MiPCSuite in english, here the link: http://pcsuite.mi.com/
If you have problems with ADB, install ADB drivers, here the link: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 or http://forum.xda-developers.com/showthread.php?t=2317790
If you have problems with hs-usb qdloader 9008 driver, try to install from here: http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Download and upack Android.Image.Kitchen for Windows, from here: https://mega.nz/#!McAj2SZT!E4XS7II27BjkjSHS2vcBnE6Tgvl8IZBhCD2wEKBchpA
Download TWRP 3.0.2.0 for MiFlash: https://mega.nz/#!cF4VVQiY!zrq2DTQRBX3UHRPOXN1dDNWiTn5tnoPxUfrHF_Rsnq4
Download ROM from different links:
http://en.miui.com/a-234.html (miui china stock, BL Locked)
https://www.androidfilehost.com/?w=files&flid=36337 (Xiaomi.eu with Gapps, no Bloatware, BL unlocked)
http://smiui.net/kitchen.php(Xiaomi.eu + other stuff)
Install Notepad++
4 - Prepare ROM:
As suggested by the user Jack0190 there are ROMS where is not needed to mod this files, like for "Xiaomi redmi3 pro locked multilanguage" roms.
Searching on web you can find them quickly, just be aware that there are some roms that have problems with SIM recognize. This comes from an old Thai \ Indian MIUI.
I've seen first this thread on en.miui, http://en.miui.com/thread-276565-1-1.html , where explains how to modify ROM to change the bootloader check. The guide explains very good how to modify the "boot.img" file of roms.
So just follow those steps.
I've seen that you can do it for both types of rom, for Recovery and MiFlash too.
For the recovery ROM, you have a file to open in 7Zip, copy the "boot.img" from it, modify it as explained in the guide, and re-copy in the zip file again.
While for the one for Miflash, it's easier; extract the rom, copy the "boot.img" file from \image folder, modify it with, and change it in the original folder. Then flash it with Miflash.
5 - Connect phone in Fastboot with pc:
One thing that always will save you is the ability to connect phone in fastboot mode.
Before start the phone in fastboot mode with cable unplugged (point 1).
Once you've installed Miflash, go on it's directory folder (C:\Program Files\Xiaomi\MiPhone\), and run cmd from there (shift+right mouse click).
Connect phone to pc.
Then run command "fastboot.exe devices" and if the result under the line on left is a code, the phone is recognized
6 - Force Download Mode from fastboot:
To force the phone to go in dowload mode, first run it in fastboot (point 5), check if it's recognized (point 2-A), then type but don't run command "fastboot.exe reboot".
Now push vol+ & vol- in the same time, and now run the command.
If it runs in the right mode, you can see it's connected by device manager under "Ports (COM &LPT)" section.
You will see "qdloader 9008 driver" with a COM port installed. The same port you will see in Miflash if you run it and push the "refresh button".
7 - Flash Job:
A) First you need to flash the recovery, TWRP, and to do this you should already have done this things:
Install Miflash, MiPcSuit
Your phone is right seen in fastboot and in Miflash in download mode.
You have downloaded the right versione of TWRP for MiFlash.
B) Flash TWRP with Miflash
Select in Miflash the button "Browse" and go to the folder "\Image"where you have extracted the TWRP zip
Click "Refresh"
Click "Flash"
Wait to complete (If it fails sending hello packets, it's because it's too much time the phone is in download mode, in this case, switch it off, e restart in Download mode and re-do all )
C) Copy modified ROM:
Now, I've done this step by OTG connection but there are more ways to do it:
Connec and mount an USB Drive in OTG
Push it by ADB
Copy it by SD card
If the old ROM still works, copy it in MTP connection
if none of this options is available, flash the Rom with Miflash, flash again TWRP recovery, run recovery, wipe cache and dalvik (factory reset option under "Wipe") and try to run system, it should run last system flashed.
D) Flash modified rom by recovery
E) Restart in system (It could take long time, even 10 minutes, so just wait for it)
Thanks to all users\ people helped me with different guides from XDA and other forums.
I' m sorry for no image, but it's not an official guide.
If something is wrong I'll change it asap, but don't blame me, these are just advices.
If it's not enough clear, search it on web.
If there are grammar errors, the Image verification confirms "I'm not a robot"
If you don't find the answer, then it's 42.

After mod, i can flash rom update from recovery?
Inviato dal mio GT-I9505 utilizzando Tapatalk

Just wanted to say thank you - This guide works. I tried it with a new redmi 3 pro with locked bootloader. You can skip step 4 if you want to, because there are some prepared images available (search for "xiaomi redmi3 pro locked multilanguage" and you will find them).
Also to note: The first boot of the new system took some long time (~ 10-minutes), so don't get frustrated. As long as there's the android logo with the three dots wandering around, everything should work fine.
- Jack

RuLe89 said:
After mod, i can flash rom update from recovery?
Inviato dal mio GT-I9505 utilizzando Tapatalk
Click to expand...
Click to collapse
not sure about this, I've flashed the last version available, so i don't have updates for now to test.
But i think that it could overwrite files modified.
This is what in some guides tells.

Jack0190 said:
Just wanted to say thank you - This guide works. I tried it with a new redmi 3 pro with locked bootloader. You can skip step 4 if you want to, because there are some prepared images available (search for "xiaomi redmi3 pro locked multilanguage" and you will find them).
Also to note: The first boot of the new system took some long time (~ 10-minutes), so don't get frustrated. As long as there's the android logo with the three dots wandering around, everything should work fine.
- Jack
Click to expand...
Click to collapse
Thanks to you, I've updated with what told. I've tried some of ROMs for locked bootloader, but was an Indian \ Thai version, and I had issues with SIM, no recognize.
That's why it was needed for me to use other rom for unlocked bootloader.

Hi, thanks for the guide. It seems like it'd be the only decent I could come across for my problem.
The only thing is that everytime I try to flash any ROM/image through MiFlash, I get the error:
Code:
Error loading type libary/DLL.(0x80029c4a: wait port ready to use <time in seconds>)
So far I haven't found anything or anyone that could help me with this. Can any of you help me out here? That'd be much appreciated.
Thanks~
----------------------------------
::Edit::
Alright, turns out I just had to do this:
1. Uninstall the Qualcomm drivers
2. Reboot Windows into "test mode"/Disabled driver signature enforcement
3. Reinstall the Qualcomm drivers
4. Flash device (phone in download mode)
5. Be very pacient. Waiting through the phone's boot phase
(took about 10 minutes; if it takes more than 15 minutes, then something is probably wrong. Try to enter download mode and flash it again.)
6. Redmi 3 working again
Okay, so, this worked for me, it doesn't mean it'll necessarily work for you!
This was done with a locked bootloader and MiFlash 2015.10.28.0

(Working Method, Latest MIUI 8) - Unlock bootloader + twrp recovery + install SuperSu

How to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission on the Latest MIUI 8 - V8.0.6.0.LHOMIDG. (as of 22-11-16)
Here you have the step by step procedures to successfully unlock your Redmi Note 3 SnapDragon global variant with latest global stable rom MIUI 8. Please follow the steps carefully.
The rom used for this procedure is the latest global stable fastboot rom MIUI V8.0.6.0.LHOMIDG.
This is the working guide for the Xiaomi redmi note 3 (SD) on latest MIUI 8.0.6.0 as on 22-11-2016. I did lots of experiments, bricked my device several times to find this working guide for latest rom, however you are free to link to this page for reference.
You dont need to apply for official unlocking and wait for a month or more to get the sms confirmation from xiaomi to officially unlock the bootloader, the problem with the official method is many users have reported that they did not receive the confirmation sms from xiaomi, even if they receive the confirmation sms the unlocking process stucks at some percentage and fails to unlock the bootloader. So for everyone here is the easy way to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission.
First of all take a backup of all important files from your phone to your PC before starting. Because all data will be formatted while flashing the rom.
I have simplified most of the procedures and complicated works for this guide. A good part of the credit goes to some other developers because their works were helpful to me for experimenting to find this working full unlocking guide for the latest miui rom for redmi note 3 (SD) as of 22-11-2016.
REQUIREMENTS:
Xiaomi Redmi Note 3 (SD) Mobile
Micro USB data cable (or) compatible usb cable
Desktop or Laptop (Widows based)
Download all the tools, rom and other files from this androidfilehost folder link and keep all files in one folder for easy access:
https://www.androidfilehost.com/?w=files&flid=137618​Files List:
1. AnF.zip
2. fastboot_edl.zip
3. Fastboot Rom: "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz"
4. MiFLash_v2016.08.30.0.zip
5. minimal_adb_fastboot_v1.4_setup _working.exe
6. MiPcSuiteSetup_v3.2.1.3111_2717.exe
7. Root Checker Basic v5.9.7.apk
8. SR1-SuperSU-v2.78-SR1-20160915123031.zip
9. twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip
10. ADBdriversetup.zip (alternate use, in case device specific drivers are not properly installed)​
***Carefully remove your sim card & sd card from mobile (if inserted) before you begin and do not connect to internet until all steps are completed, because the phone would automatically sync with Xiaomi servers at first boot and may cause problems.
Make sure your phone is charged 60% and above.
The complete video go through of step by step procedures in this guide is available in this YouTube video,
https://www.youtube.com/watch?v=rj4gVMk3y0o​
FOLLOW THE STEPS CAREFULLY, IF YOU FACE ANY TROUBLE, START OVER AGAIN FROM STEP 1, IF YOU FACE ANY OTHER ERROR OR BOOTLOOP OR STUCK IN LOGO LOOK AT THE TROUBLE SHOOT SECTION AT THE BOTTOM.
Step 1:
Enable Usb Debugging, if not done before:
Open Settings in your device"Redmi note 3 (SD)", scroll to bottom in settings and click on "About phone" and now tap on MIUI version 7 times, it will show a message like "You are now a developer" and Developer options will be revealed.
Next go back to Settings main screen and then -> Additional settings -> Developer options -> Enable Developer options, Enable OEM Unlock, Usb Debugging.
{
"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: After that when you connect your phone to the Pc to execute adb commands, a prompt may appear on your phone with computer's fingerprint key, you should confirm it when it appears. In case if you already done this for your computer with proper adb drivers installed, you don't need to bother about this.
Step 2:
DISABLE DRIVER SIGNATURE ENFORCEMENT IN YOUR PC:
You now have to disable driver signature enforcement in your PC, to do this you have to open the settings window by pressing the shortcuts"Windows button + i -> Update & Security -> Recovery -> Advanced startup -> Restart now. Now the system will logout and show Recovery options, from there select Troubleshoot -> Startup Settings in Advanced options -> Restart. Your system will now reboot and show the "Startup settings" screen, a list of options will be available, you have to choose option number 7 to disable driver signature enforcement. Then the system will boot into the OS with driver signature enforcement disabled. After that do not restart your pc until all the below steps are completed, in case if you restart your pc for any reason you need to redo this step again because system reboot might enable driver signature enforcement again. That's it. Refer this video if you need further guidance.
Step 3:
To install ADB, Fastboot and other drivers in your PC:
Install the " minimal_adb_fastboot_v1.4_setup _working " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiPcSuiteSetup_v3.2.1.3111_2717.exe " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiFLash_v2016.08.30.0.zip " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Step 4:
Extract AnF.zip file and execute the commands:
Now extract the "AnF.zip" file downloaded from the link I provided above. Connect your phone to Pc using the Usb cable. Open the extracted AnF folder and double click on the cmd.exe file, which will open a adb command window from there.
Execute the below command through adb command window to check and confirm the phone is connected via adb interface. If connected properly it should show device serial like "******** device"
adb devices​
Incase if your phone shows a prompt for computer's fingerprint key approval, allow it. Then execute the command again. You should see your phone serial number as shown in the image below, which means your phone is properly connected via adb. Incase if the device is not connect properly via adb, disable and enable USB debugging on your phone. If that also helping to install the phone's adb drivers, extract and run the"ADBdriversetup.zip" downloaded from the link I provided above to install the specific drivers for your phone.
Step 5:
Reboot the phone to EDL mode:
Now you have to reboot your phone to edl mode aka Emergency download mode. To do this execute the below command via adb window with phone still connected to Pc.
adb reboot edl​
Your phone will now reboot into blank screen or edl mode and new driver named "qshusb qloader 9008" will be installed in your Pc, now only red led notification light will be blinking on your phone. Once the driver is installed properly, the phone is now connected in edl mode. Now close the adb command window.
Step 6:
Setup MiFlash Tool & Flash the ROM:
Open the MiFlash tool (MiFLash_v2016.08.30.0.zip) application you installed earlier, click refresh button and your phone will be visible as port number (ex: COM10) in MiFlash tool. Exe file is in this path,"C:\Xiaomi\XiaoMiFlash"
Now extract the "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz" fastboot rom file downloaded from the link I provided above. In your MiFlash tool window, click the Browse button and locate the extracted fastboot rom folder. Then select "clean all" button at the bottom of MiFlash window. The flash tool is now configured. Now click the Flash button.
Wait for few minutes for the flashing process to complete, once the process is complete and MiFlash tool window will show task finished. But do not disconnect the phone.
Step 7:
Reboot to Fastboot mode & execute Fastboot commands:
Now while the phone is still connected to your pc, reboot your phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the boot screen and release, the phone will now enter into fastboot mode.
Now double click and open the cmd.exe file from AnF folder you extracted earlier to open the command window. Then execute the below command.
fastboot oem device-info​
This command will show you the current bootloader status. The bootloader status shows "Device Unlocked: False", execute the below command in command widow, it will Unlock the bootloader.
fastboot oem unlock-go​
Your device might restart now, if restarts press Volume down button and Power button simultaneously to reboot phone to fastboot mode again to check your bootloader status again by executing the below command. It should show "Device Unlocked: True" in the command window. Which means the device's bootloader is unlocked.
fastboot oem device-info​
Now to flash TWRP recovery and Supersu for root permissions, jump to step 8, or if your aim is to unlock the bootloader only, you may restart your phone and skip all below steps.
Step 8:
Flash TWRP:
Now restart phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the fastboot screen.
Extract the "twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip" file downloaded from the link I provided above to the AnF folder.
Then open the AnF folder, double click and open the cmd.exe file, paste the below command in the command window to flash twrp recovery.
fastboot flash recovery twrp-3.0.2-2-kenzo.img​
After flashing the recovery image reboot the phone to TWRP recovery by pressing Volume Up button and Power button simultaneously until you see the boot screen. It will boot the phone into TWRP recovery, on the front screen just swipe the slider to mount system as read only. That's it now to flash supersu proceed to step 9.
Step 9:
Flash SuperSu:
While the phone is in TWRP recovery connect the phone to Pc, it will be detected as mass storage device, just copy the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" file downloaded from the link I provided above to your phone's mass storage device.
On the twrp menu click on Install option and locate the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" to install via twrp, now swipe the slider to right to install supersu to have root access in your phone's OS and then wipe dalvik cache using the button below in twrp.
If twrp shows any read/write error while flashing supersu, on the twrp mainscreen choose mount option and click on system in the next menu, then go back to main screen and try again to install.
That's it, now supersu is installed, to check the root status follow to step 10.
Step 10:
Check root status:
After completing all the steps successfully, reboot the phone into the system normally and complete the initial setup without Sim card, the first boot may take a little more time to boot into OS, In case if the phone stuck in boot screen for very long(10+ mins), go to troubleshoot section at the bottom and start over the steps. Otherwise you are good to go.
Connect device to Pc after initial setup completes, now copy the "Root Checker.apk" file to your phone and install it, open the root checker app and click on verify root, you will be prompted by Supersu for root permission, allow it, your root access will be verified. Voila, you have successfully rooted, flashed twrp and installed supersu on your Redmi Note 3 with latest rom installed.
That's it. Now you are ready to rock.
KNOWN ISSUES:
No issues found so far, in case if you find any issues after successfully unlocking using the above method, kindly let me know.
After successfully unlocking your bootloader, incase if you update your rom via official updates, your will lose root access and twrp custom recovery and may end up with locked bootloader again, if you face this situation by some reason, you may start over and follow this guide from step 1 to revert back to unlocked bootloader. Do not update the rom and turn off automatic updates in settings as a precautionary measure.
Troubleshoot:
If your device gets bricked or Stuck in Boot logo, try this,
Reboot your phone into edl mode by following below step.
If you are stuck on bootscreen, you may not be able to enter into edl mode using the normal method above because of bootloop or Stuck in Boot logo, in that case try this method to enter into edl mode from fastboot, download "fastboot_edl.zip" file from the link I provided above, extract the zip file and open the extracted folder, connect the phone to your Pc in fastboot mode(vol down + power), double click and run this file "edl.cmd", the phone will automatically enter into edl mode if the phone's drivers and adb drivers are installed properly.​Now follow step 6 and follow on from this step.​
If QHUSB_BULK drivers are not properly installed while the phone in edl mode,
If QHUSB_BULK drivers are not installed while the phone in edl mode, your device may not be visible in MiFlash tool(ex:COM10) even after you click refresh button, in this case open the device manager in your Pc, the phone will be visible as QHUSB_BULK with some alert sign, right click on it and select Update driver software. Then click browse my computer and browse to the location of the driver files in path "C:\Program Files\Xiaomi\MiPhone\Qualcomm\Driver" and proceed and when prompted to Install this Driver Software anyway, allow it and complete the driver installation. Now open MiFash tool and click refresh button your device will be detected in MiFash tool, now you can flash the fastboot rom by following the steps above.​

Does this work for Kate version also? OP doesn't specify

Will I lose my warranty by using this method of bootloader unlock?

This method still works for Global Snapdragon phone. Finally got it last night after 2 days of torture (I didn't sleep).
The important part is firstly the image with the modified file you are going to flash to the phone. Here he is using v8.0.6.0 which is the newest (and now last) update for android 5.1 (which is needed, phone will not flash 6.0 without a proper Cache and data clear). I ended up using version 7.3.2.0 which is 1 patch before the version my phone came with (7.3.7.0). Then I replaced emmc_appsboot.mbn with the one from here then flashed the file in EDL mode.
After the flash is done is just as important I found. You place it in fastboot mode (power button + vol down) and run a script. I wasn't able to manually unlock the device via cmd line 'fastboot oem unlock-go'. Instead I found a script that worked from here called 'Root_Folder' (this site also has majority of the files needed). You use the script called 'Root' in the folder to finish the unlock. Notice there is a 'recovery.img' in the folder as well, I replaced it with ZCX TWRP.
Now run through the script after the flash in fastboot mode. Follow the instructions from script, sometimes you take cable out or force phone back into fastboot mode. The key goal here is to have the script boot into TWRP in the end. If this happens you can do all that's needed now.
Another thing I noticed was you have to give debug permission to computer your using and save permission. Debug mode/oem unlock - connect cable, on phone you should get a prompt to accept PC and save permission. If you don't get this prompt make sure you have ADB and Fastboot installed.
Important steps are:
1. Phone connect to computer via debug/oem mode.
2. Flash correct modified ROM with MiFlash in EDL mode.
3. Once flash is done hold power and volume down button for fastboot mode.
4. Run script to attempt to unlock bootloader and/or install TWRP.
MikeyLee said:
Does this work for Kate version also? OP doesn't specify
Click to expand...
Click to collapse
You would have to look it up for Kate specifically. If anything at all that changes it's the Image you use to flash the phone.
zeon321 said:
Will I lose my warranty by using this method of bootloader unlock?
Click to expand...
Click to collapse
Don't think so. You don't 'officially unlock it' and you can flash a stock image that relocks the phone automatically.

Thank you works 100% !!!! :laugh:

After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.

zeon321 said:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
Click to expand...
Click to collapse
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).

Narcle said:
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Click to expand...
Click to collapse
Thanks, I flashed old version of twrp and formatted the storage. Now phone is working fine.

Can i use this tuto on a Redmi note 4 MTK?

Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !!

Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !! @Sci Subi

Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html

W7nstroll said:
Can i use this tuto on a Redmi note 4 MTK?
Click to expand...
Click to collapse
This method is for Redmi Note 3 pro, (Kenzo) variant.

can i use it for global stable 8.2.3 ??

The heart of this - the unofficial bootloader unlock - are taken from: http://en.miui.com/thread-345728-1-1.html (It's generally polite to link your sources).
This _does_ work on `kate`. However, this is using a modified 'emmc_appsboot.mbn'. If you flash an original emmc_appsboot.mbn, you may well find your bootloader no longer unlocked and you needing to reflash your device back to stock.
Also, for those wanting to use it on kate (because Xiaomi seems singularly incompetent when it comes to supporting the official bootloader unlock for that devcie): your device will identify itself as a kenzo, so you may have trouble flashing things like the 'miuifirmware_x.zip' updates for kate. Also, those 'miuifirmware_x.zip' files often include the emmc_appsboot.mbn, so be careful.
On another note, if anyone has an actual infallible method to get an official bootloader unlock for the kate device, please let me know.

Can I use this method for 2GB / 16 GB version of Redmi Note 3 Pro (Snapdragon)?
Thanks

Works Thanks
Tested On 18/05/17
This method works But You are stuck on a older rom with no OTA/Later Updates. Method Does not work with MM Roms.(Maybe with different emmc_appsboot.mbn it would work.
Some Pointers
I was on MIUI8 before using this.
1. This downgrades your ROM from the latest ROM, therefore Points to follow.
2. Use This Method Instead Works with latest firmware as on date.

Works, Simply Nicely Perfectly Done, Just follow the steps things will never goes wrong. :highfive:

Sci Subi said:
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
Click to expand...
Click to collapse
hi my phone was on miui 8 marshmallow i used the above method nd flashed the rom ( rom is 5.1.1) which is given after that unlocked bootloader nd installed twrp also but now i downloaded a new rom nd i want to flash it i placed the rom in micro sd card nd wiped everything in phone nd flashed the rom with gapps now phone boots but its stuck at the boot logo of the rom i also tried many other roms of 7.1.1 but same is happening phone is not going ahead its stuck in the rom boot logo what should i do also when i flashed that given rom when i charge the phone the red light blinks which seems like edl light help me out of this !! thanks in advance !!

You have flashed a recovery rom and that's why you are in bootloop.
Try to flash in EDL mode a fastboot rom.
PS: Hope you haven't tried to downgrade already because you can loose IMEI and baseband.

Android 7.1.1 Doogee X5PRO

I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?

I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.

Do the camera and fingerprint work?

Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.

Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?

****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!

The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.

I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.

installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?

xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )

Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug​#b. Enable OEM unlock​
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:​type: adb reboot-bootloader ___ (Wait 1-3 second)​type: fastboot devices ___ (verify device is detected)​#b. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: yes​= unlocked: no​#c. unlock bootloader​type: fastboot oem unlock ___ and you get​-> start unlock flow​---> on screen appear:​vol UP=Yes; void warranty, clear ALL data​vol DWN=no; no unlock​Press Vol UP​#d. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: no​= unlocked: yes​#e. May be phone restart​
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt​as per normal way (You know this , after some trying...)​
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)​
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons​#b. choose recovery with Vol Up and confirm with Vol Down​
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.

Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo

xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.

when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file

I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file

xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?

The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.

I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...

As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?

Nokia 6.1 plus Stuck on TWRP Splash screen. PLEASE HELP!!

Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks

Now, dissemble the device and enter edl mode
Sent from my Nokia 6.1 using Tapatalk

MaxTurner771 said:
Hello everyone,
I have recently unlocked the bootloader on my Nokia 6.1 plus, and rooted it. I then went ahead and installed TWRP ( App install method - found in the twrp website ). However after I rebooted my phone has been stuck on the TWRP splash screen , I Tried going to download mode , and that just got me back to the twrp splash screen. I turned off the phone and powered it on again , same result . Whatever I do it just keeps going back to the TWRP splash screen .. What is even worse is that my device can not be recognized by my pc while stuck on the splash screen , thus I can not use ADB or Fastboot ...
I am feeling really hopeless and stuck , Help would be much appreciated!! Thanks
Click to expand...
Click to collapse
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.

CarbonGTR said:
You shouldn't have installed TWRP on a A/B device let alone install it via the app. It's okay, We're here to help.
If you have OSTLA in your PC, Just open it up and load all files and select to flash the stock ROM. Select Normal Download/Erase User Data options and if the option to Chech AP status is enabled, Disable it. Select on start or the option to flash stock ROM.
Power off your phone completely. If you can't, Then press the volume+ button and power button. Once the screen goes off, Immediately connect phone to PC.
Phone should now reboot into download mode and stock rom should start flashing. Then it's just a matter of waiting for it to flash and reboot.
Click to expand...
Click to collapse
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?

MaxTurner771 said:
I had a problem in that my device would never be recognized by my pc even when i finally manage to put in download mode, However after many days trying I was finally able to do it , and to use OSTL.... so thank you!!
I am wondering now how I will do the thing i wanted from the start which is to flash a kernel if i shouldn't use twrp?
Click to expand...
Click to collapse
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"

D-Mi said:
So to my understanding what you want to achieve is flash a custom kernel on stock rom. And after you messed up your stock recovery by installing twrp, if you have flashed stock rom using ostla then follow these steps.
First without tampering anything finish an ongoing/pending ota/sp update cause after you install custom kernel you phone won't be able to install OTAs. The last sp is of june so install that.
Now coming to installing the kernel-
*Place your twrp and kernel zip file into your adb folder*
1. Setup usb debugging and connect your device normally to your pc, check if the device is communicating with pc type in "adb devices" and allow on your phone for authorisation.
It should reply with your serial on cmd window.
2. Type in "adb reboot bootloader" that should put your device in download mode.
3. Type in "fastboot boot twrp.img" (replace twrp.img with whatever your twrp image file name is)
4. Go to advanced and select adb sideload, swipe to start.
5. Now move to your cmd window and type in "adb sideload kernel.zip" (replace kernel.zip with whatever your kernel zip file name is)
Wait for the process to finish
Now press home go to wipe>advanced wipe select dalvik cache and swipe to wipe
again press home and select reboot, select system
Now final important step
6. don't swipe, select "do not install twrp"
Click to expand...
Click to collapse
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated

MaxTurner771 said:
This might sound like a stupid question but I am a major newbie when it comes to this,
Right now i managed to compile a custom kernel and I have a boot image along with the kernel, so to get the kernel.zip do I just zip up all these files? also I read that I could simply flash the image by rebooting to my bootloader and then using " fastboot flash boot boot.img " would this work , and if so does this mean i don't need twrp...
Thanks again for the help , it is much appreciated
Click to expand...
Click to collapse
If you just want to flash your custom kernel there's no need to flash a boot.img if you've a running rom installed. You can flash the kernel.zip it via twrp or adb sideload via twrp.
Sorry for the late reply, if you have a bootloader-unlocked 6.1 Plus you should join Nokia 6.1 Plus community on telegram you'll get much faster response from the community regarding your device ?

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself