Hovatek Forum MOBILE Android Bricked Infinix Hot 10S
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


Bricked Infinix Hot 10S

Bricked Infinix Hot 10S

HAWKIND
HAWKIND
HAWKIND
Newbie
3
05-08-2021, 03:09 PM
#1



While trying to root my Infinix Hot 10S device i flashed the empty vbmeta.img and magisk patched boot.img with fastboot and then i rebooted the phone now the phone is stuck in bootloop it just reboots constantly i have tried to flash the firmware with SP Flash Tool but i receive the following error:


ERROR: STATUS_BROM_CMD_SEND_DA_FAIL(0xC0060003) [See attached Screenshot]

I have tried with diffrent laptops it gives the same error everywhere tried a few diffrent drivers and tried SWD Aftersales software too same error there too.

Today i stumbled upon the mtk bypass tool method i tried it and got the following result:

PS C:\Users\Ankit\Desktop\bypass_utility-master> python3 main.py
[2021-08-05 19:17:49.529024] Waiting for device
[2021-08-05 19:18:14.059159] Found port = COM1

[2021-08-05 19:18:14.440233] Device hw code: 0x707
[2021-08-05 19:18:14.440233] Device hw sub code: 0x8a00
[2021-08-05 19:18:14.441222] Device hw version: 0xca00
[2021-08-05 19:18:14.442225] Device sw version: 0x0
[2021-08-05 19:18:14.457065] Device secure boot: True
[2021-08-05 19:18:14.457065] Device serial link authorization: False
[2021-08-05 19:18:14.458065] Device download agent authorization: True


[2021-08-05 19:18:14.458690] Found device in preloader mode, trying to crash...

[2021-08-05 19:18:14.461585] status is 7024

[2021-08-05 19:18:14.469088] Waiting for device

I googled it and found a another person also had the same issue developer replied that the device is in preloader mode but it needs to be in bootrom mode.I tried googling about bootrom mode and how to get into it but didn't find any satisfactory result.

Apparently infinix needs you to go through recovery to go into fastboot mode there is no direct key combination but recovery is also not opening when i press the key combination to go into recovery mode device's screen stays on and it is detected as adb composite device in device manager and no other adb command works expect adb devices all other commands give this error:

adbd F 07-29 15:30:18 333 333 shell_service.cpp:380] Could not set SELinux context for subprocess
libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 333 (adbd), pid 333 (adbd)

Here is some more info:-
(1)The device runs on android 11.
(2)SP flash tool detects the device as mt6768.
(3)I have unlocked the bootloader already.

So please tell me what can i do to fix the device any help will be greatly appreciated.
Attached Files
.png
Screenshot (14).png
Size: 142.59 KB / Downloads: 4
HAWKIND
HAWKIND
HAWKIND
Newbie
3
05-08-2021, 04:00 PM
#2
Ok guys a update i pressed the volume key when rebooting phone and mtk bypass tool method worked and i successfully flashed the firmware but now when i reboot the phone it shows a blank screen no logo(unlike before) no nothing and is detected as android composite adb interface so any idea where can i go from here?
X3non
X3non
X3non
Recognized Contributor
22,062
06-08-2021, 10:43 AM
#3
(05-08-2021, 04:00 PM)HAWKIND Ok guys a update i pressed the volume key when rebooting phone and mtk bypass tool method worked and i successfully flashed the firmware but now when i reboot the phone it shows a blank screen no logo(unlike before) no nothing and is detected as android composite adb interface so any idea where can i go from here?

do you remember the build number of your device before you flashed it? and the build number of the firmware you flashed?
where did you get the firmware from?
HAWKIND
HAWKIND
HAWKIND
Newbie
3
07-08-2021, 12:37 PM
#4
(06-08-2021, 10:43 AM)X3non
(05-08-2021, 04:00 PM)HAWKIND Ok guys a update i pressed the volume key when rebooting phone and mtk bypass tool method worked and i successfully flashed the firmware but now when i reboot the phone it shows a blank screen no logo(unlike before) no nothing and is detected as android composite adb interface so any idea where can i go from here?

do you remember the build number of your device before you flashed it? and the build number of the firmware you flashed?
where did you get the firmware from?

Nevermind the firmware was wrong there were three firmwares listed on the website i tried the first two they didn't work so i tried the last one yesterday and it worked after booting imei was invalid so i used the maui meta tool to flash imei and now my device is as good as new and btw all this apparently started because i patched the boot.img from one of those two wrong firmwares :p. Thanks to this website and hovatek team! I found all the tools and tutorials here which helped me fix the device.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram