« first day (806 days earlier)      last day (4132 days later) » 

ce4
9:00 PM
You can dl recent i9100 CM10.1 firmwares here: get.cm/?device=i9100
 
dmsg -c gives me
`[63902.028114] usb 2-4: USB disconnect, device number 69`
`[63905.664081] usb 2-4: new high-speed USB device number 70 using ehci_hcd`
 
ce4
The .zip also contains a boot.img
Oh @Pureferret looks promising
Does the 5.5. version have the option to start 'adbd' on demand under advanced?
 
lsusb | grep Samsung
Bus 002 Device 070: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
Let me reboot and see
 
ce4
what about 'adb devices' ?
 
nuthin'
adbd=running and adbd.recovery=1
 
ce4
9:05 PM
root 25760 0.0 0.0 30392 1444 pts/19 Sl+ 20:42 0:02 adb fork-server server
is your adb process running as root (the 'fork-server' daemon )
 
I was going to say that ce4!
 
ce4
:-)
 
Have you seen the new chat room I made?
 
ce4
which one?
 
The only other active one funnily enough.
 
9:06 PM
devices [-l] - list all connected devices
('-l' will also list device qualifiers)
using -l makes it show up as a recovery usb
0019638048f28e recovery usb:2-4
 
ce4
good
but you cannot connect with 'adb shell', can you?
 
YES!
Woot
 
YAY
 
how I can exit that and I can run your command?
there is also a adb backup command...
 
use the exit command to get out of adb shell
 
ce4
9:08 PM
fine.
I'll post that command again, wait
 
adb backup is only for normal user mode
 
how I can exit that and I can run your command?
 
ce4
one sec
'exit'
done?
If you like, you can install 'clpbar'
it's a pipe throughput visualizer
Oh: And mount USB storage should now also work
@Pureferret ^^
for i in mmcblk0p{1..12} mmcblk1p{1,2}; do adb shell cat /dev/block/$i \| gzip -1 \| uuencode o | uudecode -o - | gzip -d > /targetfolder/$i.img;done
this fetches everything
but it's slow. You can also use Mount USB and omit the big 12GB usb partition via adb
 
9:26 PM
@ce4 I like this option
I've mounted it but I've not seen it pop up in my explorer
 
ce4
?
Should've done so a few sec's later
maybe you need to manually do it (see by "cat /proc/partitions")
Besides this: Which option do you want to take? Go CyanogenMod? Not sure how to fix your actual situation (so that you have root and retain your current setup)
 
@ce4 it doesn't seem to show up there
 
ce4
Which option?
 
hang on, sorry
 
ce4
ah, in your partitions list, ok
 
9:37 PM
11 0 1048575 sr0
11 1 7973664 sr1
8 0 976762584 sda
8 1 102400 sda1
8 2 163840000 sda2
8 3 1 sda3
8 4 698532864 sda4
8 5 102400000 sda5
8 6 11883520 sda6
no idea how I know which is which
 
ce4
none
sr* = CDrom or so, sda is your primary HDD
 
@ce4 and lsusb doesn't show it up either
 
ce4
should be something like sdb + sdb1
but you could get in via adb, right?
 
I could
I thnk whilst mounted I can't do that anymore
 
ce4
maybe, but should be possible normally
 
9:40 PM
hmmm
yeah shell is saying device not found
 
ce4
lsusb?
 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 046d:c068 Logitech, Inc. G500 Laser Mouse
 
ce4
completely missing
 
yup
 
ce4
anyway, then just use adb to pull the data
for i in mmcblk0p{1..12} mmcblk1p{1,2}; do echo $i; adb shell cat /dev/block/$i \| gzip -1 \| uuencode o | uudecode -o - | gzip -d | bar > /tmp/$i.img;done
 
9:43 PM
adb doesn't seem to work
getting it back now hopefully
 
ce4
yeah, reboot the CWM
 
ok
it's gone now
rats
 
ce4
?
adb mode inaccessible?
just try to replug it again
 
yeah
ok
 
ce4
I have these issues too
(I just updated my S2 via this method)
 
9:48 PM
uh-huh
still trying
 
ce4
at least it once worked
 
yeah
we can do this, we have the technology
 
ce4
:-)
I noticed that plugging the micro-port does the trick (only happens with my S2 though, must be a samsung thing)
(i.e. the phone-plug, not the PC-side)
 
I have sudo dmesg running on a 1 second watch and just playing with the usb cable now
in and out
 
ce4
hmm, really strange
always the error -22?
 
9:56 PM
@ce4 for?
 
ce4
(that got logged in your dmesg which you posted above some time ago)
or does dmesg output nothing at all when you replug it?
 
@ce4 nothing
even with the -l option
 
ce4
CWM's up? and nothing happens when plugging in? What if you boot your phone when it's plugged in already?
Or remember what you did special when it worked the last time?
 
@ce4 last time was just the first boot into CWM from the new flash
 
ce4
that should be no reason (booting the recovery doesn't change anything. all is mounted read-only by default)
 
10:04 PM
weird
I decided that trying 'fix permissions' would be a good plan
it's still 'fixing'
 
ce4
erm, ...
 
yeah I'm regrettign that now as it's taking too long
 
ce4
That modifies your firmware, it's going over all of your files probably
never actually did that personally
 
yeah....
done!
well I can go into the actual device now
so I might try using adb not in CWM mode?
is that possible?
 
ce4
fine
yeah
do you have that command:
bar
 
10:12 PM
adb bar?
 
ce4
no on your linux box, just "bar"
it's in the "bar" package in ubuntu
 
ce4
If you like you can install it
 
...what does it do?
 
ce4
gives you an ETA (visualizes pipe throughput)
it's just eye candy
sort of (if one can say that on the cmdline)
 
10:14 PM
awesome
 
ce4
@ce4 <= here's the command
 
thanks
 
ce4
To make a dump of your S2's partitions
 
Yup
I'm just booting back into CWM
nope
it won't have it >.<
 
ce4
didn't you just have adb access?
 
10:22 PM
Yeah
not anymore
 
ce4
Why did you reboot then?
 
oh no
I lost it before I rebotted
I tried to mount my device, remember? Then it wouldn't let me adb anymore
 
ce4
Ah, I thought it worked after the 'fix perms' thing
 
ah no
13 mins ago, by Pureferret
well I can go into the actual device now
that means I can turn it own as usual
 
ce4
Ah! the kernel now works again...
Now i got it
 
10:26 PM
@ce4 yes
 
ce4
However your device now doesn't have the right kernel fitting for your rom
 
can I just leave it at that?
I don't know how flashing CWM 5.5.0.4 did that
 
ce4
(the kernel is old) your firmware is newer. Very probably stuff doesn't work (camera, mic, taking/watching videos)
It flashes the boot-kernel
(that is in fact an original Samsung kernel)
just an old one with addons to have the recovery working
 
ahhh ok
 
ce4
Now you got a working device back: Which exact version is it running (samsung firmware)?
 
10:28 PM
that's in settings right?
 
ce4
yeah, settings=>device info or so
 
3.0.15-TH codeworkx@cyanogenmod #2 SMP PREEMPT Sun Apr 29 10:50:20 CEST 2012
 
ce4
ah, that is a cyanogenmod kernel. Do you know what was installed before that?
It says so here (to pick the right download)
 
that one----> CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.zip <---that one
 
ce4
@Pureferret Thats what you said you loaded
 
10:33 PM
yeah
 
ce4
It did match your then installed stock version, right?
 
yes
I checked my kernel before I tried to flash it
 
ce4
Something must have gone wrong...
 
yeah...
I gathered XD
 
ce4
you don't have a encrypted phone, do you?
A very recent root-exploit that works for your device...
You can then do a titanium backup and decide how to proceed
If you like, there's even JellyBean 4.2 (Cyanogenmod available)
@Pureferret ^^
 
10:37 PM
@ce4 no, not encrypted
 
ce4
ok, the original cfroot source states problems with crypto
(just saying)
 
@ce4 well not as far as I know
I've not encrypted
 
ce4
you have to do it manually in the settings
 
ahh ok
I've not
 
ce4
@ce4 here's a working exploit
 
10:41 PM
cool
I'm reading it now
 
ce4
In fact this hole is very uncool (of Samsung), because any app can exploit it, easily. Good for modding though
 
@ce4 I don't quite get what it does
 
ce4
nevermind, it's just a root-exploit to gain root-access and install Superuser+su
 
ah ok
why not just flash it with the JB you mentioned??
 
ce4
(the hole that's exploited opens the whole system RAM read/write for anyone. The exploit uses it to overwrite system memory and gain access)
The JB needs a wipe in advance
Which you probably don't want (not having a backup yet)
 
10:45 PM
@ce4 right
and the CW 5.5 doesn't give me root to use titanium, does it?
 
ce4
it's just a recovery (linux + a basic gui). Titanium needs a full fledged android
 
@ce4 got you
so I want to root it first....and the exploit is a good way
 
ce4
It allows to do backups (but that needed too much space you said)
 
right.
 
ce4
Yep, that root is OK
 
10:51 PM
@ce4 that root being a .apk?
 
ce4
yes, for easy deployment
 
cool
 
ce4
You need to enable 'unknown sources' in the settings
 
I just installed it via the QR code
and it says it's already rooted
so the next stpe is to download titanium from the gPlay?
 
ce4
sure
 
10:57 PM
Thanks for doing this by the way
extremely helpful
 
ce4
:-)
I have some time left (waiting for stuff to compile)
switching between chat here and reddit...
Only thing is: Hands on in RL whould've been way faster (than remote via chat), well.
 
but I'd have learnt less
 
ce4
sure.
I once had to secure a friend's Nexus that got its screen shattered to pieces
got him all valuable data in an hour and got his Nexus S for that action :-)
Most valued item: Phone Number of a gal he met in one of his notes... :-)
 
