Hovatek
  • Private Support
  • Blog
  • Home
Login Register Ask Question Hello There, Guest!
Login
Username:
Password: Lost Password?
 

OR

       

Hovatek is hiring: Application is open to residents of Lagos, Nigeria only! Click Here To Apply
Telegram Channel: Join the discussions @ t.me/Hovatek


  1. Hovatek Forum
  2. MOBILE PHONES HELP SECTION
  3. Android
 
Thread Rating:
  • 0 Vote(s) - 0 Average

Thread Modes

[Please help] Bricked Cubot J5

odelind
Newbie
Posts: 2
Threads: 1
Joined: Aug 2020
Reputation: 0
#1

11-08-2020, 11:49 PM


Hello,

I bought a Cubot J5 as a gift from someone else (not too used to smartphones). After a few days the phone was having troubles and, due recommendation of the seller, I was told to update it via sp flashtools (everything downloaded via the official site cubot.net). I tried to do so but the remedy was worse than the disease and I ended bricking the phone. 

Right now the phone doesn't turn on or react in any way, not even charging (I doubt it have battery at this point), but the SP Flashtools can still interact with the phone. 

There are two errors, 6128 and 1041. The first one is theoretically fixed by ticking two options related to the checksum in the Download section but by doing so, the second error appears instead. The solution for this should be delete the checksum.ini file, which doesn't get generated (or at least I can't find it) and untick the two options within Downloads, which causes the error 6128 again. 

I did a memory test and got two errors: 

-NAND flash not detected
-UFS not detected


I also tried to format without bootloader but didn't seem to change the result.


Is there a way to make it functional again? I don't mind if I have to leave it blank and root it or something. I don't know much about these things and just can't afford another phone right now. 

Thank you in advance.

Find
Reply
X3non
Hovatek Representative
Posts: 18,416
Threads: 550
Joined: Jul 2014
Reputation: 326
#2

12-08-2020, 09:27 AM
(11-08-2020, 11:49 PM)odelind Wrote:  ...
I tried to do so but the remedy was worse than the disease and I ended bricking the phone. 

i take it that the flashing attempt got the phone dead, did you get to successfully flash the firmware or it failed with an error? before the phone went totally dead


(11-08-2020, 11:49 PM)odelind Wrote:  I did a memory test and got two errors: 
...

these really are not errors, the device doesn't use nand or ufs storage, rather emmc


(11-08-2020, 11:49 PM)odelind Wrote:  Is there a way to make it functional again? I don't mind if I have to leave it blank and root it or something. I don't know much about these things and just can't afford another phone right now. ...

you can try generating checksum.ini for the firmware then retry flashing ; see https://forum.hovatek.com/thread-23301.html
Find
Reply
odelind
Newbie
Posts: 2
Threads: 1
Joined: Aug 2020
Reputation: 0
#3

12-08-2020, 07:18 PM
If I recalled properly, the error was failed to get PMT info or something related to that. Sadly, I forgot to take an screenshot and can't remember exactly. 

I'll try the checksum solution you gave me and post the results.

Edit 1: I read somewhere else that if the drivers arent installed properly that might cause the problem. I just checked the device manager and found yellow triangles over the drivers. I tried to reinstalled it but no results, if that might be the cause, what can I do?

Edit 2: Tried to Checksum generator, but still got the loop between 6128 and 1041.
(This post was last modified: 12-08-2020, 07:57 PM by odelind.)
Find
Reply
X3non
Hovatek Representative
Posts: 18,416
Threads: 550
Joined: Jul 2014
Reputation: 326
#4

15-08-2020, 10:17 AM
(12-08-2020, 07:18 PM)odelind Wrote:  If I recalled properly, the error was failed to get PMT info or something related to that. Sadly, I forgot to take an screenshot and can't remember exactly. 

if the first flash that resulted in a dead phone was a failed attempt then take out / reinsert the battery, this should get the device back to the previous state it was assuming you didn't select the option to "format" in spft


(12-08-2020, 07:18 PM)odelind Wrote:  Edit 1: I read somewhere else that if the drivers arent installed properly that might cause the problem. I just checked the device manager and found yellow triangles over the drivers. I tried to reinstalled it but no results, if that might be the cause, what can I do?

yellow triangle on driver indicates that it's an unsigned driver, not that the driver doesn't work
you can always test the driver, open device manager > connect the phone while its switched off and check if it gets detected


(12-08-2020, 07:18 PM)odelind Wrote:  Edit 2: Tried to Checksum generator, but still got the loop between 6128 and 1041.

try using a different firmware build and specified flash tool @ http://forum.cubot.net/viewtopic.php?f=2...b1c1134f91 OR https://www.cubot.net/platform/Support/d...id/15.html
Find
Reply
« Next Oldest | Next Newest »

Share

Share Tweet Share Share Pin


Possibly Related Threads…
Thread / Author Replies Views Last Post
Cubot x19 S
AdiE
33
2,025
Last Post by AdiE
23-05-2020, 10:29 AM
TWRP for Cubot hafury a7
braca999
31
2,265
Last Post by X3non
08-05-2020, 10:11 AM
Cubot x18 plus bricked
AroArijan
2
694
Last Post by AroArijan
19-06-2019, 01:32 PM
Cubot note plus deadboot unresponsive
Tolani.okus
6
1,076
Last Post by Tolani.okus
02-06-2019, 07:16 PM
Bootlooping Cubot Power
madis121
6
1,427
Last Post by madis121
26-02-2019, 12:08 PM

  • View a Printable Version


Users browsing this thread: 1 Guest(s)
  1. Hovatek Forum
  2. MOBILE PHONES HELP SECTION
  3. Android

About

The Hovatek Forum is a free Tech. Support Forum. We provide solutions to all your device related problems and questions. We'll love to have you participate in discussions here whether you're a Newbie or Experienced.

         

Forum Team

Powered By MyBB. Crafted by EreeCorp.




Linear Mode
Threaded Mode