<wltjr>
I definitely have my device in a better state, I can flash the various stuff now, boot.img, recovery.img, etc
<t445>
I got a third hand tablet that somehow got into a boot loop. And I can't find the stock firmware for it. Just found one that *might* work and Im flashing it right now...
<wltjr>
well I can flash boot not the others :P but more than I could before
<wltjr>
t445: what is the tablet
<t445>
maybe some sacrifice for the firmware gods is in otder?
<t445>
order
<t445>
the thing is called "playtab"
<t445>
(hmm - it seems to be booting just now - at least I got the stupid android splash screen)
<t445>
Well, at least I can tell you that upgrade_tool automatically reboots the target after upgrading. It just did here.
<wltjr>
t445: that is good to know, so I must still be having some issues
<wltjr>
t445: what did you flash an upgrade.img?
<t445>
yes
<wltjr>
t445: ok must be issues with mine, let me see if I can locate a premade one
<wltjr>
t445: got a link to yours? can't really mess this up any more, completely different device but if I can get back to cwm or some recovery I can go from there
<t445>
mine uses the 312A chip, which I think it's also known as 3126
<wltjr>
t445: ah yes no go I need a rk3188 based update.img :)
<t445>
so the damned android just booted and it switched to the 'correct' local language - spanish
<t445>
scary
arnd has quit [Ping timeout: 240 seconds]
arnd has joined #linux-rockchip
dlezcano has quit [Ping timeout: 240 seconds]
fungi has quit [Ping timeout: 240 seconds]
nighty has joined #linux-rockchip
dlezcano has joined #linux-rockchip
fungi has joined #linux-rockchip
<wltjr>
goal :) recovered back into cwm :)
<t445>
congrats =)
<wltjr>
t445: I realized I did not use the right parameters file
<t445>
hehe =)
<wltjr>
also needed correct loader version
<wltjr>
now if I want to try to repeat back to cm12.1/5.1.1.... :P
<wltjr>
least I can recover now
<wltjr>
good learning process and I am quite pleased I never had to use windows though lost a great deal of time, however in the future I will regain that by not having to use windows :)
* wltjr
note to self do not wipe data after restore backup...
<wltjr>
habit from flashing firmware where I sometimes forgot... now do it excessively even when I do not want to... restoring again...
<t445>
would using windows had made any difference?
<t445>
apart from the disgust caused by using windows that is =P
<wltjr>
yes would have saved me hours
<wltjr>
I would not have needed to make an update.img, just allow the rocktool software to do that itself
<wltjr>
android has always had this odd history of most tools being windows based...
<wltjr>
I had to use windows to reflash my S7, and samsung has become very rom/root unfriendly
<wltjr>
heimdall will flash boot.img and maybe some others but not system.img it fails at the very end
<t445>
as far as I can tell the rockchip flashing tools do the same thing in either windows or linux
<wltjr>
think signature verification or something the samsung software does its own
<wltjr>
yes it seems to be the case, basically creates an update.img and flashes that
<t445>
I took a quick look at the usb protocol in the rkflashkit python source and it seems rather simple
<wltjr>
t445: but update_tool is missing the rest, afptool and img_maker, I tried another set of those from the crew rktablets but they did not work, just the ones from rockchip-pack-tools from radxa
<wltjr>
radxa has some really good docs on rk stuff
<t445>
ah, I haven't looked into packing an img file yet
<wltjr>
t445: I have played with it, and used the simg2img tool for the signed ones
<t445>
...on the other hand, my tablet is not showing up in linux's adb =/
<wltjr>
well I am happy can go eat and get back to playing with stuff :)
<t445>
haha
<wltjr>
t445: doyou get the ???? or anything? may need to enble usb debugging and stuff
<t445>
I enabled usb debugging
<wltjr>
havent used this thing in years would suck to have messed it up
<t445>
table even says "usb debuggng connected"
<t445>
tablet
<wltjr>
t445: does it show under lsusb?
<t445>
anyway, gonna try it on....windows haha
<t445>
yes
<t445>
2207:0010
<wltjr>
t445: adb not showing anything or saying waiting for devices?
<t445>
the server started
<wltjr>
t445: your close if its shows under usb should not have need for windows
<t445>
but the list is empty
<t445>
weird
<wltjr>
t445: there is some reason its been a long time, but if it shows under lsusb your close
<t445>
linux sees it, and usb dgb is enabled on the tablet - should be working but it isnt =P
<t445>
anyway, got to go now
<t445>
nice chatting with you
<t445>
laterz
t445 has quit [Quit: Leaving]
<wltjr>
t445: gl c ya
t445 has joined #linux-rockchip
<t445>
...so on my linux I had to add the line 0x2207 to ~/.android/adb_usb.ini
<t445>
if the vendor id is not liste there, adb doesn't list the device...
<stdint>
btw, do you find a way to enter into maskrom
<t445>
me?
<stdint>
in my memory, the rockchip would always have a maskrom, it would be more easy for you guys
<stdint>
to flash a new system
cnxsoft has joined #linux-rockchip
<t445>
I finally managed to put a working android firmware on my tablet - I think I used the maskrom bootloader - isn't that the one that's working when the screen is black?
<stdint>
not understand what you mean, but maskrom is a iROM, a rom in chip internally
<t445>
yes
<t445>
I thought you were talking about the bootloader inside that maskrom
<t445>
that maskrom loader makes it easy to flash new systems, is that what you mean?
<t445>
...so, I'm still trying to figure out what kind of linux I can put on this thing?
<stdint>
t445, if you could open the box and take a photo of the SoC
<stdint>
it would be more easily to know which model of SoC it used
<stdint>
the maskrom could load the image from PC host through USB
<t445>
stdint I'm fairly sure the SoC is a 312A
<stdint>
also it would be the first bootloader at booting
<t445>
aka 3126 I think
<stdint>
t445, yes, I know, but rkflashtool's message is hard to understand
<stdint>
the rk3338 would be RK330C
<stdint>
could you find any relation between them?
<t445>
you mean, RK330C is what's printed on the chip?
<t445>
stdint I'm not sure what you mean - I can't even find a rk3338 SoC
<stdint>
sorry, typo, rk3399
<stdint>
t445, I mean that it is hard to know the correct chip model from rkflashtool's report
<t445>
because it can't be trusted?
<t445>
I thought the rkflashtool sends a command to the chip and the chip answers with its own id
<stdint>
not, just I don't know what it actually means
<t445>
anyway In my case it said 312A, I flashed an android firmware for 3126 and it workded, so in this case rkflashtool seems to have gotten it right
<stdint>
let me phone somebody for help
tizbac has quit [Ping timeout: 240 seconds]
tizbac has joined #linux-rockchip
tizbac has quit [Ping timeout: 240 seconds]
tizbac has joined #linux-rockchip
indy has joined #linux-rockchip
t445 has quit [Quit: Leaving]
premoboss has joined #linux-rockchip
maz has joined #linux-rockchip
maz has quit [Read error: Connection reset by peer]
maz has joined #linux-rockchip
maz has quit [Read error: Connection reset by peer]
dlezcano has quit [Ping timeout: 260 seconds]
dlezcano has joined #linux-rockchip
nighty has quit [Quit: Disappears in a puff of smoke]
rperier has quit [Remote host closed the connection]
rperier has joined #linux-rockchip
rperier has quit [Remote host closed the connection]
rperier has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
rperier has quit [Remote host closed the connection]
rperier has joined #linux-rockchip
nighty has joined #linux-rockchip
dlezcano has quit [Remote host closed the connection]
dlezcano has joined #linux-rockchip
premoboss has quit [Ping timeout: 260 seconds]
dlezcano has quit [Remote host closed the connection]
mrjay has joined #linux-rockchip
lorenzo64 has joined #linux-rockchip
mrjay has quit [Quit: Page closed]
premoboss has joined #linux-rockchip
paulk-minnie has joined #linux-rockchip
dlezcano has joined #linux-rockchip
paulk-minnie has quit [Read error: Connection reset by peer]
cnxsoft has quit [Quit: cnxsoft]
maz has joined #linux-rockchip
maz has quit [Read error: Connection reset by peer]
maz has joined #linux-rockchip
maz has quit [Read error: Connection reset by peer]
jkstrick has joined #linux-rockchip
jkstrick has quit [Remote host closed the connection]
jkstrick has joined #linux-rockchip
premoboss has quit [Ping timeout: 250 seconds]
paulk-collins has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
srao has quit [Read error: Connection reset by peer]
srao has joined #linux-rockchip
premoboss has joined #linux-rockchip
vagrantc has joined #linux-rockchip
norris has quit [Ping timeout: 258 seconds]
norris has joined #linux-rockchip
paulk-collins has quit [Remote host closed the connection]
premoboss has quit [Ping timeout: 250 seconds]
t445 has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Remote host closed the connection]