yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] AvRS:
Hate to piss on your parade so to speak but the thread is redundant until Gok actually releases a CM9 compatible kernel, he's only ever stated it may or may not work that is no guarantee so no reason for people to start complaining of issues for something that isn't fully supported. It's a good attempt to remove some of the posts from here but it's also nothing to do with development therefore is only a general thread at best but I'm sure that will be soon moved however irrelevant it may be.

You may want to just retitle it to post your ideas about a Siyah kernel slogan as them posts are just as annoying as seeing people continuously fill up this thread with repeated issues which have been discussed. Can't remember Gok opening this thread for people to say how excited they are or post an idea for a new slogan. I'm sure when he decides he'll add one. If only this could be a development only thread.
[Galaxy S II Original Android Development] Simongiar:
I'm experimenting an insane Android OS drain, apart from that, everything seems to be working good.
[Galaxy S II Original Android Development] sachs:
Good news....:D
[Galaxy S II Original Android Development] Karpfenhai:
Just read the OP with care, EXtweaks and voltage control work like a treat for me,

GB-undervolts are running fine ;) -100 everywhere
[Galaxy S II Original Android Development] Cristiano Matos:
weird, cause i use with LP7 and everything works very well (good battery life, very smooth, bln is ok ...) What problems do you have?
[Galaxy S II Original Android Development] bragon2010:
Same here. LP7 and it's all ok! :D
[Galaxy S II Original Android Development] Muchoaliento:
Sure ? Been using Beta 3 with LP7 for the last 18 hours and not a single freeze nor hiccup, with very good battery life.

I even lowered lowest frequency to 100 Mhz with VC...ROCK SOLID
[Galaxy S II Original Android Development] fkfs9:
are you guys running beta4 on LP7?
[Galaxy S II Original Android Development] digeddydogg:
Angry man:eek:

rice and pea(ce)
[Galaxy S II Original Android Development] rauschkugl:
You don't have to warn anyone. There's beta with big letters in the title so don't flash it if you don't know how to get back or are afraid to loose data or get a bootloop. Sources are out for less than 2 days now so it's normal that such problems will occur in this early stage. And I'm pretty sure that your backup will work if it's not corrupted or even flashing the stock kernel will be enough to get it booting again.

Will try at home if this is really due to the lp7 base or was caused by anything else.

Edit: well seems I don't have to flash lp7 as others already posted that it's working without problems.
[Galaxy S II Original Android Development] rlorange:
Sigh... the dev clearly stated LPQ or newer compatibility since LPQ is the first official and all LP(X) released based on it will work also.

Only when the base is updated by Samsung will this compatibility regime change. A new base will accompany a new source code release by Samsung.

On Gingerbread there were 3 base updates by Samsung.
[Galaxy S II Original Android Development] Pfeffernuss:
Yes, works just fine.
[Galaxy S II Original Android Development] AvRS:
Haha no I'm not angry at all just stating a bit of common sense. That thread could be put to better use if it was just a general Q&A thread instead of asking for issues that will be obvious seeing as it's not fully supported.
[Galaxy S II Original Android Development] wiedz:
yup.. been running for 12 hours now.

now problem yet. only complaint is cant play my mkv movies but will wait for future releases
[Galaxy S II Original Android Development] kachrukamble:
Which cf-root will work?

people having different rom installed other than sammy..
[Galaxy S II Original Android Development] jaxadv:
Well may i suggest that if ive been flashing all day with the original, without a problem but now there seem to be issues, then whatever change was made has caused the problems people are having. That would seem like a logical conclusion???

Right, so how do you explain our issues than?

Here's my story:

Was running Omega V11 with CF-Root kernel.

Downloaded Siyah, flashed it, decided to do a factory reset, powered off the phone. Started it in recovery. Selected wipe/data factory reset... the process was blocked but the arrows were working, I could see the separator line moving when I was touching up or down... but blocked...

