Hovatek Forum MOBILE Android [Please help] Tecno Camon 17 Pro CG8 MT6785 Bootloop and Not Flashing
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


[Please help] Tecno Camon 17 Pro CG8 MT6785 Bootloop and Not Flashing

[Please help] Tecno Camon 17 Pro CG8 MT6785 Bootloop and Not Flashing

Pages (4): Previous 1 2 3 4 Next
Abdulakeem14
Abdulakeem14
Abdulakeem14
Senior Member
1,757
27-12-2021, 06:26 PM
#11



(26-12-2021, 04:07 PM)iamonehood I flashed the empty vbmeta but still It is bootlooping

Also when backing up the rom the user data part took a long time
and still gave errors the user data alone was around 138gb when the error occurred so I have deleted the userdata from the backup rom the rest of the folder is about 8gb

So should I try to flash the hovatek roms with the mtk client
Or there is a way around the boot loop issues

First you need to know your original build no.
Refer to https://www.hovatek.com/forum/thread-16005.html
Method 4
kelvinchinedu
kelvinchinedu
kelvinchinedu
Contributor
1,302
27-12-2021, 06:58 PM
#12
Pls mind u that flashing the ROM gotten from here will format Ur data and imei maybe wipe
Pls first read Ur phone firmware using miracle thunder 2.82 to view Ur imei and write it out somewhere.
Then u can go ahead and write the firmware gotten from here.
(That is  read info from miracle thunder)
This post was last modified: 27-12-2021, 07:00 PM by kelvinchinedu.
iamonehood
iamonehood
iamonehood
Junior Member
22
28-12-2021, 03:39 AM
#13
(27-12-2021, 06:58 PM)kelvinchinedu Pls mind u that flashing the ROM gotten from here will format Ur data and imei maybe wipe
Pls first read Ur phone firmware using miracle thunder 2.82 to view Ur imei and write it out somewhere.
Then u can go ahead and write the firmware gotten from here.
(That is  read info from miracle thunder)

i used the the mtk client to flash the firmwares here but nothing happens 
the same bootloop issues 
if i relock the bootloader with mtk client it gives me red state
boot verification failed something like that -- I should flashed a verified boot  or dissable verification or something
so i unlocked the bootloader again and the orange state is showing now
flashing the firmware  here with mtkclient does nothing to the fon same bootloop
iamonehood
iamonehood
iamonehood
Junior Member
22
28-12-2021, 04:32 AM
#14
(27-12-2021, 06:26 PM)Abdulakeem14
(26-12-2021, 04:07 PM)iamonehood I flashed the empty vbmeta but still It is bootlooping

Also when backing up the rom the user data part took a long time
and still gave errors the user data alone was around 138gb when the error occurred so I have deleted the userdata from the backup rom the rest of the folder is about 8gb

So should I try to flash the hovatek roms with the mtk client
Or there is a way around the boot loop issues

First you need to know your original build no.
Refer to https://www.hovatek.com/forum/thread-16005.html
Method 4

The only Method will be dismantling the phone thus Mother board
Which I can't do right now wwr mtk and miracle 2.28 don't support my fon
Can't go to recovery or factory mode

But I backed up the phone with the mtkclient can I get the build from super, I think super is the system or
Any way I have a picture of the Rom dump check if I can get the build number from there

I'm Attaching the images
Attached Files
.png
b1.PNG
Size: 40.75 KB / Downloads: 13
.png
b2.PNG
Size: 38.24 KB / Downloads: 11
.png
b3.PNG
Size: 21.48 KB / Downloads: 11
hovatek
hovatek
hovatek
Administrator
49,570
29-12-2021, 10:58 AM
#15



(26-12-2021, 04:07 PM)iamonehood I flashed the empty vbmeta but still It is bootlooping

Also when backing up the rom the user data part took a long time
and still gave errors the user data alone was around 138gb when the error occurred so I have deleted the userdata from the backup rom the rest of the folder is about 8gb

So should I try to flash the hovatek roms with the mtk client
Or there is a way around the boot loop issues

We don't really need userdata.
yours is AB so it doesn't have recovery partition.
Upload both boot_a and boot_b from your dump and provide a link.
Hopefully, boot_b hasn't been tampered with and should tell us your original build number
You should also specify what files you flashed to the phone via mtk client
This post was last modified: 29-12-2021, 11:05 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
iamonehood
iamonehood
iamonehood
Junior Member
22
29-12-2021, 06:45 PM
#16
(29-12-2021, 10:58 AM)hovatek
(26-12-2021, 04:07 PM)iamonehood I flashed the empty vbmeta but still It is bootlooping

