[25-08-2022] UMTv2/UMTPro UltimateMTK v5.1 - Xiaomi MiCloud/OTA Disable, Vivo & more

[fonelab1o1]

Wow, Really good update Thanks UMT Team.

[U.M.T]

Originally Posted by noor300

Enable/Disable BROM for Vivo MT6765 Devices
- Preloader Crashing for BROM does not work anymore in updated devices
- Use this option for MT6765 base devices to enter BROM mode
- After Enable BROM, you must use custom preloader for other operations
- Once finished, use Disable BROM to restore device back to normal condition
- You must use correct backup file made while Enable BROM


HAHAHAHH Oppo A54 android 11 and chip MT6765 But no enter brom mode teem plz chak and info send user .

i have 2 pice OPPO a54 but no enter brom mode only some models MT6765 chip ALL 6765 not working very bad

If you dont know difference betwen Oppo and Vivo then it is your problem.

Even if you are dumb, lets compare these
V I V 0 and O P P O, only last letter matches.

Br,
UMT

[U.M.T]

Originally Posted by noor300

HAHAHAHH Oppo A54 android 11 and chip MT6765 But no enter brom mode teem plz chak and info send user .

i have 2 pice OPPO a54 but no enter brom mode only some models MT6765 chip ALL 6765 not working very bad

If you dont know difference betwen Oppo and Vivo then it is your problem.

Even if you are dumb, lets compare these
V I V 0 and O P P O, only last letter matches.

Br,
UMT

[.::MAHABUB::.]

Originally Posted by noor300

Enable/Disable BROM for Vivo MT6765 Devices
- Preloader Crashing for BROM does not work anymore in updated devices
- Use this option for MT6765 base devices to enter BROM mode
- After Enable BROM, you must use custom preloader for other operations
- Once finished, use Disable BROM to restore device back to normal condition
- You must use correct backup file made while Enable BROM


HAHAHAHH Oppo A54 android 11 and chip MT6765 But no enter brom mode teem plz chak and info send user .

i have 2 pice OPPO a54 but no enter brom mode only some models MT6765 chip ALL 6765 not working very bad

use test point than works 100% tested by me.

[.::MAHABUB::.]

Originally Posted by noor300

Enable/Disable BROM for Vivo MT6765 Devices
- Preloader Crashing for BROM does not work anymore in updated devices
- Use this option for MT6765 base devices to enter BROM mode
- After Enable BROM, you must use custom preloader for other operations
- Once finished, use Disable BROM to restore device back to normal condition
- You must use correct backup file made while Enable BROM


HAHAHAHH Oppo A54 android 11 and chip MT6765 But no enter brom mode teem plz chak and info send user .

i have 2 pice OPPO a54 but no enter brom mode only some models MT6765 chip ALL 6765 not working very bad

its true but only vivo.

[naizersky]

Operation : MTK One Click
Hold VOL UP + DOWN and connect USB Cable.
Some phone may have different key combination for BROM mode.
Waiting for device in BROM mode...
Port: COM22 [MediaTek USB Port (COM22)]
Device Path: \\?\usb#vid_0e8d&pid_0003#5&b554af&0&2#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Chipset: 0x0766, [MT6765] [Helio P35/G35]
Hardware Info: 0x8A00, 0xCA00, 0x00
Config : [SecureBoot: True] [SLA: True] [DA Auth: True]
MEID: 3AF9E64036D0366DB77977222E6B32BD
Preparing device...
-- Success!
Preloader saved as : preloader_k62v1_64_bsp_220826_150615.bin
DA : MTK_AllInOne_DA.bin
Waiting for Phone in Flash Mode...
Connect Power Off phone within 30 secs...
Port : MediaTek USB Port (COM22)
Connected to BROM.
Sending Download Agent...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Connected to Download Agent..
Syncing with Target...
Reading Partition Table...
Storage : eMMC
Reading Information...
Manufacturer : Xiaomi
Market Name : Redmi 9A
Build Date : Thu Aug 5 22:53:29 CST 2021
Build Flavor : dandelion-user
Build Desc. : dandelion-user 10 QP1A.190711.020 V12.0.18.0.QCDINXM release-keys
Android Ver. : 10
Display ID : QP1A.190711.020
Patch Level : 2021-08-01
Platform : MT6765
Board : dandelion
Platform : mt6765
Userdata is ENCRYPTED
Disabling OTA...
- Success
Removing FindDevice...
- Find Device data not found.
- Failed!
Disconnect Battery/Cable and Power On Phone.
[UltimateMTK Ver. 5.1]

now system has been destroyed

[Y Michael]

Nice update keep it up UMT to the world

Sent from my CPH1727 using Tapatalk

[Y Michael]

Originally Posted by naizersky

Operation : MTK One Click
Hold VOL UP + DOWN and connect USB Cable.
Some phone may have different key combination for BROM mode.
Waiting for device in BROM mode...
Port: COM22 [MediaTek USB Port (COM22)]
Device Path: \\?\usb#vid_0e8d&pid_0003#5&b554af&0&2#{86e0d1e0-8089-11d0-9ce4-08003e301f73}
Chipset: 0x0766, [MT6765] [Helio P35/G35]
Hardware Info: 0x8A00, 0xCA00, 0x00
Config : [SecureBoot: True] [SLA: True] [DA Auth: True]
MEID: 3AF9E64036D0366DB77977222E6B32BD
Preparing device...
-- Success!
Preloader saved as : preloader_k62v1_64_bsp_220826_150615.bin
DA : MTK_AllInOne_DA.bin
Waiting for Phone in Flash Mode...
Connect Power Off phone within 30 secs...
Port : MediaTek USB Port (COM22)
Connected to BROM.
Sending Download Agent...
connect DA end stage: 2, enable DRAM in 1st DA: 0
Connected to Download Agent..
Syncing with Target...
Reading Partition Table...
Storage : eMMC
Reading Information...
Manufacturer : Xiaomi
Market Name : Redmi 9A
Build Date : Thu Aug 5 22:53:29 CST 2021
Build Flavor : dandelion-user
Build Desc. : dandelion-user 10 QP1A.190711.020 V12.0.18.0.QCDINXM release-keys
Android Ver. : 10
Display ID : QP1A.190711.020
Patch Level : 2021-08-01
Platform : MT6765
Board : dandelion
Platform : mt6765
Userdata is ENCRYPTED
Disabling OTA...
- Success
Removing FindDevice...
- Find Device data not found.
- Failed!
Disconnect Battery/Cable and Power On Phone.
[UltimateMTK Ver. 5.1]

now system has been destroyed

What did you mean by system has destroyed? Did the software remove the account or it kills the phone pls be detailed

Sent from my CPH1727 using Tapatalk

[naizersky]

try Disabling OTA Find Device on redmi 9a

[:Aishur:]

Originally Posted by Y Michael

What did you mean by system has destroyed? Did the software remove the account or it kills the phone pls be detailed

Sent from my CPH1727 using Tapatalk

this issue happens when the bootloader is not unlocked.
it is required as mentioned in post #1 to unlock the bootloader first.

[pcuse8]

Thank you for micloud

Envoyé de mon SM-A405FN en utilisant Tapatalk

[gsm-mobi]

Very good work UMT team

team plz add oppo imei repair thanks

[Aamir_Zia]

vivo s1


Operation : Enable BROM Mode (Vivo MT6765 Only)
Connection Mode : Preloader
Waiting for Phone in Flash Mode...
Connect Power Off phone within 30 secs...
Port : MediaTek PreLoader USB VCOM_V1632 (Android) (COM558)
Connect BROM failed: STATUS_SCATTER_HW_CHIP_ID_MISMATCH(-1073545201)
Disconnect cable and Power ON phone.
Please check if correct Platform/DA is selected
Disconnect Battery/Cable and Power On Phone.
[UltimateMTK Ver. 5.1]

[sultanovyashar]

Really good update . thanks UMT team

[sumit jagwani]

Originally Posted by Fast Unlocking

UMTv2 / UMT Pro
UltimateMTK v5.1






Supported functions:
- Read Info
- Reset FRP (For devices supporting this feature)
- Reset Locks (All Android Versions, Encrypted Userdata NOT Supported)
- Read Pattern (Android 5.x and earlier, Encrypted Userdata NOT Supported)
- Format FS
- Format FS (Advance)
- IMEI Repair in META / Boot Mode
- Backup NVRAM
- Restore NVRAM
- Reboot to META / FACTORY / FASTBOOT Mode
- Added Support for Helio CPU (MT6750, MT6755, MT6763, MT6739 etc)
- Disable Lock / Restore Lock for Encrypted Userdata
- Remove Lcoks for Encrypted Userdata for Vivo
- Factory Reset in META Mode (Vivo, Oppo and others)
- SafeFormat Option to let device format itself safely in recovery
- Added Support for Helio X20 (MT6797)
- Oppo/Realme Safe Factory Reset in META Mode
- Added Disable Auth to disable SLA/DAA
- Added Mi Account Reset
- Xiaomi IMEI Repair
- NVRAM/NVDATA Format
- META Reboot for SLA Enabled Devices
- MTK One Click Function Added
- Crash Preloader Added
- Added More Options in MTK One Click
- Added Bootloader Unlock / Relock
- Added RPMB Read/Write
- Added Vivo Security Repair
- Added Samsung Knox Guard (KG) Status Change
- Added Oppo ID Remove
- Added Huawei ID Remove
- Added Erase RPMB
- Added Partition Manager
- Vivo MT6765 Enable/Disable BROM - NEW!!!
- Xiaomi Disable OTA - NEW!!!
- Xiaomi Disable MiCloud - NEW!!!





MTK One Click
- No need to select any model.
- No need to select any DA/preloader.
- Simply tick required options and execute.


Supported SOCs for DAA/SLA Bypass:
- MT6261
- MT6572
- MT6580
- MT6582
- MT6735
- MT6737
- MT6739
- MT6753
- MT6755
- MT6757
- MT6761
- MT6763
- MT6765
- MT6768
- MT6771
- MT6779
- MT6785
- MT6795
- MT6797
- MT6799
- MT6873
- MT8127
- MT8163
- MT8173
- MT8695
- MT6885
- MT6595
- MT8167
- MT6592
- MT6833 (Dimensity 700 5G)
- MT6853 (Dimensity 720 5G)
- MT8590
- MT6758 (Helio P30)
- MT6781 (Helio G96)
- MT6877 (Dimensity 900)
- MT6893 (Dimensity 1200)




Disable OTA and Find Device (Xiaomi)
- It will disable OTA updates and Find Device also
- Bootloader should be already unlocked


Remove Orange State (Oppo)
- Removes Orange state warning on unlocked devices
- Supports most Oppo firmware


Enable/Disable BROM for Vivo MT6765 Devices
- Preloader Crashing for BROM does not work anymore in updated devices
- Use this option for MT6765 base devices to enter BROM mode
- After Enable BROM, you must use custom preloader for other operations
- Once finished, use Disable BROM to restore device back to normal condition
- You must use correct backup file made while Enable BROM


Improved Bootloader Unlock Function


Improved Read Device Information for Helio Devices




Thanks to:
- All users for their continuous support





MTK One Click supports most phones regardless of Brand and Model


Important
- Features introduced may work on other devices too, which are not litsed here.
- User needs to untick By Model checkbox to be able to select Platform manually.
- For manual work, just select Platform and DA.
- For new secured devices, use Disable Auth, and select Preloader.
- Rest operations will work same.


Note : Some features are device/OS specific and may not work on all devices.




WARNING :
ESN / MEID / IMEI REPAIR IS INTENDED TO REPAIR ESN / MEID / IMEI TO ORIGINAL ONE WRITTEN ON PHONE BACK LABEL / BOX. WE DO NOT ENDORSE OR ENCOURAGE ESN / MEID / IMEI CHANGING. ITS ILLEGAL. USER IS SOLE RESPONSIBLE FOR ANY ILLEGAL ACTIVITY DONE WITH USE OF FEATURES PROVIDED IN OUR SOFTWARE, NOT LIMITED TO ESN / MEID / IMEI.

ANY USER USING OUR SOFTWARE FOR ILLEGAL PURPOSE WILL BE SOLE RESPONSIBLE FOR HIS ACTS.

WE CONDEMN USE OF OUR SOFTWARE FOR ANY ILLEGAL PURPOSE.


Download using Support Access or Mirrors


Official Website

what is the use of enable/disable brom vivo 6765?