Removed the battery, placed it back... tried to turn on... dead :(

---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------

That's a good ideea.... dunno, anybody know if they can find out or not?
[Galaxy S II Original Android Development] Ludus7:
mmm i'll find out.

do you think that the warranty change my phone if i say that he is dead after kies update ?

thank you
[Galaxy S II Original Android Development] yahyoh:
just tell them as i said :rolleyes: try
[Galaxy S II Original Android Development] jaxadv:
I was using Omega V11 and I'm in the same situation.
[Galaxy S II Original Android Development] Cristiano Matos:
Well may i suggest that if ive been flashing all day with the original, without a problem but now there seem to be issues, then whatever change was made has caused the problems people are having. That would seem like a logical conclusion???

Did you see my question on previously page?

That's what I meant!

Maybe some bad download.
[Galaxy S II Original Android Development] jaxadv:
I understand that different battery or usb jig is not working...

The ultimate solution is a JTAG service or warranty service :(
[Galaxy S II Original Android Development] Ludus7:
tomorrow i will try warranty :(
[Galaxy S II Original Android Development] darkgoon3r96:
Not even the one from your friend?!?
[Galaxy S II Original Android Development] kachrukamble:
None of method working, service center is last option for me
[Galaxy S II Original Android Development] Criminal23:
My Phone is also dead! :mad:

My Base: latest rc6 from this morning (after gokhanmorals reupload)

- Flashed Sensation v3 - and Hydrog3n

For Now: can't format or wipe /data

Flashed with Odin with Pit and Re-Partition - hang during data writing

Thankx

400 Eier im Arsch!
[Galaxy S II Original Android Development] geeman77:
m

I was agreeing with you in the fact that to me there looks like a problem with the kernel since the Dev (Gokhan) made a change to RC6 yesterday.

I'm not sure what you mean by "the process was blocked"??

P.S. I never use the softkeys to navigate in recovery. Always use volume and power.
[Galaxy S II Original Android Development] itchetrigr:
It seems to be Siyah-v3.1rc6 built on the 20th of april or later that seems to be the problem. I have flashed numerous roms with the 2nd kernel built on the 19th with no issues.
[Galaxy S II Original Android Development] gokhanmoral:
I have arrived home and removed the links.

and now I will upload m250l based sources, maybe someone would have an idea why that happened.

there is no change in formatting or wiping part of cwm recovery. it is the same in all v3.* versions.

so, if there is something wrong it is in m250l sources.

by the way, m250l and s and k sources are the same, only config file differs.

I did wipe, factory reset and format data, cache system but could not brick my device.

I will read the posts again and think about a possible reason.

but for now, I have no idea how your bootloader is wiped.

normally, if you haven't wiped it you should be able to use download mode.

in my previous experience I had blank screen, the phone was on but it was always trying to get into recovery. I had to charge my battery externally and use voldown-home-power combo. but I read that it doesn't work.
[Galaxy S II Original Android Development] dee163:
All software are not perfect.

What is the bug.
[Galaxy S II Original Android Development] bala_gamer:
Installed more than 4 roms today and all using Siyah rc6 + factory reset . Dunno where the problem resides

#*posted on the move *#
[Galaxy S II Original Android Development] Criminal23:
For me Recovery and Download still working.

I can install CF-Root Kernel with Odin and so on flash any other custom Kernel.

But I can't format /data - so I can't flash any Rom

On my Win I would del my Partition table and write a new one, but how should it work with the SGSII
[Galaxy S II Original Android Development] Vaedryn:
Welcome back at Home
[Galaxy S II Original Android Development] aeroman:
Here the same, no Problems with built from 19.04 - 22.05h - RC6 !!!

I use it since days and flash many Roms or make Full Wipe/Reset without any problems.

I've attached the RC6 from 19.4, should it need one here. ;)

Greetings
[Galaxy S II Original Android Development] snakefreak:
Its your own risk to flash customized kernel or rom!

German part

Ich kann verstehen das du sauer bist! Aber! Du hast das ja aus freien stücken geflasht weder GK noch die rom devs sind dafür verantwortlich.

Versuch garantie.

Grüße Dennis
[Galaxy S II Original Android Development] Ludus7:
i have another one battery full charge.

i use it, use jig or trying to turn on doesn't work. i also try to keep the phone with usb plug to pc and turn on with down+home button combo, but still nothing :(

i hope that warranty service change the phone without problem (i have flash counter to one and if they restart the phone can find out it maybe)
[Galaxy S II Original Android Development] Criminal23:
so I will try send back to sender (with clean counter and SD)

For the next time I must fishing out my Galaxy 3 *rofl*
[Galaxy S II Original Android Development] BrandoHD:
I think your issue is totally different, if your device was soft bricked during a Odin flash, that has nothing to do with kernel

All issues discussed today are with using recovery to wipe a partition

---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------

Were you using the very latest Siyah sources with the new WiFi driver and kernel rebase
[Galaxy S II Original Android Development] geeman77:
Gok, just a thought but did you verify the checksum after you uploaded the kernel? If not then it could be that the file was corrupted on transfer.
[Galaxy S II Original Android Development] pay.c:
Hey Gokhanmoral,

just a small suggestion for some future implementation:

The light sensor of the SGS2 is actually pretty good and not used up to it's full potential at all (nicely seen if you input *#0589# into you phone - the raw values of the sensor are shown then). Instead only four values are used in Siyah & stock ROM right now (see https://github.com/gokhanmoral/siyahkernel3/blob/master-3.0.y/drivers/sensor/cm3663.c)

Actualy it would be very easy to stock up, it seems: Adding some values in adc_table (e.g. 8 or whatever) in cm3663.c, that seems to be all that is needed. (According to the code at least)

That would be great for apps such as "Lux Auto Brightness" and stop the rather big jumping in display brightness levels.

Just an idea, BR! :)
[Galaxy S II Original Android Development] gokhanmoral:
I did the same, used all kind of wipes and that was even without making any backup... but I could not reproduce the issue.

some people reported having the issue after factory reset, some after wiping data/cache, and some after flashing a full-wipe rom (which should also flash another kernel).

first I blamed payload extraction part because when you try to boot into recovery and payload cannot be extracted (because of a bad flash or bad download maybe) all you get is a blank screen and you have to use odin to flash the kernel again.

and you should not attach any jig/usb cable to get into download mode but use only 3-button combo. also make sure that you press voldown-home-power using that order.

but if you still cannot get into download mode then I am lost... for now I cannot think of any reason and the only way seems jtag...

needless to say, I am very sorry although I never meant to brink any device...

the only change in the recent rc6 is that it was based on korean sources.

using git, I applied all the patches to korean base and I was planning to fix camera and other issues.

the sources are in the github for those who want to check.

I could not find anything in them which could cause that.
[Galaxy S II Original Android Development] Stylez Ray.:
Funniest post of the week!
[Galaxy S II Original Android Development] Criminal23:
Thnkx, but I only try to repair with Odin, for what I should Flash any normally custom Rom with it? For the counter? :D
[Galaxy S II Original Android Development] Mr.Dadulka:
Downloaded the same version probably - no problem. Reflashed again today with new CM9 120422. OK

Edit:

In comparison with RC5 and earlier I am fully satisfied with RC6 - mostly due to battery hold.
[Galaxy S II Original Android Development] BrandoHD:
It is indeed very weird and the manner in which it started was surreal, one user made a post and then boom, these issues came out of the word work.

Where is Entropy512, he is the type that would go through this with a fine teeth comb until he finds the reason
[Galaxy S II Original Android Development] yeahtyeaht:
sieh es so, du hast einen grund um aufs s3 zu wechseln :D
[Galaxy S II Original Android Development] Ludus7:
how can i check if the phone gone in download mode if the screen is blank ?

i try so hold vol down, home button, power on for 5 seconds, release power button, wait 3 secondi, presso volume up, this should be the combination to go to download mode. at this point, if i have just a blank screen but the phone is in download mode, plug usb to pc i can use odin, but nothing happen :(

some other solution to find out ? :(
[Galaxy S II Original Android Development] pmcee:
my phone is also bricked.

1. on cm9 did full wipe.

2. flashed hydrogenics + neak

3. flashed siyah

4. tried to wipe data but it got stuck at "formating data"

5. tried a nandroid of the cm9 but it stuck at "writing system"

6. took battery out. since then black screen.

usb jig doesnt work.

odin doesnt see it.

it is just a black stone.

help please
[Galaxy S II Original Android Development] Criminal23:
+1

aber wie mach ich das meiner Frau klar? :D

How could I explain that to my wife - that I now had a reason for buy GS3 :(

For now I must use my old Galaxy 3

Also: I now that the brick is not the reason of the Siyah Team (not directly) - It's my mistake (I'm a Flashing junkie)
[Galaxy S II Original Android Development] D108:
can anyone else that is NOT on this hydrogen rom confirm this problem with "hard" bricking while doing a factory reset?

i think the problem is Hydrogen rom & latest siyah.....
[Galaxy S II Original Android Development] simone201:
No 3 button combo? I think JTAG is the only way....or send it to a service centre :(

Very strange that using the korean sources causes those problems, i have looked at the sources but found nothing relevant about this wipe issue, seems like the recovery formats SBL instead of another partition, very strange indeed
[Galaxy S II Original Android Development] dee163:
GK

Don't apologize.

All users know there are risks when replacing the os or kernel.
[Galaxy S II Original Android Development] Criminal23:
Looks like, the combo Kills!

FOR NOW DON'T FLASH HYDROG3N WITH SIYAH 3.1RC6

Donload Link is removed, I know, but I hab the Kernel also on my SD, ...
[Galaxy S II Original Android Development] snakefreak:
looked at sources too, kannt find anything relevant.
[Galaxy S II Original Android Development] pmcee:
what is jtag?

btw it has to be a siyah kernel problem since the other kernels (including the hydrogenics included one) have no problem at all...
[Galaxy S II Original Android Development] Criminal23:
FOR ALL WHO HAD BRICKED DEVICES

LOOK HERE

Phistachio, the Moderator is totay in Holiday, but I hope he could help us tomorrow!
[Galaxy S II Original Android Development] beston94:
Are the people serious about these bricks?
[Galaxy S II Original Android Development] jaxadv:
Well it was written:

Wipping data...

This is where it was blocked... stuck for 10 minutes till I have removed tha bat.
[Galaxy S II Original Android Development] XDA mark:
Holy god what's going on :eek:

I'm on Hydrogen ICS and with the "old" Siyah rc6. I downloaded RC6 Friday Night if I'm not mistaken.

Should I run to another kernel atm? I have only read this page, will read the past ones but I am in panic mode so I posted directly
[Galaxy S II Original Android Development] bleuxeon:
I'm afraid that I have a timebomb in my GS2 now!:p

Thanks for this great adrenaline rush GK:D
[Galaxy S II Original Android Development] Criminal23:
What? do you mean, I make a joke? :eek:

Sry, ... what should I say
[Galaxy S II Original Android Development] darkgoon3r96:
Nope, all these guys are just playing around...

Of course they are serious! :banghead:
[Galaxy S II Original Android Development] darkgoon3r96:
Its just a problem with the latest one where GK changed the base to a Korean one.
[Galaxy S II Original Android Development] gokhanmoral:
as I said, it is complete rebase.

instead of applying patches to update4 sources, I applied them to korean sources.

there is no other difference neither in recovery nor in anything else.

it seems that with korean rebase something (which I don't know) corrupts partition table or bootloader because I don't know anything else that can cause that problem.

again, I am very sorry for those who had this problem. I wish I knew the reason and a solution but for now jtag seems to be the only solution.
[Galaxy S II Original Android Development] Ludus7:
this is step by step what i have done

1. i use hydrogen ics build 18.04 + neak 2.0.2

2. i perform a full wipe, including sd card, so i need to transfer file to sd card to install the rom again

3. the pc don't see like an usb storage the internal sd card from cwm to transfer the file

4. so with odin i flash siyah (because it has a different cwm version and i hope that usb storage will work and it did) downloaded 10 minutes before the brick from http://www.gokhanmoral.com/

5. flash is ok, i went in cwm, i did a factory reset (the voice up wipe cache and down reboot phone in cwm menu), i flash from internal sd card, the zip of hydrogen ics. flash has gone ok

6. reboot

7. died
[Galaxy S II Original Android Development] XDA mark:
Phiew. Thanks for your quick reply.

I read the past pages and saw that people posted the "build date" from settings, about. I believe if I'm not being a total noob, I have the RC6 version build on: Fri Apr 20 13:35:14 EEST 2012

I can calm down and go take a bath ^_^

edit: sorry for the people with bricked phone's, hope you all get it working again one way or another.
[Galaxy S II Original Android Development] kazuni:
Another bricked device here. MIUI.us latest with Siyah rc6, data wipe stuck, now can't do anything about mmcblk0p10 (data partition).

One interesting find though, I don't know if this helps gokhanmoral, is that in recovery, I can mke2fs on /dev/block/mmcblk0p10 (successful):

~ # mke2fs /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
131072 inodes, 524288 blocks
26214 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=536870912
16 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

however, I can't seem to mount it as ext2. Anyone got any insight?
[Galaxy S II Original Android Development] pmcee:
please tell me what is jtag...i only find xbox relevant stuff when i google jtag
[Galaxy S II Original Android Development] vektek:
Bricked too
[Galaxy S II Original Android Development] nayyarsheikh:
links broken not working help pls
[Galaxy S II Original Android Development] kazuni:
jtag - you can look up something like ORT-jtag.

I actually have a dead SHV-E160S (SKT-variant korean version of galaxy note) which i want to jtag and revive... perhaps it won't hurt to jtag these two devices now. haha.

(still sad that it's dead)

on second thought, gokhanmoral, if you can somehow skip data copy of "2nd rom" we can sort of have a script in your kernel to boot a system with data.img on internal SD? at LEAST we can have a working device... just a thought :P
[Galaxy S II Original Android Development] beston94:
Type in Samsung galaxy s2 jtag...
[Galaxy S II Original Android Development] Criminal23:
Or a little German accent, because Im from Germany? :p

OK - On the Fix an unflashable or soft bricked GSII you could see, 3 more XDA Members with the same /data Problem!

Is seems It came from Siyah 3.1rc6

Newest Post : Siyah 3.1rc6 but not hydro

So - Now It is not Hydrog3n alone! PLS Flash carefully till the Problem is fixed!!!
[Galaxy S II Original Android Development] dee163:
Read the forum. :confused:
[Galaxy S II Original Android Development] jaxadv:
Pretty much same thing happened to me as well just that my device got stuck during the wipe/data process and I had to remove the battery :(
[Galaxy S II Original Android Development] Westylakey:
UK members this guy on ebay offers the service. I do not know him or can vouch for him.

http://www.ebay.co.uk/itm/Samsung-G...ssories_RL&hash=item3374ca2f52#ht_7046wt_1401
[Galaxy S II Original Android Development] tolis626:
Don't apologize mate,it's not your fault.How should you know?Don't even feel sorry,those of us who take smartphone business seriously know the risks and accept the chances of breaking their devices only to make them better. :)

Anyway,I don't think there is anything in the kernel that could trigger such a "disaster".Unless you made a mistake or a typo in the recovery code,there is literally nothing else that could cause that behavior.And only the fact that some people have these issues while some others(me and you included) don't(yes,I'm using the latest RC6,build #76) seems fishy.I'm not saying that people are lying,but I don't think that it's only the kernel's fault,if at all.

Only idea that I had was if maybe the kernel tries to write some m250l/s/whatever stuff to places where it shouldn't write anything,like DMB or something.But even so,it would affect all of us,so that still doesn't seem logical...

Maybe you should indeed contact Entropy512-that guy seems to have something to say about everything,and fortunately he's right most,if not all of the time. :)

If my opinion about RC6 counts for you...Well,helluva job mate,you're slowly outdoing yourself every day. ;)
[Galaxy S II Original Android Development] Ludus7:
if you find some one that do jtag in europe, tell me. tomorrow i'll go to service and hope to fix in warranty.

obviously Gokhanmoral hasn't nothing to apologize. bad things happen and all we know the risk flashing our phone.
[Galaxy S II Original Android Development] jaxadv:
Uffff so the only solution is warranty now...

I will try to send it to Samsung and see if they will notice custom software or not... if the will... does anybody know what will be the procedure?

Will you pay for the shipment back if you refuse the quotation?

What about if you have scratches or dents on the case?

I know that HTC is not fixing any software or hardware issues if you don't pay for the housing replacement as well... is it similar with Samsung?

Thanks
[Galaxy S II Original Android Development] sebarkh:
I'm running Hydrogen and rc6+ now and everything is ok...

But you scarred the sh*t out of me!

I rebooted into download mode and flashing N.E.A.T...

Let's see the result...

EDIT: OK, I flashed NEAK kernel 2.0.3 with Odin and no problem so far... How to get rid of the leftovers from the secondary rom?
[Galaxy S II Original Android Development] Zewsan:
Just a question feeling half scared on latest rc6, but running.

It should be quite safe to boot into recovery and flash the good old rc2 for example? Without any wipe, except cache and dalvik that is?