miracle box v2.27a
miracle box v2.27a
(31-08-2019, 07:05 PM)benjo73 ...
(31-08-2019, 10:38 PM)X3nonyes and it say the second enumeration port timed out(31-08-2019, 07:05 PM)benjo73 ...
how did you device get bricked? in details
and have you tried flashing the PAC firmware you have using research / upgrade tool? refer to https://www.hovatek.com/forum/thread-1231.html
(01-09-2019, 12:40 AM)benjo73(31-08-2019, 10:38 PM)X3nonyes and it say the second enumeration port timed out(31-08-2019, 07:05 PM)benjo73 ...
how did you device get bricked? in details
and have you tried flashing the PAC firmware you have using research / upgrade tool? refer to https://www.hovatek.com/forum/thread-1231.html
(31-08-2019, 06:30 PM)benjo73 yes i have..i cant open pac file..to see its content
(04-09-2019, 06:56 PM)hovatek(31-08-2019, 06:30 PM)benjo73 yes i have..i cant open pac file..to see its content
This version of miracle box tends to give problems with SPD. Loader versions aren't as stable as when one has the hardware dongle.
on Research Download tool, hope you've installed SPD and have tried both volume up and volume down button when connecting to PC (one should be your boot key)
tried it already..second enumeration port failed tried the fix no fix..it looks like a hardware issue but the problem started on that failed OTA update
(11-09-2019, 08:08 PM)benjo73(04-09-2019, 06:56 PM)hovatektried it already..second enumeration port failed tried the fix no fix..it looks like a hardware issue but the problem started on that failed OTA update(31-08-2019, 06:30 PM)benjo73 yes i have..i cant open pac file..to see its content
This version of miracle box tends to give problems with SPD. Loader versions aren't as stable as when one has the hardware dongle.
on Research Download tool, hope you've installed SPD and have tried both volume up and volume down button when connecting to PC (one should be your boot key)
(11-09-2019, 08:08 PM)benjo73 tried it already..second enumeration port failed tried the fix no fix..it looks like a hardware issue but the problem started on that failed OTA update