We're hiring! Apply Now

Hovatek Forum MOBILE Android [Please help] TECNO Spark 30C KL5 Stuck

[Please help] TECNO Spark 30C KL5 Stuck

[Please help] TECNO Spark 30C KL5 Stuck

Pages (2): 1 2 Next
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 05:05 AM
#1



Context:
I wanted to root my TECNO Spark 30C (KL5), so I looked to how to root it with KernelSU, but I was unsuccessful to install it, after I decided to use Magisk instead. I downloaded my device's stock ROM from this site: https://www.getdroidtips.com/tecno-spark...lash-file/, after downloaded the stock ROM I extracted the boot.img from it, and patched the boot.img with magisk app.

Afterward, I flashed the patched boot.img in fastboot, and rebooted the phone, and the phone booted successfully, and I had rooted access. But whenever I powered up my device, "Orange State" message would appear for a few seconds, I wanted to remove this message. So, I looked up a tutorial online and used a hex editor to edit the lk.img file. After editing the file and removing the Orange State message from, I flashed this edited LK.img in fastboot.

After flashing edited lk.img I rebooted my device with this command: fastboot reboot, but the device didn't reboot, it just sits on a black screen. Now I'm stuck and don't know what to do. How can I restore my device? Btw, the bootloader of the device is unlocked.

PLEASE HELP!
This post was last modified: 28-03-2025, 05:08 AM by AyazAliKhan.
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 05:11 AM
#2
Can someone also provided me with the Official Stock Rom for my device?
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 05:21 AM
#3
I would this guide: https://xdaforums.com/t/guide-remove-ora...s.4613541/, to modify the lk.img file.
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 05:43 AM
#4
I'm trying to follow the MTK Client Guide, but when I run the pip3 install -r requirements.txt in cmd after installing all dependencies, It gives me "failed building wheel for scrypt". How do I solve this issue?
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 08:00 AM
#5



I managed to get MTK Client working but now it keeps saying status: handshake failed retrying
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 08:08 AM
#6
Also, the Mediatek PreLoader VCOM Port keeps appearing and disappearing in the device manager.
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 08:52 AM
#7
I'm following the https://www.hovatek.com/forum/thread-37957.html How to backup / flash a MediaTek (MTK) secure boot device using MTK Bypass Utility guide but the mtk byass utility is stuck at found device.
I've installed usbdk and pyusb & json5. UsbDk Device shows up in other devices in the device manager.
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 09:50 AM
#8
I would also like to remove magisk and restore my phone to default state of locked bootloader and flashing locked and verfied boot restored?
How do I do this?
maxpayne
maxpayne
maxpayne
Intern
4,295
28-03-2025, 11:45 AM
#9
(28-03-2025, 08:00 AM)AyazAliKhan I managed to get MTK Client working but now it keeps saying status: handshake failed retrying

This model would require a paid tool.
Just to be sure we're on the same page, what is device manager detecting the phone as?
Are you able to enter BROM https://www.hovatek.com/blog/how-to-forc...brom-mode/?
This post was last modified: 28-03-2025, 11:45 AM by maxpayne.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
AyazAliKhan
AyazAliKhan
AyazAliKhan
Junior Member
19
28-03-2025, 02:46 PM
#10
The device manager is detecting the phone as MediaTek PreLoader USB VCOM (Android).
I tried using MTK Meta Utility to crash bootloader to brom and it give this output.
Waiting for mtk usb device... ok
BootMode : Preloader[COM4]
DriverDesc : MediaTek PreLoader USB VCOM (Android)
DriverPath : usb\vid_0e8d&pid_2000\5&2bf451f8&0&1
DriverSRV : wdm_usb
DriverVersion : 3.0.1512.0
DriverDate : 1-4-2023
DriverCFG : oem82.inf
DriverOEM : MediaTek Inc.
Connecting to BootROM......
● BRom protocol error: ACK 00 != a0
●●● Log file saved to => D:/Android/Tools/AndroidUtility.v170.0.6677/Logs/2025_03_28_18_42_26.log
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
Join us
WhTlYt