Database Develop

Does the NTRW utility generally get a device error?

I used the ntrw utility to back up my SD card backup from my Blue Angel. I dont see the E drive showing in Windows Explorer but thats what drive it should be. I use this command:
ntrw read XDAIII.nb1 E:
results are:
NTRW v2.00
Removeable media
Cylinders: 0:1
TracksPerCylinder: 255
SectorsPerTrack: 63
BytesPerSector: 512
bufsize is 65536
507379712 bytes written bytes: 0
ReadFile(): XDAIII.nb1 -- The request could not be performed because of an I/O device error.
Is it normal to see that error? I did get 500KB bytes written out which seems huge but maybe because I backed up my BA to a 521MB card.
Can anybody tell me if this looks OK, I dont want to chance restoring a corrupted image. Are there any docs for ntrw.exe?
Thanks.

I got the same type of error. did you ever get an answer?
after I try to backup the SD to my harddrive, I get this message/error:
G:\incoming\blueangel>ntrw read XDAIIs.nb1 I:
NTRW v2.00
Removeable media
Cylinders: 0:31
TracksPerCylinder: 255
SectorsPerTrack: 63
BytesPerSector: 512
bufsize is 65536
255852544 bytes written bytes: 0
ReadFile(): XDAIIs.nb1 -- The parameter is incorrect.
The file is there if I do a directory listing:
Directory of G:\incoming\blueangel
05/26/2005 04:41 PM <DIR> .
05/26/2005 04:41 PM <DIR> ..
05/26/2005 04:39 PM 32,768 ntrw.exe
05/26/2005 04:39 PM <DIR> romupdate
05/26/2005 04:23 PM 16,677 romupdate.zip
05/26/2005 04:42 PM 255,852,544 XDAIIs.nb1 3 File(s) 255,901,989 bytes
I also posted a request for an answer at http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=151&PN=1
but have no replies as of yet...
but I also see in http://forum.xda-developers.com/vie...s=0&postorder=asc&highlight=readfile&start=75
Note that after finishing the copy from your SD card to your_rom.nb1 file ntrw might give you an error, just don’t pay attention to it.
Click to expand...
Click to collapse

I never heard any response and I did see that quote as well about the error at the end.

adb problem, please help!

ok, so i'm trying to put a bootanimation and the trackball succession mod on my phone.
i downloaded the files, renamed them, put them in my tools folder and opened the command window. typed adb remount, that worked. typed adb devices, my phone is there so that worked. and when i type adb push and the whole file name and what not it says cannot stat no such file or directory.
so i tried putting it on the root of my c drive and doing it that way and it still wouldn't work.
any suggestions or anyone know what's going on here??

Copy/paste out the entire adb session. Include a dir listing of the folder you are presently in as well.

i'm sorry, but i'm kind of new to all of this, so i'm not sure how to include the dir listing of the folder
but here's the session
C:\Users\SubyWIll\Desktop\android\tools>adb remount
remount succeeded
C:\Users\SubyWIll\Desktop\android\tools>adb devices
List of devices attached
HT9CSP818771 device
C:\Users\SubyWIll\Desktop\android\tools>adb push bootanimation.zip /data/local
cannot stat 'bootanimation.zip': No such file or directory
C:\Users\SubyWIll\Desktop\android\tools>

can you provide a dir listing of your tools folder?
You can simply just:
dir > toolsdir.txt
then copy/paste the results.

ah, i think i got it now.
Volume in drive C has no label.
Volume Serial Number is EC86-7915
Directory of C:\Users\SubyWIll\Desktop\android\tools
03/18/2010 03:19 PM <DIR> .
03/18/2010 03:19 PM <DIR> ..
02/05/2010 06:22 PM 43,684 acp.exe
02/05/2010 06:22 PM 2,530,671 adb.exe
02/05/2010 06:22 PM 96,256 AdbWinApi.dll
02/05/2010 06:22 PM 60,928 AdbWinUsbApi.dll
02/05/2010 06:23 PM 3,394 android.bat
02/05/2010 06:23 PM 1,565 apkbuilder.bat
03/18/2010 01:47 PM 1,704,320 bootanimation.zip.zip
02/05/2010 06:23 PM 2,129 ddms.bat
02/05/2010 06:22 PM 128,177 dmtracedump.exe
02/05/2010 06:23 PM 1,491 draw9patch.bat
02/05/2010 06:22 PM 10,897,908 emulator.exe
02/05/2010 06:22 PM 493,759 etc1tool.exe
02/05/2010 06:22 PM 994,279 fastboot.exe
02/05/2010 06:23 PM 1,528 hierarchyviewer.bat
02/05/2010 06:22 PM 30,963 hprof-conv.exe
02/05/2010 06:23 PM <DIR> Jet
02/05/2010 06:23 PM 1,680 layoutopt.bat
02/05/2010 06:22 PM <DIR> lib
02/05/2010 06:22 PM 86,528 mgwz.dll
02/05/2010 06:22 PM 29,498 mksdcard.exe
02/05/2010 02:53 PM 203,735 NOTICE.txt
03/16/2010 05:37 PM 4,048,896 recovery.img
03/18/2010 02:19 PM 504,467 services.jar.zip
02/05/2010 02:53 PM 33 source.properties
02/05/2010 06:22 PM 1,696,645 sqlite3.exe
03/18/2010 03:20 PM 0 toolsdir.txt
02/05/2010 06:23 PM 1,982 traceview.bat
02/05/2010 06:22 PM 1,447,375 zipalign.exe
26 File(s) 25,011,891 bytes
4 Dir(s) 50,512,666,624 bytes free
is that what you need?

remove the last .zip from bootanimation.zip.zip and try again
or adb push bootanimation.zip.zip /data/local/bootanimation.zip
For best practices, I recommend removing the trailing .zip.

deprecate said:
remove the last .zip from bootanimation.zip.zip and try again
or adb push bootanimation.zip.zip /data/local/bootanimation.zip
For best practices, I recommend removing the trailing .zip.
Click to expand...
Click to collapse
haha i just noticed that, but why did it add a .zip to the end? i just added one .zip when i renamed it lol. i'm a little confused on how to remove the last .zip though lol

SubyWill said:
haha i just noticed that, but why did it add a .zip to the end? i just added one .zip when i renamed it lol. i'm a little confused on how to remove the last .zip though lol
Click to expand...
Click to collapse
My guess.
you have "hide file extensions" enabled in windows explorer so when you added a zip to the file, it simply tacked it onto the name which contained the .zip already.
To remove the zip, simple right click, rename, and move the cursor to where you can delete the last 4 chars (.zip).

deprecate said:
My guess.
you have "hide file extensions" enabled in windows explorer so when you added a zip to the file, it simply tacked it onto the name which contained the .zip already.
To remove the zip, simple right click, rename, and move the cursor to where you can delete the last 4 chars (.zip).
Click to expand...
Click to collapse
ahh i figured it all out, thanks man! i appreciate the help!

SubyWill said:
ahh i figured it all out, thanks man! i appreciate the help!
Click to expand...
Click to collapse
No worries. Glad you got it sorted out

Write Secure Settings adb command not working.

I cant seem to grant the write secure settings permission.
For example, I tried allowing tasker and navigation gestures to have the permission. Heres the read out:
PS C:\Users\Owner 2\Desktop> adb shell pm grant net.dinglisch.android.taskerm android.permisson.WRITE_SECURE_ Bad argument: java.lang.IllegalArgumentException: Unknown permission: android.permisson.WRITE_SECURE_ usage: pm path [--user USER_ID] PACKAGE pm dump PACKAGE pm install [-lrtsfd] [-i PACKAGE] [--user USER_ID] [PATH] pm install-create [-lrtsfdp] [-i PACKAGE] [-S BYTES] [--install-location 0/1/2] [--force-uuid internal|UUID] pm install-write [-S BYTES] SESSION_ID SPLIT_NAME [PATH] pm install-commit SESSION_ID pm install-abandon SESSION_ID pm uninstall [-k] [--user USER_ID] [--versionCode VERSION_CODE] PACKAGE pm set-installer PACKAGE INSTALLER pm move-package PACKAGE [internal|UUID] pm move-primary-storage [internal|UUID] pm clear [--user USER_ID] PACKAGE pm enable [--user USER_ID] PACKAGE_OR_COMPONENT pm disable [--user USER_ID] PACKAGE_OR_COMPONENT pm disable-user [--user USER_ID] PACKAGE_OR_COMPONENT pm disable-until-used [--user USER_ID] PACKAGE_OR_COMPONENT pm default-state [--user USER_ID] PACKAGE_OR_COMPONENT pm set-user-restriction [--user USER_ID] RESTRICTION VALUE pm hide [--user USER_ID] PACKAGE_OR_COMPONENT pm unhide [--user USER_ID] PACKAGE_OR_COMPONENT pm grant [--user USER_ID] PACKAGE PERMISSION pm revoke [--user USER_ID] PACKAGE PERMISSION pm reset-permissions pm set-app-link [--user USER_ID] PACKAGE {always|ask|never|undefined} pm get-app-link [--user USER_ID] PACKAGE pm set-install-location [0/auto] [1/internal] [2/external] pm get-install-location pm set-permission-enforced PERMISSION [true|false] pm trim-caches DESIRED_FREE_SPACE [internal|UUID] pm create-user [--profileOf USER_ID] [--managed] [--restricted] [--ephemeral] [--guest] USER_NAME pm remove-user USER_ID pm get-max-users NOTE: 'pm list' commands have moved! Run 'adb shell cmd package' to display the new commands. pm path: print the path to the .apk of the given PACKAGE. pm dump: print system state associated with the given PACKAGE. pm install: install a single legacy package pm install-create: create an install session -l: forward lock application -r: replace existing application -t: allow test packages -i: specify the installer package name -s: install application on sdcard -f: install application on internal flash -d: allow version code downgrade (debuggable packages only) -p: partial application install -g: grant all runtime permissions -S: size in bytes of entire session pm install-write: write a package into existing session; path may be '-' to read from stdin -S: size in bytes of package, required for stdin pm install-commit: perform install of fully staged session pm install-abandon: abandon session pm set-installer: set installer package name pm uninstall: removes a package from the system. Options: -k: keep the data and cache directories around after package removal. pm clear: deletes all data associated with a package. pm enable, disable, disable-user, disable-until-used, default-state: these commands change the enabled state of a given package or component (written as "package/class"). pm grant, revoke: these commands either grant or revoke permissions to apps. The permissions must be declared as used in the app's manifest, be runtime permissions (protection level dangerous), and the app targeting SDK greater than Lollipop MR1. pm reset-permissions: revert all runtime permissions to their default state. pm get-install-location: returns the current install location. 0 [auto]: Let system decide the best location 1 [internal]: Install on internal device storage 2 [external]: Install on external media pm set-install-location: changes the default install location. NOTE: this is only intended for debugging; using this can cause applications to break and other undersireable behavior. 0 [auto]: Let system decide the best location 1 [internal]: Install on internal device storage 2 [external]: Install on external media pm trim-caches: trim cache files to reach the given free space. pm create-user: create a new user with the given USER_NAME, printing the new user identifier of the user. pm remove-user: remove the user with the given USER_IDENTIFIER, deleting all data associated with that user
Click to expand...
Click to collapse
What do I do?

You really tried command?:
Code:
adb shell pm grant net.dinglisch.android.taskerm android.permisson.WRITE_SECURE_
How about:
Code:
adb shell pm grant net.dinglisch.android.taskerm android.permisson.WRITE_SECURE_SETTINGS

Spere said:
You really tried command?:
How about:
Click to expand...
Click to collapse
I did end it with SETTINGS. Thats just how its returned after execution.

Shadow Assassin said:
I did end it with SETTINGS. Thats just how its returned after execution.
Click to expand...
Click to collapse
Yeah, that's what I thought and why I asked.

Are you on a Mac or a PC?

Praks93 said:
Are you on a Mac or a PC?
Click to expand...
Click to collapse
PC

I have also same problem pls help me

pasupathimadaka said:
I have also same problem pls help me
Click to expand...
Click to collapse
Hey, I finally got it to work. Im not sure how but.
1. My phone updated
2. I clean installed the april 2018 windows 10 OS on my computer and installed all updates.
3. I used minimal adb and fastboot.
If you need any files or help, let me know.
I cant guarentee your success but ill help as best as I can.

Shadow Assassin said:
I cant seem to grant the write secure settings permission.
For example, I tried allowing tasker and navigation gestures to have the permission. Heres the read out:
What do I do?
Click to expand...
Click to collapse
you had a typo, you were missing an "i" in "permission". It should be android.permission.WRITE_SECURE_SETTINGS
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
.

Kung-Foo-Kamel's no nonsense "How To Root Your Black Shark 3"

I spent countless hours and downloaded over 100Gb of files and found nearly all how-to's and files borked in someway, so I managed to patch together a working repeatable process to root the Black Shark 3, I also managed to do this with the CN version of JoyUI but I hated it, and switch straight back to the global.
This is for the Black Shark 3 Global only
Note:
1: I will start by saying, your best to place the "Unlockfiles" directory and contents straight into your "C drive" this will make it easy when you open a command prompt, you can then just type: cd c:\unlockfiles and your good to go.
2: I'm not responsible if you FUBAR your phone, that's your problem, not mine
3: before you start this, please ffs log the out of the Mi account on the phone and shut that crap down, don't go any further until you have done this, to be honest, I don't know why anyone would eve log into this garbage in the first place, seems worse than all the google crap.
4: This "How To" is for Windows 10 only, all drivers appeared to be installed automatically by default.
5: Link to download required files: Click Here To Download
6: Password for the zip file is: Password
Unlocking the Bootloader:
1: Enable developer mode in the settings of your BS3
2: Enable USB Debugging in developer settings on your BS3
3: Connect phone to to PC via USB cable
4: Open a command prompt in the Unlockfiles directory
5: Check ADB connection to the phone by entering: adb devices
6: If okay, then type: adb reboot edl
7: Phone will reboot into emergency download mode, screen will be off, but phone will still be connected.
8: Open the MiFlash tool provided in the Unlockfiles folder, ignore any silly messages it gives you about not finder a flash script, then hit select in the MiFLash app and selct the Bootunlocker folder.
9: Press the refresh button, your BS3 should show up under devices as COM10 or something similar, then hit flash, with any luck it should say "successful"
10: Now, hold down the volume down button, then press and hold down the power button, as soon as the phone turns on, release the power button, but keep pressing the volume down until it starts in the bootloader.
11: If you did that correctly, you should be able to type fastboot devices in your command prompt and it should show as connected.
12: In the command prompt run the fbunlock.bat found in the Unlockfiles directory, this will now unlock the bootloader and reboot the phone
13: If successful it will show that the bootloader is unlocked on the phone, leave the phone in this mode if you want to continue with twrp and rooting the phone.
Installing TWRP and Rooting the phone
1: Only follow this guide if you now want to root your phone, be aware that you will need to install the provided rom image.
2: Make sure you command prompt is open in the Unlockfiles directory
3: Test your phone is connected properly by typing: fastboot devices
4: Install TWRP by typing: fastboot flash recovery twrp.img
5: Reboot the phone into recovery mode by typing: fastboot reboot recovery
6: You should now be entering into twrp, it may be in Chinese at first, one of the buttons will switch it to English
7: Now select advanced in twrp, then sideload, twrp should go into sideload mode and wait for the file to be pushed through adb on the pc
8: In your command prompt, type: adb sideload global_stock_rom.zip
9: Go grab a coffee and wait
10: when the rom is installed, hit reboot in twrp
11: If successful your phone will now have botted straight into the OS
12: In you command prompt, type: adb reboot fastboot
13: Once the phone has rebooted, using the volume buttons, select "reboot to bootloader"
14: Check your connection by typing the following in the command prompt: fastboot devices
15: Flash the rooted bootloader file by typing: fastboot flash boot rooted_boot.img
16: Once completed type: fastboot reboot
17: You may be presented with a prompt to wipe the phone and restore to factory, just do it if required.
18: Once you phone has booted to the OS, transfer the Magisk.apk to you downloads folder on the phone, this can be done through windows in "My Computer" as your phone should be connected as a storage device, just make sure you set the phone to transfer files mode when the prompt comes up.
19: Install the Magisk.apk, if everything was successful, Magisk will say installed.
20: Go read or watch a tutorial on how to use Magisk.
21: Have fun with your newly unlocked and rooted Black Shark 3
Additional fun, debloat your phone
1: Head over to here: https://selivan.github.io/2020/02/25/removing-bloatware-from-xiaomi-miui-android.html
2: Fire up the command prompt and navigate to you Unlockfiles directory
3: Check your connection to the phone: adb devices
4: Enter the android shell by typing: adb shell
5: List all packages installed on the phone by typing: pm list packages
6: If you wish to search for packages you can type: pm list packages Xiaomi or pm list packages google
7: To uninstall a package just type: pm uninstall --user 0 app.package.name (Obviously just replace app.package.name with the package name of your choice)
8: I removed all the safe to remove packages from the website listed above, and the phone works super great, even Shark Space 3 switched from Chinese text to English.
I will end this by saying, what a great piece of hardware this phone is, but like most of these Android devices, its plagued with total crap software and half arsed security, just enough to cause people issues if they want to actually have some fun with the device, in my opinion, if you want a phone with good security and well thought out software, then just by an Apple iPhone, I use an iPhone for daily work and all things important, I use Android devices for gaming and tinkering, just like I use a Mac for all things important and a PC for gaming and tinkering.
Regards
Kung-Foo-Kamel

Hi a quick question why do I have to flash a rooted boot image? Isn't it simple after flashing twrp just to flash magisk directly like everyone does ? Or it will brick the device I mean I don't want to install another rom version I just need to install root in my current official global rom that's it
Hope you can clarify all of my queries
Regards

[10:56:33 COM10]:MiFlash 2020.3.14.0
[10:56:33 COM10]:vboytest index:10
[10:56:33 COM10]:flash in thread name:COM10,id:9
[10:56:33 COM10]:flash in thread name:COM10,id:9
[10:56:33 COM10]:vboytest do open :
[10:56:33 COM10]: serial port COM10 opend successfully
[10:56:33 COM10]:[COM10]:start flash.
[10:56:34 COM10]:cannot receive hello packet,MiFlash is trying to reset status!
[10:56:35 COM10]:try to reset status.
[10:56:37 COM10]:write time out try agian 1
[10:56:39 COM10]:write time out try agian 2
[10:56:42 COM10]:write time out try agian 3
Tried all of the avaible online theroes about it holding power button to restart power cycle, entering edl mode without prompt changing usb port actiavating windows test mode Nothing works. Is there another solution?

Wissler9 said:
[10:56:33 COM10]:MiFlash 2020.3.14.0
[10:56:33 COM10]:vboytest index:10
[10:56:33 COM10]:flash in thread name:COM10,id:9
[10:56:33 COM10]:flash in thread name:COM10,id:9
[10:56:33 COM10]:vboytest do open :
[10:56:33 COM10]: serial port COM10 opend successfully
[10:56:33 COM10]:[COM10]:start flash.
[10:56:34 COM10]:cannot receive hello packet,MiFlash is trying to reset status!
[10:56:35 COM10]:try to reset status.
[10:56:37 COM10]:write time out try agian 1
[10:56:39 COM10]:write time out try agian 2
[10:56:42 COM10]:write time out try agian 3
Tried all of the avaible online theroes about it holding power button to restart power cycle, entering edl mode without prompt changing usb port actiavating windows test mode Nothing works. Is there another solution?
Click to expand...
Click to collapse
I could not get any of the newer versions of myflash to work, the one in my download which is 2018 does work, I was getting similar errors as you.
And th only way to enter edl for me was adb reboot edl
I tried all sorts and could not do it manually, probably going to need the special Qualcomm EDL USB Trigger cable.

Josh23 said:
Hi a quick question why do I have to flash a rooted boot image? Isn't it simple after flashing twrp just to flash magisk directly like everyone does ? Or it will brick the device I mean I don't want to install another rom version I just need to install root in my current official global rom that's it
Hope you can clarify all of my queries
Regards
Click to expand...
Click to collapse
I couldn't get it to work and I did almost brick my device, so I went with the full flash method, long winded, but it works, try it directly, worst case is you will have to do what I have done.

Any link for CN?

I have been flashing the ROM but Game Dock and Hyper Charging is CN, How to change English,

CTS PROFILE flase on magisk how to fix that

