Sp flashtool authentication file!

USEFUL?

  • yes..will give it a try too

    Votes: 33 42.3%
  • yes..it has worked

    Votes: 11 14.1%
  • NO

    Votes: 34 43.6%

  • Total voters
    78
Search This thread

Jy Traum

New member
Sep 24, 2018
1
0
HIT THE THANKS BUTTON
Newer MTK (mediatek) devices usually request for an AUTHENTICATION CERTIFICATE TO FLASH.. here am sharing the file i have.. i have used it on two different phones.. makes me think it can work even on most devices out there.. am sharing it here for people with such a problem to try it out.. you might be as lucky as i ey
EXTRACT and use file.
download from attachments.. give feedback after trial

Thanks.
 
Last edited:

audacias87

New member
Sep 17, 2018
4
1
I was able to flash my Redmi6 (Mediatek MT6765) and right now it has a functional TWRP recovery and Magisk flashed and is passing Safety Net correctly. I didn't use any of the auth files in this thread, instead i generated the signatures for the boot image with a pythong script available in the ROM I link here.

This is the exact image I flashed and has the root and recovery modifications, you can use the flash_all.sh script and it takes care of everything.


The forum doesn't let me post the link. Let me know if anybody wants to check it out.


Kernel log I just pulled from the phone:

