FreezingCold has quit [Remote host closed the connection]
FreezingCold has joined #linux-rockchip
fenixfunk has quit [Ping timeout: 240 seconds]
Astralix1 has joined #linux-rockchip
Astralix has quit [Ping timeout: 252 seconds]
cnxsoft has joined #linux-rockchip
bobl has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
irsol has quit [Ping timeout: 250 seconds]
irsol has joined #linux-rockchip
_massi_ has joined #linux-rockchip
theskilledworker has joined #linux-rockchip
theskilledworker has quit [Changing host]
theskilledworker has joined #linux-rockchip
cityhunter has joined #linux-rockchip
theskilledworker has quit [Ping timeout: 252 seconds]
nighty-_ has joined #linux-rockchip
rz2k has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 276 seconds]
tonikasch has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
FreezingCold has quit [Ping timeout: 265 seconds]
ganbold_ has joined #linux-rockchip
bobl has quit [Ping timeout: 240 seconds]
cityhunter has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
tonikasch has quit [Ping timeout: 255 seconds]
VargaD has quit [Ping timeout: 276 seconds]
rz2k has quit []
VargaD has joined #linux-rockchip
tonikasch has joined #linux-rockchip
jgay has joined #linux-rockchip
bdonnhue has joined #linux-rockchip
<bdonnhue>
is anyone here familiar with the RK3188
cnxsoft has quit [Quit: cnxsoft]
tonikasch has quit [Quit: Bye!]
phh has quit [Quit: No Ping reply in 180 seconds.]
phh has joined #linux-rockchip
_massi_ has quit [Quit: Leaving]
furanshishouco_ has joined #linux-rockchip
<bdonnhue>
hello can anyone help with a brick
<bdonnhue>
my device is stuck in maskrom mode
eebrah|mobile has joined #linux-rockchip
eebrah|mobile has quit [Read error: No route to host]
eebrah_ has joined #linux-rockchip
<bdonnhue>
looks like i have a bad block of memory
eebrah_ has quit [Ping timeout: 252 seconds]
<bdonnhue>
download idb failed
furanshishouco_ has quit [Quit: Page closed]
<Astralix1>
Hi!
<Astralix1>
bdonnhue: If it is stuck in mask ROM mode, you probably killed some important flash info too. So you now need to repeat the normal flash procedure and check the counters on the right side.
<bdonnhue>
Astralix1: thanks for the reply. im new to this whole process so i will be asking some dumb questions before i get familiar.
<Astralix1>
The counter showing the block number where the flash procedure breaks should increment every time you try to flash. So it collects the bad blocks
<Astralix1>
No problem, you're welcomed
<Astralix1>
The only thing you can do is to repeat the flash procedure until it runs through.
<bdonnhue>
one thing im not sure of is the tools being used
<bdonnhue>
ie
<bdonnhue>
rkandroidtool and rkbatchtool
<bdonnhue>
are these both maintained by rockchip?
<Astralix1>
rkandroidtool. The batchtool doesn'r show the secor numbers, or?
<Astralix1>
And yes, both are from RK
<Astralix1>
And these tools have to match the bootloader you flash somehow.
<bdonnhue>
ive downloaded a few versions of the tool and noticed subtle differences between them
<Astralix1>
So you should not try to flash a 2.x bootloader with an old flashtool.
<Astralix1>
What kind of android do you like to flash?
<bdonnhue>
well here is my problem. Im tryng to flash the latest img from timingpower.com for the rk3188 but it fails due to the IDB
<bdonnhue>
it compalins ERROR:PrepareIDB-->No Found 1st Flash CS
<bdonnhue>
(should say prepaerIDB
<Astralix1>
Ouch... How did you enter this flash mode? Did you try the shorting-pin recovery?
<Astralix1>
And what Android had been installed before?
<bdonnhue>
Android 4.2 Jelly Bean
<bdonnhue>
so here is the process of steps:
<bdonnhue>
got the box. plugged it in, it worked, then unplugged and plugged back in... it would not boot. i plug into pc and install drivers and it shows as blue square in batch tool
<Astralix1>
Ok, it is a dead on arrival?
<bdonnhue>
i tried shorting pins but see the same error
<bdonnhue>
no it worked initially
<bdonnhue>
it stopped afet i unplugged it (i think after the second use)
<Astralix1>
Yes, but you did not rty to flash anything when it starts failing?
<bdonnhue>
no i had not. i tried to flash after failure, but the flash fails
<Astralix1>
ok, in that case we have really think about having a bad flash... Cause you did not manipulate the device when it got bricked...
<bdonnhue>
im not sure how to go about recovering
<Astralix1>
Normally the driver of the flash protects the bootloader area. So if your device is in MaskROM mode some really severe has been broken
<bdonnhue>
oh no
<bdonnhue>
do you think it is recoverable?
<Astralix1>
Just one option to try:
<Astralix1>
If you have the rkbatchtool and a recent bootloader in it, 1.2x not 2.xx
<Astralix1>
wait, I check if I have one for you...
<tonikasch>
and the device was bought from the manufacturer so not a clone, I suppose
<Astralix1>
And rkbatchtool 1.7.1 is not the latest, but 1.7.7 the last on the page I sent above
<Astralix1>
For whatever reason, RK needs to update its bootloaders if they add a new flash chip type... I never will understand that as all flash chips have CFI...
<Astralix1>
but I use the linux tools now long time... don't remember every button of the windows tools
<bdonnhue>
they both give the exact same output
<bdonnhue>
blue square turns to red square
<bdonnhue>
if i relauch its back to blue
<Astralix1>
So with what tool now?
<bdonnhue>
this is all with the batch tool
<bdonnhue>
i dont know how to use the other tool
<Astralix1>
Which batchtool? 1.7.1 or one of mine?
<bdonnhue>
the 1.7.7 that you posted
<Astralix1>
So you can try 1.8, but I have not much hope for that
<Astralix1>
Maybe tonikasch has another idea, but we've tried the most recent flash loaders and all fail on identification of the flash chip...
<tonikasch>
no idea, sorry... just thinking, but nothing yet
<bdonnhue>
im looking at good logs (found online) and based on their output it looks like Astralix1 is right and the program cannot identify the flash chip?
<Astralix1>
yes. But this area of the chip cannot be erased, so the chip must be defect, or there is a broken trace on the PCB or a broken soldering point.
<bdonnhue>
what is a broken trace? is that going back to the bad boot loader you mentioned earlier?
<Astralix1>
I mean the thing that connects the RK3188 with the Flash chip on that base board
<bdonnhue>
so any way you slice it im f'ed because im not able to fix hardware
<Astralix1>
If you do not have a soldering iron, heating plate, hot air and a good scope... no
<bdonnhue>
no and also no experience
<Astralix1>
Write them a support reaquest and probably they will do an RMA
<valdur55>
Is a microUSB changing a hard job or not?
<Astralix1>
depends... not for me...
<bdonnhue>
ok maybe ill try that. i reached out to dick chan (the site owner) but havn't heard back
<Astralix1>
keep us updated and good luck, bdonnhue.
<tonikasch>
good luck
<bdonnhue>
thanks everyone!!
<bdonnhue>
will do
<Astralix1>
sorry that there seems no easy solution on that.
<Astralix1>
valdur55, how can we help?
<valdur55>
Astralix1: :D just asking before doing it...
<valdur55>
Maybe i will use microscope for that.
bdonnhue has left #linux-rockchip [#linux-rockchip]
<Astralix1>
Not needed. Most problem is the case that absorbs the heat very fast so you cannot get it off from the PCB
<Astralix1>
especially if you have some notbook PCBs that hav dozends of ground layers inside.
<valdur55>
OK. i use cuprum cable which is covered with flux.
<valdur55>
maybe i don't need resolder it.. it is partly working
<Astralix1>
flux is good, but not too much. Just remove the old plug and solder the case of the new one. Then solder the pins and use some flux and de-soldering cable to fetch the solder that is too much
Astralix1 is now known as Astralix
Astralix has left #linux-rockchip [#linux-rockchip]
Astralix has joined #linux-rockchip
jgay has quit [Quit: Ex-Chat]
nighty-_ has quit [Quit: Disappears in a puff of smoke]
tonikasch has quit [Excess Flood]
ganbold_ has quit [Remote host closed the connection]