Kung-Foo-Kamel said:
I spent countless hours and downloaded over 100Gb of files and found nearly all how-to's and files borked in someway, so I managed to patch together a working repeatable process to root the Black Shark 3, I also managed to do this with the CN version of JoyUI but I hated it, and switch straight back to the global.
This is for the Black Shark 3 Global only
Note:
1: I will start by saying, your best to place the "Unlockfiles" directory and contents straight into your "C drive" this will make it easy when you open a command prompt, you can then just type: cd c:\unlockfiles and your good to go.
2: I'm not responsible if you FUBAR your phone, that's your problem, not mine
3: before you start this, please ffs log the out of the Mi account on the phone and shut that crap down, don't go any further until you have done this, to be honest, I don't know why anyone would eve log into this garbage in the first place, seems worse than all the google crap.
4: This "How To" is for Windows 10 only, all drivers appeared to be installed automatically by default.
5: Link to download required files: Click Here To Download
6: Password for the zip file is: Password
Unlocking the Bootloader:
1: Enable developer mode in the settings of your BS3
2: Enable USB Debugging in developer settings on your BS3
3: Connect phone to to PC via USB cable
4: Open a command prompt in the Unlockfiles directory
5: Check ADB connection to the phone by entering: adb devices
6: If okay, then type: adb reboot edl
7: Phone will reboot into emergency download mode, screen will be off, but phone will still be connected.
8: Open the MiFlash tool provided in the Unlockfiles folder, ignore any silly messages it gives you about not finder a flash script, then hit select in the MiFLash app and selct the Bootunlocker folder.
9: Press the refresh button, your BS3 should show up under devices as COM10 or something similar, then hit flash, with any luck it should say "successful"
10: Now, hold down the volume down button, then press and hold down the power button, as soon as the phone turns on, release the power button, but keep pressing the volume down until it starts in the bootloader.
11: If you did that correctly, you should be able to type fastboot devices in your command prompt and it should show as connected.
12: In the command prompt run the fbunlock.bat found in the Unlockfiles directory, this will now unlock the bootloader and reboot the phone
13: If successful it will show that the bootloader is unlocked on the phone, leave the phone in this mode if you want to continue with twrp and rooting the phone.
Installing TWRP and Rooting the phone
1: Only follow this guide if you now want to root your phone, be aware that you will need to install the provided rom image.
2: Make sure you command prompt is open in the Unlockfiles directory
3: Test your phone is connected properly by typing: fastboot devices
4: Install TWRP by typing: fastboot flash recovery twrp.img
5: Reboot the phone into recovery mode by typing: fastboot reboot recovery
6: You should now be entering into twrp, it may be in Chinese at first, one of the buttons will switch it to English
7: Now select advanced in twrp, then sideload, twrp should go into sideload mode and wait for the file to be pushed through adb on the pc
8: In your command prompt, type: adb sideload global_stock_rom.zip
9: Go grab a coffee and wait
10: when the rom is installed, hit reboot in twrp
11: If successful your phone will now have botted straight into the OS
12: In you command prompt, type: adb reboot fastboot
13: Once the phone has rebooted, using the volume buttons, select "reboot to bootloader"
14: Check your connection by typing the following in the command prompt: fastboot devices
15: Flash the rooted bootloader file by typing: fastboot flash boot rooted_boot.img
16: Once completed type: fastboot reboot
17: You may be presented with a prompt to wipe the phone and restore to factory, just do it if required.
18: Once you phone has booted to the OS, transfer the Magisk.apk to you downloads folder on the phone, this can be done through windows in "My Computer" as your phone should be connected as a storage device, just make sure you set the phone to transfer files mode when the prompt comes up.
19: Install the Magisk.apk, if everything was successful, Magisk will say installed.
20: Go read or watch a tutorial on how to use Magisk.
21: Have fun with your newly unlocked and rooted Black Shark 3
Additional fun, debloat your phone
1: Head over to here: https://selivan.github.io/2020/02/25/removing-bloatware-from-xiaomi-miui-android.html
2: Fire up the command prompt and navigate to you Unlockfiles directory
3: Check your connection to the phone: adb devices
4: Enter the android shell by typing: adb shell
5: List all packages installed on the phone by typing: pm list packages
6: If you wish to search for packages you can type: pm list packages Xiaomi or pm list packages google
7: To uninstall a package just type: pm uninstall --user 0 app.package.name (Obviously just replace app.package.name with the package name of your choice)
8: I removed all the safe to remove packages from the website listed above, and the phone works super great, even Shark Space 3 switched from Chinese text to English.
I will end this by saying, what a great piece of hardware this phone is, but like most of these Android devices, its plagued with total crap software and half arsed security, just enough to cause people issues if they want to actually have some fun with the device, in my opinion, if you want a phone with good security and well thought out software, then just by an Apple iPhone, I use an iPhone for daily work and all things important, I use Android devices for gaming and tinkering, just like I use a Mac for all things important and a PC for gaming and tinkering.
Regards
Kung-Foo-Kamel
Click to expand...
Click to collapse
adb shell pm uninstall -k --user 0 com.xiaomi.mipicks
adb shell pm uninstall -k --user 0 com.miui.msa.global
adb shell pm uninstall -k --user 0 com.miui.cloudservice
adb shell pm uninstall -k --user 0 com.miui.cloudbackup
adb shell pm uninstall -k --user 0 com.xiaomi.glgm
adb shell pm uninstall -k --user 0 com.xiaomi.payment
adb shell pm uninstall -k --user 0 cn.wps.xiaomi.abroad.lite
adb shell pm uninstall -k --user 0 com.xiaomi.midrop
adb shell pm uninstall -k --user 0 com.miui.yellowpage
adb shell pm uninstall -k --user 0 com.miui.android.fashiongallery
adb shell pm uninstall -k --user 0 com.miui.miservice
adb shell pm uninstall -k --user 0 com.miui.bugreport
adb shell pm uninstall -k --user 0 com.google.android.youtube
adb shell pm uninstall -k --user 0 com.google.ar.lens
adb shell pm uninstall -k --user 0 com.google.android.googlequicksearchbox
adb shell pm uninstall -k --user 0 com.google.android.apps.wellbeing
adb shell pm uninstall -k --user 0 com.facebook.services
adb shell pm uninstall -k --user 0 com.facebook.system
adb shell pm uninstall -k --user 0 com.facebook.appmanager
adb shell pm uninstall -k --user 0 com.android.wallpaper.livepicker
adb shell pm uninstall -k --user 0 com.android.stk
adb shell pm uninstall -k --user 0 com.google.android.apps.googleassistant
adb shell pm uninstall -k --user 0 com.miui.hybrid
adb shell pm uninstall -k --user 0 com.android.chrome
adb shell pm uninstall -k --user 0 com.google.android.gm
adb shell pm uninstall -k --user 0 com.google.android.apps.subscriptions.red
adb shell pm uninstall -k --user 0 com.google.android.apps.walletnfcrel
adb shell pm uninstall -k --user 0 com.google.android.gms.location.history
adb shell pm uninstall -k --user 0 com.google.android.apps.maps
adb shell pm uninstall -k --user 0 com.miui.videoplayer
adb shell pm uninstall -k --user 0 com.miui.mishare.connectivity
adb shell pm uninstall -k --user 0 com.miui.analytics
adb shell pm uninstall -k --user 0 com.google.android.apps.setupwizard.searchselector <
adb shell pm uninstall -k --user 0 com.netflix.partner.activation
adb shell pm uninstall -k --user 0 com.ebay.carrier
adb shell pm uninstall -k --user 0 com.android.vending
adb shell pm uninstall -k --user 0 com.miui.micloudsync
adb shell pm uninstall -k --user 0 com.miui.newmidrive
adb shell pm uninstall -k --user 0 com.miui.player
adb shell pm uninstall -k --user 0 com.mi.globalbrowser
adb shell pm uninstall -k --user 0 com.miui.cleanmaster
adb shell pm uninstall -k --user 0 com.miui.notes
adb shell pm uninstall -k --user 0 com.google.android.calendar
adb shell pm uninstall -k --user 0 com.google.android.apps.messaging
adb shell pm uninstall -k --user 0 com.micredit.in
adb shell pm uninstall -k --user 0 com.mipay.wallet.in
adb shell pm uninstall -k --user 0 com.xiaomi.scanner

