<oliv3r>
(i don't wanna do a heimdal flash yet) but none of the images i download will 'upgrade'
<oliv3r>
it just gets stuck in recovery mode
<oliv3r>
(without screen)
<oliv3r>
unless the auto-updater runs from recovery and I wasn't patient enough; but i suppose adb reboot woul deither fail, or break the entire phone :)
<geecko>
oliv3r, reboot anyway
<geecko>
it updates from the recovery
<geecko>
but it should be displaying something
<oliv3r>
well display is broken :p
<oliv3r>
i know normally you get the little android with the open belly
<oliv3r>
i can adb shell in
<oliv3r>
how do I know whether it really is updating?
<geecko>
so it loads the blobs without problems, and then...
<oliv3r>
geecko: /sbin/recovery is idling at 20-30% cpu usage; so i'll just wait it out for about 15 minutes?
<geecko>
oliv3r, waiting more than 10 minutes from now is a waste of time
<oliv3r>
nothing is mounted though
<oliv3r>
i would think that the updater would mount partitions containing files?
<paulk-collins_>
oliv3r, yes it should
<oliv3r>
so that's why it's not updating ;)
<oliv3r>
would hdmi out work with CWM?
xplodwild has quit [Quit: No Ping reply in 240 seconds.]
<paulk-collins_>
I doubt it
<paulk-collins_>
CWM uses bare framebuffer
xplodwild has joined #teamhacksung
<oliv3r>
anythink else i can do to check things? adb logcat?
<oliv3r>
let me check this channels log for the xda report about the broken CWM
<geecko>
oliv3r, seriously, just reboot
<geecko>
you can recover from download mode anyway
<oliv3r>
but then i get back to regular CM
<oliv3r>
geecko: i have rebooted, 3 times :p
<geecko>
crap
<oliv3r>
i'm not affraid of the reboot
<oliv3r>
i go into CM-update; hit 'install rom', it reboots, but then idles in recovery mode
krabador has quit [Ping timeout: 260 seconds]
<geecko>
oliv3r, so what do you plan to do
<oliv3r>
geecko: stare at my screen :D
<oliv3r>
(reading dmesg right now)
<oliv3r>
(recovery dmesg)
<geecko>
lolz
<oliv3r>
i'll just boot into CM normally, and try again in a few days i suppose
<geecko>
oliv3r, so.. cm is still running fine on your phone?
<oliv3r>
yeah
<oliv3r>
but when I do the 'update' from the cm updater app; it reboots into the black recovery
<geecko>
why don't you try to flash the zip by hand
<geecko>
it's located in cmupdater/
zz_McNetic is now known as McNetic
<oliv3r>
so mount the internal storage partition
<oliv3r>
and then just unzip it to /system?
<geecko>
oliv3r, omg no
<oliv3r>
exactly :p
<oliv3r>
how do I flash it by hand
<geecko>
can you go into the recovery with Vol Up + Home + Power?
<oliv3r>
it always boots taht, but the screen stays black
<oliv3r>
if i reboot again; it boots normally
<oliv3r>
so it tries to run the update, but it fails to execute the upgrade somehow
<oliv3r>
actually, i don't know at all if vol up + home + power works at all
<oliv3r>
since i don't see what's on the screen :D
<oliv3r>
what option is the default, reboot?
<geecko>
oliv3r, weird.
<oliv3r>
so boot into recovery, hit power button = reboot?
krabador has joined #teamhacksung
<geecko>
if you are in the recovery and you hold Power, it will reboot
<oliv3r>
hold for 1 sec?
<oliv3r>
or until it reboots
<oliv3r>
GPT: Use GNU Parted to correct GPT errors.
<oliv3r>
heh
<oliv3r>
didn't know that the eMMC was using GPT partitions
beer has joined #teamhacksung
beer has quit [Changing host]
beer has joined #teamhacksung
<oliv3r>
geecko: i think it's at the spinning android; i do get [keys]PWR 1 and [keys]PWR 0 when i push and release the button
<geecko>
oliv3r, just flash a proper kernel
<geecko>
yours is obviously broken
<oliv3r>
i've rebooted to android now
paulk-collins_ has quit [Quit: Ex-Chat]
<oliv3r>
geecko: is there a way, not using heimdal, to flash it (either from recovery shell or via android shell)?
<oliv3r>
geecko: since recovery mode works just fine, dd-ing the kernel should be possible; since it's only boot.img right
<oliv3r>
(recovery mode works fine from shell obviously)
<geecko>
oliv3r, you can do it
<geecko>
if you succeed to copy boot.img on your internal memory
<oliv3r>
well that shouldn't be hard, either adb push, or just store boot.img on the internal emmc, i can mount stuff just fine
<oliv3r>
i'll check the updater script how it updates the kernel and what else would be requierd
<oliv3r>
geecko: do you know why/how recovery mode broke by the nightly? i know recovery mode is just a different initramfs to the very same kernel you use with your android
<geecko>
oliv3r, then you ramdisk is broken
<geecko>
copy boot.img using adb push
krabador_ has joined #teamhacksung
<geecko>
then flash it using dd following the updater script
<geecko>
that's all ;)
krabador has quit [Ping timeout: 260 seconds]
krabador_ has quit [Read error: Connection reset by peer]
krabador has joined #teamhacksung
<oliv3r>
so upgrading 'just' the kernel won't break android much will it?
<oliv3r>
it'll be a downgrade actually i suppose
<oliv3r>
since i'll go to the 10.1.3 kernel
<geecko>
oliv3r, there not major changes, don't worry
<geecko>
no*
<oliv3r>
good
<oliv3r>
so once i've upgraded the kernel; and it turns out the recovery initramfs is broken, (which i'm sure is included in the 10.1.3 zip) it's probably also just copying over some files to the recovery partition?
<oliv3r>
i'll figure that bit out im' sure :)
<oliv3r>
or i'll bug you more :p
<geecko>
oliv3r, there's no recovery partition
<oliv3r>
paulk
<oliv3r>
oh gone
<oliv3r>
geecko: ah, so wait, we have a kernel with initramfs, recovery is only run when requested, otherwise that same initramfs boots android normally
<oliv3r>
ok, that makes sense
<oliv3r>
i would have expected to have 2 kernels on the device, 1 for normal operation with normal initramfs, 1 kernel with build in initramfs for recovery purpouses :)
<oliv3r>
like 'dual bios' idea
<geecko>
oliv3r, nope
<geecko>
oliv3r, just flash it :P it's a matter of seconds
<oliv3r>
lol tomorrow or saturda
<oliv3r>
if i brick the phone now, i 'll have to fix it again before bed, or my gf will be mad :(
datagutt has quit [Ping timeout: 256 seconds]
kZard has quit [Ping timeout: 264 seconds]
<oliv3r>
in other news, our guys in #linux-sunxi can play jpeg, mpeg2 and now H264 (big buck bunny) via the cedarX engine, using only opensource code!
<oliv3r>
e.g. the binary blob is no longer needed; (lots of work still required, but big progress)
krabador has quit [Ping timeout: 260 seconds]
<geecko>
oliv3r, woot :D
<oliv3r>
very much so yeah
<geecko>
#linux-sunxi is full of talented developers, it's expected :)
<oliv3r>
which means i need to get off my ass
krabador has joined #teamhacksung
<geecko>
oliv3r, ?
<oliv3r>
geecko: work harder
<geecko>
oliv3r, haha
<oliv3r>
though should have my first driver mainlined soon, hopefully for the 3.12 merge window opens
beer is now known as nebkat
<geecko>
oliv3r, woo! what is it?
<oliv3r>
geecko: probably the world smallest driver ;)
<oliv3r>
it exposes the SID to userspace, which can contain the hdcp-key, sjtag-key, eufi-boot-key etc
paulk-collins has joined #teamhacksung
<geecko>
oliv3r, ok :)
<oliv3r>
but it brought out some bugs in sysfs that made gregkh do a lot of work :)
krabador has quit [Quit: Sto andando via]
krabador has joined #teamhacksung
McNetic is now known as zz_McNetic
yomi has joined #teamhacksung
thens has quit [Ping timeout: 245 seconds]
kZard has joined #teamhacksung
<yomi>
CM Nightly 10.2 20130829 clicking About tablet > Status = Unfortunately, the process com.android.phone has stopped.
yomi has quit [Quit: WeeChat 0.4.1]
Turtuga has quit [Ping timeout: 240 seconds]
Turtuga has joined #teamhacksung
g_byers is now known as gbyers[Away]
gbyers[Away] is now known as g_byers
kZard has quit [Ping timeout: 245 seconds]
g_byers is now known as gbyers[Away]
gbyers[Away] is now known as g_byers
g_byers is now known as gbyers[Away]
gbyers[Away] is now known as g_byers
krabador has quit [Ping timeout: 260 seconds]
altendky has quit [Ping timeout: 264 seconds]
g_byers is now known as gbyers[Away]
gbyers[Away] is now known as g_byers
geecko has quit [Quit: Quitte]
krabador has joined #teamhacksung
krabador has quit [Ping timeout: 260 seconds]
plastikman has quit [Remote host closed the connection]
paulk-collins has quit [Ping timeout: 245 seconds]
Gethiox has quit [Ping timeout: 264 seconds]
Gethiox has joined #teamhacksung
Entropy512 has quit [Remote host closed the connection]
<DAGr8>
xplodwild
<DAGr8>
around ?
<xplodwild>
yup
<DAGr8>
i shoudl receiv my oppo5 in the next 5-10 days
<DAGr8>
was wondering how I could help with 4.3
<DAGr8>
or what was the status on it (ther then it wont boot
<DAGr8>
other then *
<DAGr8>
i go tit strictly as dev device
<DAGr8>
got it *
<xplodwild>
we need to merge a bunch of kgsl patches properly in the kernel to work properly with the new qcom display hal
<xplodwild>
so for now, it boots, but black screen :)
<DAGr8>
so it boots :)
<DAGr8>
so what branch is good ??
<DAGr8>
cm2-test ?
<DAGr8>
i d like to build and test
<nebkat>
DAGr8: unless you are going to merge the patches i dont know what you plan to test
<DAGr8>
wait .
<DAGr8>
the patches are on gerrit or not ?
<DAGr8>
you guys say merge ..
<DAGr8>
im going to look thru gerrit and test them patch once i know what kernel branch touse it on
<DAGr8>
i figure its more of a "find the time to do it " issue more then somethign complicated