Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed
128 Pages « < 122 123 124 125 126 > » Bottom

Outline · [ Standard ] · Linear+

 Samsung Galaxy S II Official Thread V31, Help the G Users out, First post!

views
     
antt00
post Apr 23 2012, 02:24 PM

RescuE
********
All Stars
10,873 posts

Joined: Apr 2009
QUOTE(ellimist @ Apr 23 2012, 02:19 PM)
I restored them oredi oredi

Ah ok, susah la this whole cm changing mounts thing. but I can still see both directories, bht most likely they got swapped right. Now external SD became primary, that's y my pictures save there. Hmm wonder what would happen when I try to use ums
*
Flash voku...
snigapoe
post Apr 23 2012, 02:29 PM

Look at all my stars!!
*******
Senior Member
2,388 posts

Joined: Sep 2004
QUOTE(antt00 @ Apr 23 2012, 02:15 PM)
Guys latest siyah 3.1 is meant to match cm9 changing the mounting point of internal and external sd. If you're using aokp or older cm9 it will screw up the drive location. Gokhan was supposed to release a separate version for aokp but the hardbrick issue distracted him. Its best for you to use older siyah kernel or other kernel for now. Actually i am also now not sure how cm9 is mounting those sd cos many are complaining about it. It keeps changing.

Added on April 23, 2012, 2:16 pm
They are not uninstalled. Just not detected. Flash older kernel or other kernel and they will b back.
*
no wonder
hope newer hydrogenic ics also follow the mounting point of CM
for now have to flash to other kernel first
ellimist
post Apr 23 2012, 02:29 PM

Still a Yui-tard
*******
Senior Member
6,106 posts

Joined: Jan 2003
From: Klang
QUOTE(antt00 @ Apr 23 2012, 02:24 PM)
Flash voku...
*
Just tested UMS, external gets mounted instead.

Hmm it's no particular big deal for me for the moment, but guess maybe I should try something else like voku. Or maybe revert to rc6 for the time being.

Could be my mind playing tricks with me, but 3.1 seems pretty darn smooth o.O
tenchi0205
post Apr 23 2012, 02:31 PM

Tech Noob
*******
Senior Member
2,881 posts

Joined: Oct 2006
From: Kota Kinabalu, Sabah.
QUOTE(antt00 @ Apr 23 2012, 02:15 PM)
Guys latest siyah 3.1 is meant to match cm9 changing the mounting point of internal and external sd. If you're using aokp or older cm9 it will screw up the drive location. Gokhan was supposed to release a separate version for aokp but the hardbrick issue distracted him. Its best for you to use older siyah kernel or other kernel for now. Actually i am also now not sure how cm9 is mounting those sd cos many are complaining about it. It keeps changing.

Added on April 23, 2012, 2:16 pm
They are not uninstalled. Just not detected. Flash older kernel or other kernel and they will b back.
*
I had restore back to the 3.1rc6+ april 18 version till new update
salimbest83
post Apr 23 2012, 02:32 PM

♥PMS on certain day♥
*******
Senior Member
8,642 posts

Joined: Feb 2006
From: Jelutong Penang
QUOTE(ellimist @ Apr 23 2012, 02:29 PM)
Just tested UMS, external gets mounted instead.

Hmm it's no particular big deal for me for the moment, but guess maybe I should try something else like voku. Or maybe revert to rc6 for the time being.

Could be my mind playing tricks with me, but 3.1 seems pretty darn smooth o.O
*
im stil on rc6.
btw u flash 3.1 use odin or just using cwm manager?

( kinda sked coz got ppl say "can bricking ur phone" sweat.gif )
snigapoe
post Apr 23 2012, 02:33 PM

Look at all my stars!!
*******
Senior Member
2,388 posts

Joined: Sep 2004
QUOTE(salimbest83 @ Apr 23 2012, 02:32 PM)
im stil on rc6.
btw u flash 3.1 use odin or just using cwm manager?

( kinda sked coz got ppl say "can bricking ur phone" sweat.gif )
*
currently follow antoo method directly flash zimage
ellimist
post Apr 23 2012, 02:34 PM

Still a Yui-tard
*******
Senior Member
6,106 posts

Joined: Jan 2003
From: Klang
QUOTE(salimbest83 @ Apr 23 2012, 02:32 PM)
im stil on rc6.
btw u flash 3.1 use odin or just using cwm manager?