Hi, after I use the XiaoMi Flash tool, I can't get into fastboot mode with your steps. I tried going to it by holding Volume Up + Plugging in USB to go into fastboot mode but the fbunlock.bat gives me a 'Unrecognized command flashing unlock_critical' . Can you help me? Thank you!
EDIT: Nevermind, realized I had to launch the .bat file when I was at bootloader, not at the "fastboot" option on the Bootloader.
Worked fine for me. Very easy instructions, I have 8/128GB Global Version (not CN flashed to Global), and oh god, my game space (the one in game) is all in Chinese (this can probably be fixed by reinstalling an English APK of it). And lastly I have CTS Profile Failed on my Magisk, any fix for that?
Small question: Do your notifications also show up on your lock screen?

Kung-Foo-Kamel said:
5: Reboot the phone into recovery mode by typing: fastboot reboot recovery
Click to expand...
Click to collapse
After doing this step my BS3 just stuck at Black Shark logo. Any solution ?
Btw thanks for the guide.
Edit: It's work again after i press hold down the volume down button dan power button

Question I perma-bricked my Mi 11. (SOLVED)

Hello!
While flashing the stock ROM with mi flash tool , i ran over the wire and accidentally unplugged..
Now my phone stuck in EDL mode
can anyone please help me?
thanks
update : i had to pay some indian 30$ for edl auth

First, don't panic! EDL mode is OK.
First you need Mi Flash Tool. You already have it, great.
Install the Qualcomm QDLoader drivers. This will give your computer access to the EDL mode on the phone. This is also known as the Qualcomm Driver Qdloader 9008 driver if you need it for another OS. You can also look here.
Once your phone is recognized by your PC, you can use Mi Flash Tool to install the stock rom.
Hope that helps!

bitpushr said:
First, don't panic! EDL mode is OK.
First you need Mi Flash Tool. You already have it, great.
Install the Qualcomm QDLoader drivers. This will give your computer access to the EDL mode on the phone. This is also known as the Qualcomm Driver Qdloader 9008 driver if you need it for another OS. You can also look here.
Once your phone is recognized by your PC, you can use Mi Flash Tool to install the stock rom.
Hope that helps!
Click to expand...
Click to collapse
Really? In EDL mode you can flash now yourself? Usually you need a special permitted account to be able to and this is not for free.

Iv not bricked my Mii 11 in this way, but I did one plus 7 t and edl works.

g33k1 said:
Iv not bricked my Mii 11 in this way, but I did one plus 7 t and edl works.
Click to expand...
Click to collapse
OnePlus is something different. There you can go anytime into bootloader and use the EDL Image to restore. With Xiaomi you have to logon BEFORE you can do that and they allow only "permitted" accounts. User having such accounts usually want between 15-70€ to remotely connect to your PC and use their user to flash back the image in your Xiaomi via EDL. Your normal user (with which you unlocked the bootloader) has no permission to do that.

bitpushr said:
First, don't panic! EDL mode is OK.
First you need Mi Flash Tool. You already have it, great.
Install the Qualcomm QDLoader drivers. This will give your computer access to the EDL mode on the phone. This is also known as the Qualcomm Driver Qdloader 9008 driver if you need it for another OS. You can also look here.
Once your phone is recognized by your PC, you can use Mi Flash Tool to install the stock rom.
Hope that helps!
Click to expand...
Click to collapse
I would like to know more about this. How come this method does not require auth account as ive seen in many other cases? Whats different?

Oh another set of security. Thanks for clearing that up

for xiaomi phones you still need an edl xiaomi authrized account for flashing