@ce4 Heh
backing up now
 
ce4
What to do after that? Going the CyanogenMod route? Or do you want to leave it in this current state?
 
11:05 PM
@ce4 I'd just like the standard Samsung ROM but rooted
 
ce4
You'd need to find a fitting kernel then (the one you replace by installing CFroot)
PS: CM has some cool features. If you had an Galaxy S i9000, I'd say go for it.
 
@ce4 CM=CyanogenMod?
 
ce4
the i9100 is not so well supported because Samsung chose to not help the community
yep (@CM)
 
@ce4 ??
 
ce4
i.e. the i9100 port lacks some stuff (no FM, HDMI, amongst other minor things)
That's one of Cyanogenmod's former Samsung GAlaxy maintainers
 
11:09 PM
@ce4 Ahhh
 
ce4
He and others ran to Sony. Nice but very lengthy read (8 posts over the course of 8 weeks or so)
As for Samsung: I can't stand their touchwiz, once I've seen Android's original UI (on a Nexus or so)
 
touchwiz?
 
ce4
That's Samsung's graphical user interface (which is a proprietary Android addon)
 
@ce4 Ah ok
can't stand to dev with or use?
 
ce4
only for using it. It feels awkwardly ancient compared to the new JellyBean UI
Maybe I'm overrating it, take it with a grain of salt. :-)
here are some original kernels ^^
Not sure, how to properly revert to your old setup
Try things like camera, usb-storage, photographing, etc. And see if all works or somethings broken
 
11:18 PM
@ce4 with each new flash?
 
ce4
no, with your current setup
to decide if you leave it the way it is
 
@ce4 ah ok
the camera works but I can't see whats on the screen atm
 
ce4
yeah. What I suspected
Either: Find the correct matching kernel for your actual firmware again and hope it flashes well
Or: Go for a custom firmware like CyanogenMod. Also nice.
 
@ce4 I may go for the later
 
ce4
Or as a third option: Live with those broken features until Samsung releases another upgrade
 
11:24 PM
how does CM compare to vanilla?
 
ce4
Added value, same experience
It's rooted, you can overclock and do more stuff
in comparison on a Nexus: CM gives you a nicer shell and a more hacker friendly root-installation amongst others
 
@ce4 Look-and-feel?
 
ce4
like a nexus
it's consistent across all of their supported devices
 
so it looks the same?
 
ce4
here are some impressions
 
11:30 PM
cool
 
ce4
If you install it you need to install 3 .zip files and then do a wipe before initially booting
 
I may do that
 
ce4
in case you decide to do it, you need:
- CM10.1 .zip firmware file from http://get.cm/?device=i9100
- GApps 4.2 Google package from http://goo.im/gapps
- Radio update XXLS6 http://obihoernchen.net/downloads/SGS2%20Modems/Modem_XXLS6-CWM.zip
@Pureferret: consult your pillow... :-)
 
@ce4 Not known to be a good android modder
 
ce4
You think you'll be to fearful tomorrow?
 
11:40 PM
@ce4 Nah
I laugh in the face of fear, and drop icecubes down the vest of death
 
ce4
Yeah, that's Android's update problem and the lock it down or don't commit to the community attitude of device makers
It's a mess and you constantly have to keep track in the jungle of xda to not forget anything
(I for one forgot to install the Radio update and had dropped calls and other problems until i found the reason)
 
Titanium is hanging
 
ce4
erm, ok. which app
 
google play
 
ce4
ah
you don't need that
In fact, only the user installed apps matter + some system stuff (wifi keys + bookmarks + sms +phone calls)
 
11:47 PM
ok
am I ok to hard restart the phone via taking the baterry out?
 
ce4
think so.
 
It was the google play data not the app it froze on
 

« first day (806 days earlier)      last day (4132 days later) »