Starting TWRP 3.3.0-0423-a0d699c4 on Tue Oct 1 00:59:19 2019
(pid 341)
TWRP Version : 3.3.0-0423
Build Date : 2019年 04月 23日 星期二 13:51:38 CST
Build User : wzsx150
Build Device : Redmi 6
TW_DEFAULT_DEVICE_NAME := Redmi 6
TW_NO_VERITY_OPT_ENCRYPT := true
TW_USE_RESTORE_STOCK_REC := true
TW_USE_SIGN_BOOT := true
TW_USE_LEDS_HAPTICS := true
RECOVERY_SDCARD_ON_DATA := true
TW_NO_USB_STORAGE := true
TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/class/leds/lcd-backlight/brightness'
I:Got max brightness 255 from '/sys/class/leds/lcd-backlight/max_brightness'
I:persist tw_brightness: '102'
I:TWFunc::Set_Brightness: Setting brightness control to 102
I:LANG: zh_CN
Starting the UI...
setting DRM_FORMAT_RGBX8888 and GGL_PIXEL_FORMAT_RGBX_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
vi.bits_per_pixel = 32
vi.red.offset = 0 .length = 8
vi.green.offset = 8 .length = 8
vi.blue.offset = 16 .length = 8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
framebuffer: 0 (720 x 1440)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 102
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:pageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 0.666667x and height 0.750000x, offsets x: 0 y: 0 w: 0 h: 0
I:Loading resources...
I:Loading variables...
I:Loading mouse cursor...
I:Loading pages...
I:Loading page splash
I:Switching packages (splash)
=> Linking mtab
=> Processing /etc/twrp.fstab
I:Reading /etc/twrp.fstab
I:processing '/data'
I:processing '/cache'
I:processing '/system'
I:processing '/system_image'
I:processing '/boot'
I:processing '/recovery'
I:processing '/bootloader'
I:processing '/bootloader2'
I:processing '/vendor'
I:processing '/vendor_image'
I:processing '/cust'
I:Created '/cust' folder.
I:processing '/cust_image'
I:processing '/persist'
I:Created '/persist' folder.
I:Attempt to load settings from /persist settings file...
I:InfoManager loading from '/persist/.twrps_wzsx150'.
I:TWFunc::Set_Brightness: Setting brightness control to 102
I:TWFunc::Fixup_Time: Pre-fix date and time: 2019-10-01--00-59-19
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: Date and time corrected: 2019-10-01--00-59-20
I:processing '/persist_image'
I:processing '/nvram'
I:processing '/proinfo'
I:processing '/logo'
I:processing '/tee1'
I:processing '/tee2'
I:processing '/devinfo'
I:processing '/misc'
I:processing '/metadata'
I:processing '/persistent'
I:processing '/protect_f'
I:Created '/protect_f' folder.
I:processing '/protect_s'
I:Created '/protect_s' folder.
I:processing '/nvdata'
I:Created '/nvdata' folder.
I:processing '/nvcfg'
I:Created '/nvcfg' folder.
I:processing '/external_sd'
I:Created '/external_sd' folder.
I:processing '/usb-otg'
I:Created '/usb-otg' folder.
I:Done processing fstab files
I:Setting up '/data' as data/media emulated storage.
I:Can't probe device /dev/block/mmcblk0p39
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p39', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p39
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p39', current file system: 'ext4'
get fde password type: default_password(1)
I:Backup folder set to '/data/media/TWRP/BACKUPS/d2e59b5f7d24'
I:Settings storage is '/data/media'
I:update osversion: start
I:system: ro.build.version.release=[8.1.0]
I:system: ro.build.version.security_patch=[2019-08-01]
I:system: os_version=[8.1.0]
I:system: os_patch_level=[2019-08]
I:system: osversion_val=[268697912(0x10040138)]
I:system: osversion_val is ok
I:update osversion: process '/dev/block/platform/bootdevice/by-name/recovery'
I:recovery: osversion_val=[268697912(0x10040138)]
I:recovery: os_version=[8.1.0]
I:recovery: os_patch_level=[2019-08]
I:recovery and system osversion_val is the same, skipped
get fde password type: default_password(1)
I:Device is encrypted with the default password, attempting to decrypt.
D:crypt_ftr->fs_size = 51152863
I:Using scrypt with keymaster for cryptfs KDF
I:TWRP keymaster max API: 3
I:Signing safely-padded object
keymaster module name is Keymaster UT HAL
keymaster version is 512
Found keymaster0 module, using keymaster0 API.
Decrypt process ended with signal: 11
TW_CRYPTO_USE_SYSTEM_VOLD := true
Checking existence of vendor and firmware partitions...
vendor partition mounted, skipping /vendor substitution
I:Is_Mounted: Unable to find partition for path '/firmware'
Attempting to use system's vold for decryption...
List of additional services for vold_decrypt:
hwservicemanager: Enabled as sys_hwservicemanager -> /system/bin/hwservicemanager
keymaster-3-0: Enabled as ven_keymaster-3-0 -> /vendor/bin/hw/android.hardware.keymaster@3.0-service
Setting up folders and permissions...
Symlinking firmware folder...
Symlinking firmware files...
0 file(s) symlinked.
Starting services...
Start service sys_hwservicemanager: running.
hwservicemanager is ready.
Start service ven_keymaster-3-0: running.
Start service sys_vold: running.
footer_br: crypto footer backed up
About to run vdc...
default_password: ****************************
sdkver: 27, using /system/bin/vdc
trying connection to vold (Result: I:200 397 0|RC=0)
sdkver: 27, using /system/bin/vdc
trying connection to vold (Result: I:200 407 0|RC=0)
default_password: vdc cryptfs mountdefaultencrypted success
footer_br: crypto footer restored
Stopping services...
Stop service sys_vold: stopped.
Stop service sys_hwservicemanager: stopped.
Stop service ven_keymaster-3-0: stopped.
Finished.
Data successfully decrypted, new block device: '/dev/block/dm-0'
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/d2e59b5f7d24'
Updating partition details...
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Data backup size is 3598MB, free: 15271MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Translating partition display names
I:String resources not loaded when looking for 'system'. Using default value.
I:String resources not loaded when looking for 'system_image'. Using default value.
I:String resources not loaded when looking for 'vendor'. Using default value.
I:String resources not loaded when looking for 'vendor_image'. Using default value.
I:String resources not loaded when looking for 'cache'. Using default value.
I:String resources not loaded when looking for 'boot'. Using default value.
I:String resources not loaded when looking for 'recovery'. Using default value.
I:String resources not loaded when looking for 'data'. Using default value.
I:String resources not loaded when looking for 'data_backup'. Using default value.
I:String resources not loaded when looking for 'internal'. Using default value.
I:String resources not loaded when looking for 'microsd'. Using default value.
I:String resources not loaded when looking for 'data_backup'. Using default value.
I:String resources not loaded when looking for 'microsd'. Using default value.
I:String resources not loaded when looking for 'usbotg'. Using default value.
I:String resources not loaded when looking for 'usbotg'. Using default value.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/d2e59b5f7d24'
...done
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
/data | /dev/block/dm-0 | Size: 24519MB Used: 3598MB Free: 15271MB Backup Size: 3598MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p39
Decrypted_Block_Device: /dev/block/dm-0
Crypto_Key_Location: /dev/block/platform/bootdevice/by-name/metadata
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data (excl. storage)
Storage_Path: /data/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537

I:Unmounting main partitions...
Successfully decrypted with default password.
I:Decrypt adopted storage starting
I:pageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
I:successfully loaded storage.xml
I:type: '00000000000000000000000000000000'
I:part: '00000000000000000000000000000000'
I:Adopted_GUID '00000000000000000000000000000000'
Updating partition details...
I:Data backup size is 3598MB, free: 15271MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Translating partition display names
I:String resources not loaded when looking for 'system'. Using default value.
I:String resources not loaded when looking for 'system_image'. Using default value.
I:String resources not loaded when looking for 'vendor'. Using default value.
I:String resources not loaded when looking for 'vendor_image'. Using default value.
I:String resources not loaded when looking for 'cache'. Using default value.
I:String resources not loaded when looking for 'boot'. Using default value.
I:String resources not loaded when looking for 'recovery'. Using default value.
I:String resources not loaded when looking for 'data'. Using default value.
I:String resources not loaded when looking for 'data_backup'. Using default value.
I:String resources not loaded when looking for 'internal'. Using default value.
I:String resources not loaded when looking for 'microsd'. Using default value.
I:String resources not loaded when looking for 'data_backup'. Using default value.
I:String resources not loaded when looking for 'microsd'. Using default value.
I:String resources not loaded when looking for 'usbotg'. Using default value.
I:String resources not loaded when looking for 'usbotg'. Using default value.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/d2e59b5f7d24'
...done
I:Unmounting main partitions...


Partition Logs:
/data | /dev/block/dm-0 | Size: 24519MB Used: 3598MB Free: 15271MB Backup Size: 3598MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p39
Decrypted_Block_Device: /dev/block/dm-0
Crypto_Key_Location: /dev/block/platform/bootdevice/by-name/metadata
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data (excl. storage)
Storage_Path: /data/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537

/cache | /dev/block/mmcblk0p38 | Size: 247MB Used: 0MB Free: 247MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p38
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/system | /dev/block/mmcblk0p36 | Size: 2415MB Used: 2046MB Free: 369MB Backup Size: 2046MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/system_image | /dev/block/mmcblk0p36 | Size: 2560MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p36
Display_Name: System Image
Storage_Name: system_image
Backup_Path: /system_image
Backup_Name: system_image
Backup_Display_Name: System Image
Storage_Path: /system_image
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/boot | /dev/block/mmcblk0p28 | Size: 64MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p28
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/recovery | /dev/block/mmcblk0p2 | Size: 64MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/bootloader | /dev/block/mmcblk0p26 | Size: 1MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p26
Display_Name: bootloader
Storage_Name: bootloader
Backup_Path: /bootloader
Backup_Name: bootloader
Backup_Display_Name: bootloader
Storage_Path: /bootloader
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/bootloader2 | /dev/block/mmcblk0p27 | Size: 1MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p27
Display_Name: bootloader2
Storage_Name: bootloader2
Backup_Path: /bootloader2
Backup_Name: bootloader2
Backup_Display_Name: bootloader2
Storage_Path: /bootloader2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/vendor | /dev/block/mmcblk0p35 | Size: 727MB Used: 371MB Free: 356MB Backup Size: 371MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Mount_Read_Only
Primary_Block_Device: /dev/block/mmcblk0p35
Display_Name: Vendor
Storage_Name: Vendor
Backup_Path: /vendor
Backup_Name: vendor
Backup_Display_Name: Vendor
Storage_Path: /vendor
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/vendor_image | /dev/block/mmcblk0p35 | Size: 768MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p35
Display_Name: Vendor Image
Storage_Name: Vendor_image
Backup_Path: /vendor_image
Backup_Name: vendor_image
Backup_Display_Name: Vendor Image
Storage_Path: /vendor_image
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/cust | /dev/block/mmcblk0p31 | Size: 487MB Used: 375MB Free: 112MB Backup Size: 375MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p31
Display_Name: cust
Storage_Name: cust
Backup_Path: /cust
Backup_Name: cust
Backup_Display_Name: cust
Storage_Path: /cust
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/cust_image | /dev/block/mmcblk0p31 | Size: 512MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p31
Display_Name: cust_image
Storage_Name: cust_image
Backup_Path: /cust_image
Backup_Name: cust_image
Backup_Display_Name: cust_image
Storage_Path: /cust_image
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/persist | /dev/block/mmcblk0p12 | Size: 57MB Used: 0MB Free: 57MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: persist
Storage_Name: persist
Backup_Path: /persist
Backup_Name: persist
Backup_Display_Name: persist
Storage_Path: /persist
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files