bitpushr said:
First, don't panic! EDL mode is OK.
First you need Mi Flash Tool. You already have it, great.
Install the Qualcomm QDLoader drivers. This will give your computer access to the EDL mode on the phone. This is also known as the Qualcomm Driver Qdloader 9008 driver if you need it for another OS. You can also look here.
Once your phone is recognized by your PC, you can use Mi Flash Tool to install the stock rom.
Hope that helps!
Click to expand...
Click to collapse
Thanks for that, could you elaborate a bit more (this is what I've done so far)
Installed Drivers (Qualcomm)
Have the MI Flash Tool
Downloaded the "venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global"
Connect phone to computer wait for sound, check in device manager to see its in 9008
refresh mi flash -->then flash (here is the log file)
[5:20:59 PM COM4]:sw in images
[5:21:00 PM COM4]:sw has prog_firehose_lite.elf
[5:21:00 PM COM4]:flash in thread name:COM4,id:23
[5:21:00 PM COM4]:vboytest do open :
[5:21:00 PM COM4]: serial port COM4 opend successfully
[5:21:00 PM COM4]:[COM4]:start flash.
[5:21:00 PM COM4]:received hello packet
[5:21:00 PM COM4]rogrammertype: 0
[5:21:00 PM COM4]:vboytest:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images
[5:21:00 PM COM4]:download programmer file: D:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images\prog_firehose_ddr.elf
[5:21:00 PM COM4]:download programmer D:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images\prog_firehose_ddr.elf
[5:21:14 PM COM4]:Send done packet
[5:21:14 PM COM4]:file D:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images\prog_firehose_ddr.elf transferred successfully
[5:21:16 PM COM4]:send nop command
[5:21:16 PM COM4]:send command:<?xml version="1.0" ?><data><nop verbose="0" value="ping"/></data>
[5:21:18 PM COM4]:write time out try agian 1
[5:21:21 PM COM4]:write time out try agian 2
[5:21:23 PM COM4]:write time out try agian 3
[5:21:26 PM COM4]:write time out try agian 4
[5:21:28 PM COM4]:write time out try agian 5
[5:21:31 PM COM4]:write time out try agian 6
[5:21:34 PM COM4]:write time out try agian 7
[5:21:34 PM COM4]:error:The write timed out.
[5:21:34 PM COM4]:System.Exception: write time out,maybe device was disconnected.
at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 201
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 217
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 1873
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 251 at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 201
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 217
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 1873
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 251
[5:21:34 PM COM4]:no provision exit:COM4
[5:21:34 PM COM4]:flashSuccess False
[5:21:34 PM COM4]:isFactory False CheckCPUID False
[5:21:34 PM COM4]:before:flashSuccess is False set IsUpdate:True set IsDone True
[5:21:34 PM COM4]:after:flashSuccess is False set IsUpdate:false set IsDone true
all the help would be welcome...
Thanks!

killa-beez said:
Thanks for that, could you elaborate a bit more (this is what I've done so far)
Installed Drivers (Qualcomm)
Have the MI Flash Tool
Downloaded the "venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global"
Connect phone to computer wait for sound, check in device manager to see its in 9008
refresh mi flash -->then flash (here is the log file)
[5:20:59 PM COM4]:sw in images
[5:21:00 PM COM4]:sw has prog_firehose_lite.elf
[5:21:00 PM COM4]:flash in thread name:COM4,id:23
[5:21:00 PM COM4]:vboytest do open :
[5:21:00 PM COM4]: serial port COM4 opend successfully
[5:21:00 PM COM4]:[COM4]:start flash.
[5:21:00 PM COM4]:received hello packet
[5:21:00 PM COM4]rogrammertype: 0
[5:21:00 PM COM4]:vboytest:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images
[5:21:00 PM COM4]:download programmer file: D:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images\prog_firehose_ddr.elf
[5:21:00 PM COM4]:download programmer D:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images\prog_firehose_ddr.elf
[5:21:14 PM COM4]:Send done packet
[5:21:14 PM COM4]:file D:\Xiaomi Files\venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00_11.0_global\images\prog_firehose_ddr.elf transferred successfully
[5:21:16 PM COM4]:send nop command
[5:21:16 PM COM4]:send command:<?xml version="1.0" ?><data><nop verbose="0" value="ping"/></data>
[5:21:18 PM COM4]:write time out try agian 1
[5:21:21 PM COM4]:write time out try agian 2
[5:21:23 PM COM4]:write time out try agian 3
[5:21:26 PM COM4]:write time out try agian 4
[5:21:28 PM COM4]:write time out try agian 5
[5:21:31 PM COM4]:write time out try agian 6
[5:21:34 PM COM4]:write time out try agian 7
[5:21:34 PM COM4]:error:The write timed out.
[5:21:34 PM COM4]:System.Exception: write time out,maybe device was disconnected.
at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 201
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 217
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 1873
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 251 at XiaoMiFlash.code.Utility.Comm.WritePort(Byte[] send, Int32 offSet, Int32 count) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 201
at XiaoMiFlash.code.Utility.Comm.SendCommand(String command, Boolean checkAck) in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\Utility\Comm.cs:line 217
at XiaoMiFlash.code.bl.SerialPortDevice.ping() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 1873
at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() in E:\code\new_miflash\MiFlash-merge-zhousheng\MiFlash\XiaoMiFlash\XiaoMiFlash\code\bl\SerialPortDevice.cs:line 251
[5:21:34 PM COM4]:no provision exit:COM4
[5:21:34 PM COM4]:flashSuccess False
[5:21:34 PM COM4]:isFactory False CheckCPUID False
[5:21:34 PM COM4]:before:flashSuccess is False set IsUpdate:True set IsDone True
[5:21:34 PM COM4]:after:flashSuccess is False set IsUpdate:false set IsDone true
all the help would be welcome...
Thanks!
Click to expand...
Click to collapse
had the same isssue, u hardbricked ur device
Howto unbrick