Error status sec auth file needed 0xc0030012 как исправить ошибку
В теме нет куратора. По вопросам наполнения шапки, обращайтесь к модераторам раздела через кнопку 
под сообщениями, на которые необходимо добавить ссылки.
Ребята вообщем, есть прошивка инженерная, выложенная lioxx
Я скачал её, в ней нашёл MT6797_Android_scatter.txt и secro.img, необходимые для разблокировки загрузчика и восстановления кирпича.
Если делать по аналогии m2 note, где надо разблокировать загрузчик, то не хватает файла temp_unlock_secro.img, которого я в архиве найти не могу, и понятия не имею как его собсно получить. Вот скриншот архива:
А если же делать по аналогии M3 mini, где восстанавливают кирпич, имея MT67**_Android_scatter.txt
То этот архив выше уж точно будет полезен тем, у кого кирпич! Стоит попробовать.
Если у кого есть какие либо идеи, предложения, мысли, кто разбирается собственно в разблокировке загрузчика и имеет понятие как из secro.img, сделать temp_unlock_secro.img, то вэлком сюда для обсуждения. Может мы наконец найдём способ разблокировки загрузчика)
Это не то о чем я думаю? Зашёл в «правовая информация» телефон не шитый.
Это, лишь, перестраховка компании Meizu на случай судебных обращений от пользователей, устройства которых взломали и похитили информацию. Если таковые случай возникнут.
Работает:
Видит память телефона
Видит ОЗУ
Видит камеру(а значит драйвера камеры рабочие, не придётся допиливать)
Вай фай работает
Блутуз к сожалению не проверил
Заурик, как с отпечатком дела?
P.S. По поводу краша звонилки, попробуй кэш приложения этого очистить, должно помочь
STATUS_SEC_AUTH_FILE_NEEDED (0x0030012)
Please guide me to flash Infinix x652b. it shows the error STATUS_SEC_AUTH_FILE_NEEDED (0xC0030012) on SP Flash tool
I tried hard but can’t find AUTH file for this model. please please please help me to solve this problem.
Bundle of thanks in advance.
(20-06-2020, 10:03 AM) Fahad116600 Wrote: Please guide me to flash Infinix x652b. it shows the error STATUS_SEC_AUTH_FILE_NEEDED (0xC0030012) on SP Flash tool
I tried hard but can’t find AUTH file for this model. please please please help me to solve this problem.
Bundle of thanks in advance.
use software download tool (format all + download) @ https://forum.hovatek.com/thread-23709.html to flash the phone.
(20-06-2020, 10:03 AM) Fahad116600 Wrote: Please guide me to flash Infinix x652b. it shows the error STATUS_SEC_AUTH_FILE_NEEDED (0xC0030012) on SP Flash tool
I tried hard but can’t find AUTH file for this model. please please please help me to solve this problem.
Bundle of thanks in advance.
use software download tool (format all + download) @ https://forum.hovatek.com/thread-23709.html to flash the phone.
(20-06-2020, 10:03 AM) Fahad116600 Wrote: Please guide me to flash Infinix x652b. it shows the error STATUS_SEC_AUTH_FILE_NEEDED (0xC0030012) on SP Flash tool
I tried hard but can’t find AUTH file for this model. please please please help me to solve this problem.
Bundle of thanks in advance.
use software download tool (format all + download) @ https://forum.hovatek.com/thread-23709.html to flash the phone.
Hello, Please guide me to flash infinix x652b.. x652a DA file is not working on it.. kindly suggest me any solution for this. Please reply as soon as possible.. thanks in advance.
How To Fix ERROR STATUS SEC AUTH FILE NEEDED on MTK secure Boot device
For some of us who like taking the laws of flashing MTK phones into our hands, this tutorial on how to fix ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012) error and others is for you.
With Mediatek secure devices comes a lot of popular terms and fears. Servicing MTK secure boot devices actually needs care unless you’re like us who want to see the other side of the story first.
The last one is why we are going to stick around here for a while.
If you accidentally formated an MTK secure boot device like Tecno LA7 or an Infininx etc, you will end up not only needing a DA FILE, SP Flashtool will request for an auth file to be able to continue.
These auth/authentication files for MTK devices are very rare and almost impossible to get for every device out there.
So, this is a short guide to help you fix a dead MTK secure boot device after bricking it by formating the device.
The ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012) error is shown when you format a secured boot MTK device.
Newer MTK chipsets come with more security and these kinda give issues if done without care.
So, if you get error related auth file for SP Flashtool, this could be your lucky day.
To make this as simple as possible, we wouldn’t complicate the steps.
This tutorial will work for your MTK devices that are completely dead after formating with any tool, Miracle box, SP Flash tool, NCK etc.
How to Fix ERROR STATUS SEC AUTH FILE NEEDED on MTK secure Boot device
You can now happily disconnect your bricked MTK device and charge it or power it on if it was charged.
Note, you don’t need a DA file or Auth file to get this to work.
After this, you will need to repair/write back the IMEI on the secured boot MTK device using this tutorial. You can check the IMEI using *#06# to confirm.
If you are facing any issues, just drop a comment.
So what’s all this talk about Mediatek Secure Boot and DA files?
The stone the builders neglected has become the cornerstone. That’s how best I can summarize the DA file crisis we now face.
You’d probably not really noticed the Download-Agent section in your favorite Mediatek (MTK) flash tool but with the way things are going, its becoming a critical determinant of whether or not whatever you’re trying to do halts abruptly or proceeds.
What’s this Secure Boot and how does a DA file fit into the equation?
DA is an abbreviation of Download Agent. The DA is what enables whatever Mediatek tool you’re using read or write to the device in Flash Mode (powered off and sometimes holding volume buttons).
A Mediatek device which has Secure Boot won’t allow any tool read from or write to it without a custom DA file loaded to the tool. In other words, no backup, flash, FRP, IMEI write etc without a custom DA. A DA file is thus like a key and the Scatter file like a map.
The Secure Boot issue has been around for a while (my earliest encounters were with Tecno M3S & Acer B1-770; both Lollipop devices) and has increasingly been adopted in Mediatek devices. When trying to interact with a Secure Boot MTK smartphone without the required DA file, you might encounter errors like:
…and the list goes on. For such devices, you’ll need a DA file.
Important things to note when dealing with a Secure Boot MTK device
When handling a Secure Boot MTK device, these are some things you should have at the back of your mind:
Where can I get a Secure Boot DA file for my device / model
Team Hovatek started a Mediatek (MTK) Secure Boot DA file collection. We’ll keep updating the list. Its a community effort so please don’t leave all the work to us. Send us any confirmed DA file not on our list and it could help someone.
How do I use the DA file after downloading it?
We’d dropped a video explaining how to load the DA file in SP Flash tool, NCK box and Infinity CM2 box.
The idea is just to locate the Download Agent section in the tool and load your custom DA. If you have trouble loading it in other tools then drop a comment and I’ll be happy to guide you.
Transsion (Tecno, Infinix and Itel) device users can use Software Download (Transsion Aftersale tool) on Secure Boot devices because they wouldn’t need to load a DA or Auth file for flashing.
Error status sec auth file needed 0xc0030012 как исправить ошибку
READ INFO OF THE DEVICE
Operation : Identify [ v2.03 ]
SRAM: 0x00040000 [ 256.00 KB ]
DRAM: 0x80000000 [ 2.00 GB ]
EMMC: 150100474536424D420346E6DCAC85ED
EMMC: VEN : SAMSUNG | OEM : 01 | DEV : GE6BMB
EMMC:
BOOT1 : 0x00400000 [ 4.00 MB ]
BOOT2 : 0x00400000 [ 4.00 MB ]
RPMB : 0x00400000 [ 4.00 MB ]
USER : 0x3A3E00000 [ 14.56 GB ]
DA : USB : HIGH-SPEED
Patch Level : O11019
Display ID : LA7-H393A-O-181011V172
Ver. CodeName : REL
Ver. Release : 8.1.0
Sec. Patch : 2018-09-05
Build Time : 1539251516
Product Brand : TECNO
Product Manfct : TECNO MOBILE LIMITED
Product Model : TECNO LA7
Product Device : TECNO-LA7
Product Name : H393
Product Info : TECNO-LA7
Board Platform : mt6739
THIS IS THE FILE I USED FOR FLASHING
Operation : Write Flash [ v2.03 ]
Repartition : Enabled
Flash Verify : Disabled
Reg.Pre-Erase : Disabled
Verify HW/SW : Enabled
SData Backup : Disabled
Safe UserData : Disabled
Files :18
[FL] : Set : recovery-verified.img
[FL] : Set : md1img-verified.img
[FL] : Set : md1dsp-verified.img
[FL] : Set : spmfw-verified.img
[FL] : Set : mcupmfw-verified.img
[FL] : Set : lk-verified.img
[FL] : Set : lk-verified.img
[FL] : Set : loader_ext-verified.img
[FL] : Set : loader_ext-verified.img
[FL] : Set : boot-verified.img
[FL] : Set : logo-verified.bin
[FL] : Set : odmdtbo-verified.img
[FL] : Set : tee-verified.img
[FL] : Set : tee-verified.img
[FL] : Set : vendor.img
[FL] : Set : system.img
[FL] : Set : cache.img
[FL] : Set : userdata.img
[FL] : Total size : 0xB2812F94 [ 2.79 GB ]
SRAM: 0x00040000 [ 256.00 KB ]
DRAM: 0x80000000 [ 2.00 GB ]
EMMC: 150100474536424D420346E6DCAC85ED
EMMC: VEN : SAMSUNG | OEM : 01 | DEV : GE6BMB
EMMC:
BOOT1 : 0x00400000 [ 4.00 MB ]
BOOT2 : 0x00400000 [ 4.00 MB ]
RPMB : 0x00400000 [ 4.00 MB ]
USER : 0x3A3E00000 [ 14.56 GB ]
DA : USB : HIGH-SPEED
[FL] : HW verification passed!
SEC_DL : False (RAPHAEL)
OK
SEC_ID : 0x494E46494E495459424F584245535432
[FL] : RePartition
[FL] : RePartition Ok!
Write : RECOVERY
Write : MD1IMG
Write : MD1DSP
Write : SPMFW
Write : MCUPMFW
Write : LK
Write : LK2
Write : LOADER_EXT1
Write : LOADER_EXT2
Write : BOOT
Write : LOGO
Write : ODMDTBO
Write : TEE1
Write : TEE2
Write : VENDOR
Write : SYSTEM
Write : CACHE
Write : USERDATA
SEC_DL : False (RAPHAEL)
OK
SEC_ID : 0x494E46494E495459424F584245535432
[FL] : RePartition
[FL] : RePartition Ok!
[FL] : Flashing finished!
Done!
Elapsed: 00:02:57
DEAD BRICK AFTER FLASH
i was having the real file but i used the information from read and this device is a kind of confusing with LA7 and LA7 PRO
I have this firmware already
TECNO LA7_Pro 16+3 A2_MT6739_8.1.0__LA7-H393A-O-13M-180719V89
but i will need a good checksum file to restore it back to life without AUTH file
this is the CHECKSUM info
F:\WORK\FLASH\TECNO\TECNO LA7_Pro 16+3 A2_MT6739_8.1.0__LA7-H393A-O-13M-180719V8
9\CheckSum_Gen.exe F:\WORK\FLASH\TECNO\TECNO LA7_Pro 16+3 A2_MT6739_8.1.0__LA7-H
393A-O-13M-180719V89
Check Check Generate begin.
Bin File is From Path: F:\WORK\FLASH\TECNO\TECNO LA7_Pro 16+3 A2_MT6739_8.1
.0__LA7-H393A-O-13M-180719V89
CheckSum.ini is write to : F:\WORK\FLASH\TECNO\TECNO LA7_Pro 16+3 A2_MT6739_8.1
.0__LA7-H393A-O-13M-180719V89
SearchFile. preloader
preloader_la7_h393.bin is found;
preloader_la7_h393.bin is Calc_Checksum
Global File size: 117868 Buffer size: 117868.
preloader_la7_h393.bin is Append to List.
SearchFile. DSP_BL
DSP_BL is not found;
SearchFile. uboot
uboot is not found;
SearchFile. lk.bin
lk.bin is found;
lk.bin is Calc_Checksum
Global File size: 502752 Buffer size: 502752.
lk.bin is Append to List.
SearchFile. logo.bin
logo.bin is found;
logo.bin is Calc_Checksum
Global File size: 1030304 Buffer size: 1030304.
logo.bin is Append to List.
SearchFile. boot.img
boot.img is found;
boot.img is Calc_Checksum
Global File size: 8434592
fu_checksum_by_package is : 0x00007395
boot.img is Append to List.
SearchFile. recovery.img
recovery.img is found;
recovery.img is Calc_Checksum
Global File size: 13083552
fu_checksum_by_package is : 0x0000609d
recovery.img is Append to List.
SearchFile. secro.img
secro.img is not found;
SearchFile. system.img
system.img is found;
system.img is Calc_Checksum
Global File size: 1791896448
fu_checksum_by_package is : 0x000042f0
system.img is Append to List.
SearchFile. userdata.img
userdata.img is found;
userdata.img is Calc_Checksum
Global File size: 139593976
fu_checksum_by_package is : 0x00006a35
userdata.img is Append to List.
SearchFile. PRO_INFO
PRO_INFO is not found;