/persist_image | /dev/block/mmcblk0p12 | Size: 64MB
Flags: IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: persist
Storage_Name: persist
Backup_Path: /persist_image
Backup_Name: persist_image
Backup_Display_Name: persist
Storage_Path: /persist_image
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/nvram | /dev/block/mmcblk0p24 | Size: 64MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p24
Display_Name: nvram
Storage_Name: nvram
Backup_Path: /nvram
Backup_Name: nvram
Backup_Display_Name: nvram
Storage_Path: /nvram
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/proinfo | /dev/block/mmcblk0p14 | Size: 3MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p14
Display_Name: proinfo
Storage_Name: proinfo
Backup_Path: /proinfo
Backup_Name: proinfo
Backup_Display_Name: proinfo
Storage_Path: /proinfo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/logo | /dev/block/mmcblk0p29 | Size: 64MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p29
Display_Name: logo
Storage_Name: logo
Backup_Path: /logo
Backup_Name: logo
Backup_Display_Name: logo
Storage_Path: /logo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/tee1 | /dev/block/mmcblk0p32 | Size: 5MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p32
Display_Name: trustzone1
Storage_Name: trustzone1
Backup_Path: /tee1
Backup_Name: tee1
Backup_Display_Name: trustzone1
Storage_Path: /tee1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/tee2 | /dev/block/mmcblk0p33 | Size: 5MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p33
Display_Name: trustzone2
Storage_Name: trustzone2
Backup_Path: /tee2
Backup_Name: tee2
Backup_Display_Name: trustzone2
Storage_Path: /tee2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd

/devinfo | /dev/block/mmcblk0p37 | Size: 8MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p37
Display_Name: devinfo
Storage_Name: devinfo
Backup_Path: /devinfo
Backup_Name: devinfo
Backup_Display_Name: devinfo
Storage_Path: /devinfo
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
(...)
 

alaz30

New member
Feb 8, 2010
1
0
I was able to flash my Redmi6 (Mediatek MT6765) and right now it has a functional TWRP recovery and Magisk flashed and is passing Safety Net correctly. I didn't use any of the auth files in this thread, instead i generated the signatures for the boot image with a pythong script available in the ROM I link here.

This is the exact image I flashed and has the root and recovery modifications, you can use the flash_all.sh script and it takes care of everything.


The forum doesn't let me post the link. Let me know if anybody wants to check it out.


Kernel log I just pulled from the phone:


i've just bricked my redmi 6a, could you help me out sir please..? TIA
 

avwova

New member
Apr 16, 2019
3
0
Sec_Auth_file

I have the same error for Camon 11 cf7. After, i have downloaded the file, iam suppose to paste it in SP Tools folder? Or what iam suppose to do...
 

burzaa4

Member
Oct 9, 2019
36
2
I am looking for a working file authentication file for redmi 6 will anyone help for free?
 

audacias87

New member
Sep 17, 2018
4
1
tinyurl(dot)com

slash tnr4esp

