Hovatek Forum DEVELOPMENT Android Did I do something wrong while flashing TWRP from Hovatek's TWRP Online Builder?
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Did I do something wrong while flashing TWRP from Hovatek's TWRP Online Builder?

Did I do something wrong while flashing TWRP from Hovatek's TWRP Online Builder?

c_xrsed
c_xrsed
c_xrsed
Newbie
3
14-04-2024, 08:17 PM
#1



I'm using TECNO Camon 18, recently rooted it thanks to the guide from Hovatek forum. I used my backup boot.img to create TWRP with builder provided on the Hovatek site, unfortunately, it ended up hard bricking my phone. I managed to unbrick my phone later on but I was wondering, did I make a mistake by doing the following:

The boot.img I created using the TWRP Online Builder, I renamed it to twrp.img when i flashed it, thinking maybe that was the cause of hard brick since initially boot file should be named boot.img

I was thinking about retrying to make TWRP using Hovatek's TWRP Builder but I'm unsure of it because of the hard brick, so I wanted to consult with anyone if naming the boot file anything else but boot.img will lead to bricking phone.
hovatek
hovatek
hovatek
Administrator
49,597
15-04-2024, 10:29 AM
#2
(14-04-2024, 08:17 PM)c_xrsed I'm using TECNO Camon 18, recently rooted it thanks to the guide from Hovatek forum. I used my backup boot.img to create TWRP with builder provided on the Hovatek site, unfortunately, it ended up hard bricking my phone. I managed to unbrick my phone later on but I was wondering, did I make a mistake by doing the following:

The boot.img I created using the TWRP Online Builder, I renamed it to twrp.img when i flashed it, thinking maybe that was the cause of hard brick since initially boot file should be named boot.img

I was thinking about retrying to make TWRP using Hovatek's TWRP Builder but I'm unsure of it because of the hard brick, so I wanted to consult with anyone if naming the boot file anything else but boot.img will lead to bricking phone.

Since you're rooted, verified boot shouldn't be the problem.

try booting the twrp instead

Code:

fastboot boot boot.img

it would help to know what you mean by hard brick. How did the phone behave?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
c_xrsed
c_xrsed
c_xrsed
Newbie
3
15-04-2024, 08:23 PM
#3
(15-04-2024, 10:29 AM)hovatek
(14-04-2024, 08:17 PM)c_xrsed I'm using TECNO Camon 18, recently rooted it thanks to the guide from Hovatek forum. I used my backup boot.img to create TWRP with builder provided on the Hovatek site, unfortunately, it ended up hard bricking my phone. I managed to unbrick my phone later on but I was wondering, did I make a mistake by doing the following:

The boot.img I created using the TWRP Online Builder, I renamed it to twrp.img when i flashed it, thinking maybe that was the cause of hard brick since initially boot file should be named boot.img

I was thinking about retrying to make TWRP using Hovatek's TWRP Builder but I'm unsure of it because of the hard brick, so I wanted to consult with anyone if naming the boot file anything else but boot.img will lead to bricking phone.

Since you're rooted, verified boot shouldn't be the problem.

try booting the twrp instead

Code:

fastboot boot boot.img

it would help to know what you mean by hard brick. How did the phone behave?

I will try booting instead of flashing once I have available PC to run a test on, thank You for advice.

My phone wasn't showing any signs of being operable; holding power button or combination of power button with volume buttons didn't cause my phone to vibrate and I was left with black screen. Windows didn't seem to recognize my phone either but after I left my phone to lose it's battery completely I was able to enter BROM again since it stopped trying to boot into corrupt boot partiton.
c_xrsed
c_xrsed
c_xrsed
Newbie
3
16-04-2024, 11:34 AM
#4
I will try and use command instead of flashing boot.img, thank You for the advice!

By hard brick I meant my phone wasn't responding to power button nor power button with any volume button combination (power button didn't even cause phone to vibrate). After I left phone to completely run out of battery I was able to enter BROM and flash stock boot.img I have backed up during the process of patching magisk on the same backup boot.img.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram