[Please help] Infinix Hot Note x551 Not showing boot logo after successfully flashing
[Please help] Infinix Hot Note x551 Not showing boot logo after successfully flashing
(10-10-2018, 03:28 PM)EMMANUS Everything you posted is as they should be.
Maybe you should try another firmware, I will suggest kitkat.
If it still doesn't work, then consider hardware problems.
(10-10-2018, 09:33 PM)Impossiblecrown(10-10-2018, 03:28 PM)EMMANUS Everything you posted is as they should be.
Maybe you should try another firmware, I will suggest kitkat.
If it still doesn't work, then consider hardware problems.
Can you find me a link of a kitkat version for my phone's version & build no? Will appreciate bro
(11-10-2018, 08:07 AM)EMMANUSVery much appreciative(10-10-2018, 09:33 PM)Impossiblecrown(10-10-2018, 03:28 PM)EMMANUS Everything you posted is as they should be.
Maybe you should try another firmware, I will suggest kitkat.
If it still doesn't work, then consider hardware problems.
Can you find me a link of a kitkat version for my phone's version & build no? Will appreciate bro
This is it https://mega.nz/#!vlpECJJL!5MF4-4JvWoemL...VRq7UNkpII
(11-10-2018, 03:43 PM)EMMANUS Please get back with the results.I flashed the kk version but it still has a display malfunction(screen flickering when I press the power button), which am thinking maybe due to an incorrect build number. I have tried researching how to get the right build no. for this device to download the specific stock ROM but nothing so far has gone my way
(11-10-2018, 07:37 PM)Impossiblecrown(11-10-2018, 03:43 PM)EMMANUS Please get back with the results.I flashed the kk version but it still has a display malfunction(screen flickering when I press the power button), which am thinking maybe due to an incorrect build number. I have tried researching how to get the right build no. for this device to download the specific stock ROM but nothing so far has gone my way
(12-10-2018, 12:28 AM)X3nonThank you I'll try once more, incase it doesn't respond the hardware might be the cause. The phone is a 16+1 as indicated in the battery's casing. I will update as soon as possible(11-10-2018, 07:37 PM)Impossiblecrown(11-10-2018, 03:43 PM)EMMANUS Please get back with the results.I flashed the kk version but it still has a display malfunction(screen flickering when I press the power button), which am thinking maybe due to an incorrect build number. I have tried researching how to get the right build no. for this device to download the specific stock ROM but nothing so far has gone my way
the both firmware's you've flashed are for 16+1, unless phone really isn't 16+1 [e.g the PCB is 16+2 or 32+2 while the casing or sticker on the battery is that of 16+1]
you can try flashing only lk.bin of 16+2 and 32+2 roms at https://www.hovatek.com/forum/thread-19977.html
if you flash lk.bin from the other two variants and screen isn't fixed then you'll need to consider faulty hardware
(12-10-2018, 11:09 AM)Impossiblecrown(12-10-2018, 12:28 AM)X3nonThank you I'll try once more, incase it doesn't respond the hardware might be the cause. The phone is a 16+1 as indicated in the battery's casing. I will update as soon as possible(11-10-2018, 07:37 PM)Impossiblecrown(11-10-2018, 03:43 PM)EMMANUS Please get back with the results.I flashed the kk version but it still has a display malfunction(screen flickering when I press the power button), which am thinking maybe due to an incorrect build number. I have tried researching how to get the right build no. for this device to download the specific stock ROM but nothing so far has gone my way
the both firmware's you've flashed are for 16+1, unless phone really isn't 16+1 [e.g the PCB is 16+2 or 32+2 while the casing or sticker on the battery is that of 16+1]
you can try flashing only lk.bin of 16+2 and 32+2 roms at https://www.hovatek.com/forum/thread-19977.html
if you flash lk.bin from the other two variants and screen isn't fixed then you'll need to consider faulty hardware
(12-10-2018, 11:09 AM)Impossiblecrown Thank you I'll try once more, incase it doesn't respond the hardware might be the cause. The phone is a 16+1 as indicated in the battery's casing. I will update as soon as possible