It's the old fastboot image I modified so it installs TWRP recovery, permanently rooted boot image and some more stuff, use the scripts in the file to flash your phone. It worked for me, but I take 0 responsability of what it does to your phone.
 

burzaa4

Member
Oct 9, 2019
36
2
tinyurl(dot)com

slash tnr4esp

It's the old fastboot image I modified so it installs TWRP recovery, permanently rooted boot image and some more stuff, use the scripts in the file to flash your phone. It worked for me, but I take 0 responsability of what it does to your phone.

Thank you, I still have a brick, so it was worth a try. Unfortunately, I still have the status brom cmd fail 0xc0060005 or status brom cmd fail 0xc0060001.
 

dmilz

Senior Member
Mar 9, 2015
381
123
Lusaka
I was able to flash my Redmi6 (Mediatek MT6765) and right now it has a functional TWRP recovery and Magisk flashed and is passing Safety Net correctly. I didn't use any of the auth files in this thread, instead i generated the signatures for the boot image with a pythong script available in the ROM I link here.

This is the exact image I flashed and has the root and recovery modifications, you can use the flash_all.sh script and it takes care of everything.


The forum doesn't let me post the link. Let me know if anybody wants to check it out.


Kernel log I just pulled from the phone:

If you have a solution, you can post it here we updated the main post for others to benefit or you can make a new thread. It's good you are getting somewhere.

To those whom the auth file i shared did not work, sorry keep looking you might find something that works for you.

To those whom have benefited from the auth file, good for you;)

For those that have other auth files or methods, Feel free to share here. I will update main post with your findings and give credit

For those
 

natsupeng

Member
Jan 5, 2020
15
2
Since my Nokia 3 bricked, if use the DL file in SP Flash tool, need the auth file because the DL file isn't match the Boot ROM on SoC depended on vendor built.

After found the correct verison of DL file, my Nokia 3 can flash the firmware.

P.S. Need press the Vol + & Vol - & PWR (Three button) at the same time during plugged in USB when the SP flash tool start.
 

EjazAhmad

New member
May 21, 2020
3
0
Hi XDA team,
I have xiaomi redmi 6a (mtk6765).i tried to flash a ROM but now my phone is bricked.
Only black screen. I tried too many methods to unbrick it but every time I failed. Could anyone help me to find DA and AUTH file for redmi 6a.😥😥
Reply me on ea7382407@gmail.com.
 

dmilz

Senior Member
Mar 9, 2015
381
123
Lusaka
Since my Nokia 3 bricked, if use the DL file in SP Flash tool, need the auth file because the DL file isn't match the Boot ROM on SoC depended on vendor built.

After found the correct verison of DL file, my Nokia 3 can flash the firmware.

P.S. Need press the Vol + & Vol - & PWR (Three button) at the same time during plugged in USB when the SP flash tool start.

Am glad you found a way.
 

Badexample4all

New member
Sep 24, 2021
1
0
HIT THE THANKS BUTTON
Newer MTK (mediatek) devices usually request for an AUTHENTICATION CERTIFICATE TO FLASH.. here am sharing the file i have.. i have used it on two different phones.. makes me think it can work even on most devices out there.. am sharing it here for people with such a problem to try it out.. you might be as lucky as i ey
EXTRACT and use file.

Join our mobile repairs telegram group
https://t.me/joinchat/G3LynhqZG60GcqX1uLFEOA

download from attachments.. give feedback after trial
used it at mtk device spflashtool accept the file and move on but BCOM CMDSTART error appers.
 

Acbel

New member
Dec 25, 2021
1
0
Mod edit - translated by https://www.deepl.com/translator:
Thank you very much, that file saved my life.
**********************************************
Muchas Gracias, ese archivo me salvo la vida.
 
Last edited by a moderator:

Oswald Boelcke

Senior Moderator / Moderator Committee
Staff member
Mod edit - translated by https://www.deepl.com/translator:
Thank you very much, that file saved my life.
**********************************************
Muchas Gracias, ese archivo me salvo la vida.
@Acbel

As courtesy, I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Spanish posts. Thanks for your cooperation!
4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

Regards
Oswald Boelcke
Senior Moderator
 

Top Liked Posts