( kinda sked coz got ppl say "can bricking ur phone" sweat.gif )
*
I tested mobile odin since I have it.

This one should be fine. Problem is apparently not 3.1, but something in rc6 that was wiping wrong partitions (flashing via recovery includes the script to wipe cache or whatever I guess).

If you're scared, maybe try extracting the ziimage from the zip file, and flash via cwm app, like how antt00 usually does it. Or wait till all this dies down laugh.gif
snigapoe
post Apr 23 2012, 02:36 PM

Look at all my stars!!
*******
Senior Member
2,388 posts

Joined: Sep 2004
downloading voku 1.8 hope this solve my problem
since i', not sure the siyah rc6 i downloaded is the affected batch not
toocommon
post Apr 23 2012, 02:48 PM

Casual
***
Junior Member
388 posts

Joined: Mar 2008
From: PJ
Hi guys, i have my s2 for 8 months now only i noticed i got the camera red spot problem. Actually last time read about it in internet, that time i checked, no red spot, may be that time under that specific condition, there's no red spot, not sure.
but now i clearly see it.
any one here have the same issue? possible because of the 2.3.6 update that cause it? b4 this i was using 2.3.4 or 2.3.5
can fix it?
snigapoe
post Apr 23 2012, 03:01 PM

Look at all my stars!!
*******
Senior Member
2,388 posts

Joined: Sep 2004
first impression i'm having on voku kernel felling almost as smooth as siyah 3.1
let's see how's the performance on standby mode
hope it won't fail me too
tenchi0205
post Apr 23 2012, 03:04 PM

Tech Noob
*******
Senior Member
2,881 posts

Joined: Oct 2006
From: Kota Kinabalu, Sabah.
Do you think Gohan will stop develop siyah after the RC6 incident?
ellimist
post Apr 23 2012, 03:11 PM

Still a Yui-tard
*******
Senior Member
6,106 posts

Joined: Jan 2003
From: Klang
QUOTE(tenchi0205 @ Apr 23 2012, 03:04 PM)
Do you think Gohan will stop develop siyah after the RC6 incident?
*
Doubt so. Bricking is a risk they always disclaim when you flash their stuff; there's always the possibility things can go wrong when they tinker with codes n what nots.

Oh well, testing voku 1.8 now I guess tongue.gif

This post has been edited by ellimist: Apr 23 2012, 03:16 PM
antt00
post Apr 23 2012, 03:18 PM

RescuE
********
All Stars
10,873 posts

Joined: Apr 2009
QUOTE(snigapoe @ Apr 23 2012, 03:01 PM)
first impression i'm having on voku kernel felling almost as smooth as siyah 3.1
let's see how's the performance on standby mode
hope it won't fail me too
*
Yes voku have always been smooth, sometimes i feel its smoother than siyah. But numerous issue in the past prevent me from evaluating its batt performance. V1.8 seem to be running without any bugs so finally can test it.

Also by default its 100 - 1400mhz. Change this if you want with voltage controller or rom controller or any app you prefer.
snigapoe
post Apr 23 2012, 03:18 PM

Look at all my stars!!
*******
Senior Member
2,388 posts

Joined: Sep 2004
QUOTE(tenchi0205 @ Apr 23 2012, 03:04 PM)
Do you think Gohan will stop develop siyah after the RC6 incident?
*
no way that will happen
it's my favourite kernel since i started flashing

QUOTE(ellimist @ Apr 23 2012, 03:11 PM)
Doubt so. Bricking is a risk they always disclaim when you flash their stuff; there's always the possibility things can go wrong when they tinker with codes n what nots.

Oh well, testing voku 1.8 now I guess tongue.gif
*
you should try, it really very smooth on my device
antt00
post Apr 23 2012, 03:18 PM

RescuE
********
All Stars
10,873 posts

Joined: Apr 2009
QUOTE(tenchi0205 @ Apr 23 2012, 03:04 PM)
Do you think Gohan will stop develop siyah after the RC6 incident?
*
I hope not. sad.gif
ellimist
post Apr 23 2012, 03:25 PM

Still a Yui-tard
*******
Senior Member
6,106 posts

Joined: Jan 2003
From: Klang
QUOTE(antt00 @ Apr 23 2012, 03:18 PM)
Yes voku have always been smooth, sometimes i feel its smoother than siyah. But numerous issue in the past prevent me from evaluating its batt performance. V1.8 seem to be running without any bugs so finally can test it.

Also by default its 100 - 1400mhz. Change this if you want with voltage controller or rom controller or any app you prefer.
*
3.1 siyah is pretty smooth from my very short stint on it tongue.gif

QUOTE(snigapoe @ Apr 23 2012, 03:18 PM)
no way that will happen
it's my favourite kernel since i started flashing
you should try, it really very smooth on my device
*
Yeah like antt00, I tried previous versions of voku. Then we both got stuck on boot logo (fortunately not hard brick), and had to flash kernel via Odin. I removed by triangle with jig, while antt00 used triangle away app since he was on newer bootloader.

But yeah, I'm ok voku now. No idea if battery is ok on this one.
snigapoe
post Apr 23 2012, 03:28 PM

Look at all my stars!!
*******
Senior Member
2,388 posts

Joined: Sep 2004
QUOTE(ellimist @ Apr 23 2012, 03:25 PM)
3.1 siyah is pretty smooth from my very short stint on it tongue.gif
Yeah like antt00, I tried previous versions of voku. Then we both got stuck on boot logo (fortunately not hard brick), and had to flash kernel via Odin. I removed by triangle with jig, while antt00 used triangle away app since he was on newer bootloader.

But yeah, I'm ok voku now. No idea if battery is ok on this one.
*
soft brick on voku?
luckily nothing happen to me
the only softbrick i got is when i first trying to rooting my device after that, never appear on my device anymore
ellimist
post Apr 23 2012, 03:30 PM

Still a Yui-tard
*******
Senior Member
6,106 posts

Joined: Jan 2003
From: Klang
QUOTE(snigapoe @ Apr 23 2012, 03:28 PM)
soft brick on voku?
luckily nothing happen to me
the only softbrick i got is when i first trying to rooting my device after that, never appear on my device anymore
*
soft brick after trying to go into recovery, some sort of bug which he fixed oredi (think that was on v1.4) laugh.gif

should be working good now
antt00
post Apr 23 2012, 03:33 PM

RescuE
********
All Stars
10,873 posts

Joined: Apr 2009
QUOTE(snigapoe @ Apr 23 2012, 03:28 PM)
soft brick on voku?
luckily nothing happen to me
the only softbrick i got is when i first trying to rooting my device after that, never appear on my device anymore
*
That was an old version tongue.gif . Not hard brick just something wrong with the recovery. So when boot to recovery device got stuck and cannot reboot also. Only can get into download mode and flash another kernel.

Added on April 23, 2012, 3:34 pm
QUOTE(ellimist @ Apr 23 2012, 03:30 PM)
soft brick after trying to go into recovery, some sort of bug which he fixed oredi (think that was on v1.4) laugh.gif

should be working good now
*
After that it was fixed. biggrin.gif

This post has been edited by antt00: Apr 23 2012, 03:34 PM
ellimist
post Apr 23 2012, 03:43 PM

Still a Yui-tard
*******
Senior Member
6,106 posts

Joined: Jan 2003
From: Klang
QUOTE(antt00 @ Apr 23 2012, 03:33 PM)
That was an old version  tongue.gif . Not hard brick just something wrong with the recovery. So when boot to recovery device got stuck and cannot reboot also. Only can get into download mode and flash another kernel.

Added on April 23, 2012, 3:34 pm
After that it was fixed.  biggrin.gif
*
Recently both those 2 got recovery related problems, scary tongue.gif

Gonna use your zimage method, or at least flash via tar using mobile odin from now on sweat.gif

Especially scared since I experienced the voku prob, and I did flash the freaking rc6 with camera fc. Sometimes I do wipe cache/dalvik before flashing, fortunately I didn't when reverting to older rc6 yesterday. So close to hard brick sweat.gif sweat.gif

Ok just noticed something with voku. I can't save my UV settings. It keeps reverting to stock values sweat.gif


This post has been edited by ellimist: Apr 23 2012, 03:49 PM
« Next Oldest · Android · Next Newest »
 

128 Pages « < 122 123 124 125 126 > » Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
 0.0357sec    0.64    6 queries    GZIP Disabled
Time is now: 11th December 2025 - 10:15 PM
All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)
Removal Request
Powered by Invision Power Board © 2025  IPS, Inc.