Also when backing up the rom the user data part took a long time
and still gave errors the user data alone was around 138gb when the error occurred so I have deleted the userdata from the backup rom the rest of the folder is about 8gb

So should I try to flash the hovatek roms with the mtk client
Or there is a way around the boot loop issues

We don't really need userdata.
yours is AB so it doesn't have recovery partition.
Upload both boot_a and boot_b from your dump and provide a link.
Hopefully, boot_b hasn't been tampered with and should tell us your original build number
You should also specify what files you flashed to the phone via mtk client

I checked both boot_a and boot_b
They all have the same fingerprint thus the V537 here
I think the boot command I issued earlier affected both the boot_a and boot_b
Thus,     fastboot flash boot boot.img

I flash the whole firmware folder with the mtk client
The files that have same sectors flash successfully but others give error like those not flash able. I think the mtkclient just skip those files

But is super not the same as system? 
Wanted to unpack the system image then check the build from there but it gives me errors
Is there any other way
This post was last modified: 29-12-2021, 06:48 PM by iamonehood.
hovatek
hovatek
hovatek
Administrator
49,570
30-12-2021, 07:39 AM
#17
(29-12-2021, 06:45 PM)iamonehood I checked both boot_a and boot_b
They all have the same fingerprint thus the V537 here
I think the boot command I issued earlier affected both the boot_a and boot_b
Thus,     fastboot flash boot boot.img

I flash the whole firmware folder with the mtk client
The files that have same sectors flash successfully but others give error like those not flash able. I think the mtkclient just skip those files

But is super not the same as system? 
Wanted to unpack the system image then check the build from there but it gives me errors
Is there any other way

You can use simg2img @ https://androidfilehost.com/?fid=8889791610682868118 to convert to super.raw then unpack using 7zip . You can then unpack system.img if you know how to

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
iamonehood
iamonehood
iamonehood
Junior Member
22
02-01-2022, 04:29 AM
#18
(30-12-2021, 07:39 AM)hovatek
(29-12-2021, 06:45 PM)iamonehood I checked both boot_a and boot_b
They all have the same fingerprint thus the V537 here
I think the boot command I issued earlier affected both the boot_a and boot_b
Thus,     fastboot flash boot boot.img

I flash the whole firmware folder with the mtk client
The files that have same sectors flash successfully but others give error like those not flash able. I think the mtkclient just skip those files

But is super not the same as system? 
Wanted to unpack the system image then check the build from there but it gives me errors
Is there any other way

You can use simg2img @ https://androidfilehost.com/?fid=8889791610682868118 to convert to super.raw then unpack using 7zip . You can then unpack system.img if you know how to

The Build Number is 211012V760

Was able to get the build number by renaming super.bin to super.img
Then using lmjtool to extract the super.img to a folder
Then mounted the system_ext_a.img to a folder then read the build.prob from there
i have attached some screenshot
This post was last modified: 02-01-2022, 04:38 AM by iamonehood.
Attached Files
.png
lmjtool.png
Size: 19.62 KB / Downloads: 9
.png
build.png
Size: 214.12 KB / Downloads: 7
hovatek
hovatek
hovatek
Administrator
49,570
02-01-2022, 08:44 AM
#19
(02-01-2022, 04:29 AM)iamonehood The Build Number is 211012V760

Was able to get the build number by renaming super.bin to super.img
Then using lmjtool to extract the super.img to a folder
Then mounted the system_ext_a.img to a folder then read the build.prob from there
i have attached some screenshot

That would be CG8-H854ABCLM-R-GL-211012V760
That's the firmware you need

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
iamonehood
iamonehood
iamonehood
Junior Member
22
02-01-2022, 11:40 PM
#20



(02-01-2022, 08:44 AM)hovatek
(02-01-2022, 04:29 AM)iamonehood The Build Number is 211012V760

Was able to get the build number by renaming super.bin to super.img
Then using lmjtool to extract the super.img to a folder
Then mounted the system_ext_a.img to a folder then read the build.prob from there
i have attached some screenshot

That would be CG8-H854ABCLM-R-GL-211012V760
That's the firmware you need

Yh I searched saaa couldn't get some online 
So do wild and upload some give me 
Waiting on you as usual
But is there no solution apart from flashing d same build image
Pages (4): Previous 1 2 3 4 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram