Unfortunately I cannot ask questions in specific thread, so I would like to do it now.
I have a problem after flashing LS8, specifically Wanamlite v.14. For some time phone works perfectly, until it suddenly switches off. I am able to power it up, but it freezes on the first screen with logo and model number. I am however able to access recovery.
And so I did - accessed recovery, flashed rom again, unfortunately, the only thing that worked was to do a full factory reset.
It worked... for a while. Then the story repeated itself. This time I did exactly the same, but started digging: some reported, that it might be a problem with kernel, which is Philz newest 4.00 b22. So I changed kernel: Dorimanx 7.44 - got serious overheating problems and the same probem. Jeboo 1.2 - the same. I then discovered, that eg. Jeboo has something from Philz kernel, so I flashed earlier version of Jeboo 1.1f. I am currently at this stage. Oh, btw. my chip is insane, if it changes anything.
Can anyone please tell me if you had similar problems, maybe not only users of Wanamlite, but other roms (which would confirm problems with kernel)? Can anyone tell me if there is any solution? Or at least does anyone knows what is happening? It is getting really weird, as I have been reading post of people reporting identical problem as I have, but devs seem to avoid the topic... Or maybe you guys are working hard to find out what is the problem - in that case a simple one line statement "we are aware. working on it" will suffice. Please, I am starting to be desperate here...
Regards.
Try Siyah kernel v6 beta4. I am also using WannamLite and have no issues at all.
Odp: [Q] Black Logo Screen problem
Thank you for the tip. I found the kernel elsewhere, however is there a thread about siyah v6 somewhere here, on xda-developers?
I will test it against problems I encountered and report for future readers.
The question still stays: what happened to me and all these other people?
Sent from my GT-I9100 using xda app-developers app
clawz71 said:
Thank you for the tip. I found the kernel elsewhere, however is there a thread about siyah v6 somewhere here, on xda-developers?
I will test it against problems I encountered and report for future readers.
The question still stays: what happened to me and all these other people?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yes it is, try to always download from xda.
You've experienced conflict between ROM & Kernel. Always check the custom ROM thread and read it upside down so you can spot potential issues regarding this kinda conflict.
Odp: [Q] Black Logo Screen problem
gastonw said:
Yes it is, try to [U/]always[/U] download from xda.
Click to expand...
Click to collapse
Could you point me in its direction? I have been using search extensively without any results.
gastonw said:
You've experienced conflict between ROM & Kernel. Always check the custom ROM thread and read it upside down so you can spot potential issues regarding this kinda conflict.
Click to expand...
Click to collapse
I did it, however, which is weird, only some of people reported it and dev, who in this case is Wanam, did not reply.
And I know, that it seems to be a conflict between rom and kernel, but how is it possible that not everyone had this issue while flashing Wanamlite with factory reset and kernel included in the rom? Nevertheless, I am sticking with Siyah for the while and see what happens.
Sent from my GT-I9100 using xda app-developers app
I have the same issue, it seems with LS8 whenever I reboot, there's a 50-50 chance my phone will "die" and I'll need a complete wipe and rom install
If I do a hot boot within Titanium Backup, guaranteed my phone will brake.
This happens with Siyah, PhilZ and Jeboo, it's not really a kernel issue, now a Wanamlite's issue since people on NEATROM also said they suffered the same issue, there's some problem with the firmware, seems that whenever the phone doesn't shut down properly, it won't start again.
Wish I could provide a log, but since phone totally dies, I don't know how to retrieve it.
@op: you got a siyah q&a thread sticked in the Q&A section.
Why don't you guys flash stock while you sort this out?
Custom ROMs will be updated soon now that ls8 is out. Therefore kernels will be updated as well.
Sent from the little guy
I'm having the same problem too. I have been using the Stock LS8 and Philz Kernel (4.00 b22-b30). I stopped using Siyah b4 in the previous JB Stock Leak because I had isues with the camera freezing.
Any suggestion?
clawz71 said:
Unfortunately I cannot ask questions in specific thread, so I would like to do it now.
I have a problem after flashing LS8, specifically Wanamlite v.14. For some time phone works perfectly, until it suddenly switches off. I am able to power it up, but it freezes on the first screen with logo and model number. I am however able to access recovery.
And so I did - accessed recovery, flashed rom again, unfortunately, the only thing that worked was to do a full factory reset.
It worked... for a while. Then the story repeated itself. This time I did exactly the same, but started digging: some reported, that it might be a problem with kernel, which is Philz newest 4.00 b22. So I changed kernel: Dorimanx 7.44 - got serious overheating problems and the same probem. Jeboo 1.2 - the same. I then discovered, that eg. Jeboo has something from Philz kernel, so I flashed earlier version of Jeboo 1.1f. I am currently at this stage. Oh, btw. my chip is insane, if it changes anything.
Can anyone please tell me if you had similar problems, maybe not only users of Wanamlite, but other roms (which would confirm problems with kernel)? Can anyone tell me if there is any solution? Or at least does anyone knows what is happening? It is getting really weird, as I have been reading post of people reporting identical problem as I have, but devs seem to avoid the topic... Or maybe you guys are working hard to find out what is the problem - in that case a simple one line statement "we are aware. working on it" will suffice. Please, I am starting to be desperate here...
Regards.
Click to expand...
Click to collapse
reading threads + trial & error.
Sent from the little guy
Odp: [Q] Black Logo Screen problem
gastonw said:
reading threads + trial & error.
Sent from the little guy
Click to expand...
Click to collapse
We do it. We read threads and do trial and error. I even started a separate thread to report our trials to the community. This one
Thank you for your input.
pedroren said:
I'm having the same problem too. I have been using the Stock LS8 and Philz Kernel (4.00 b22-b30). I stopped using Siyah b4 in the previous JB Stock Leak because I had isues with the camera freezing.
Any suggestion?
Click to expand...
Click to collapse
Well I am still on siyah v6.b4. So far so good. But I am not too happy with battery life... You might try jeboo 1-1f, as some reported it doesn't cause any problems. I had jeboo 1-2 for a while but out generated the same bootloop...
Sent from my GT-I9100 using xda app-developers app
Odp: [Q] Black Logo Screen problem
gastonw said:
Custom ROMs will be updated soon now that ls8 is out. Therefore kernels will be updated as well
Click to expand...
Click to collapse
What do you mean by that? We are discussing here ls8 kernels, aren't we? Newest Phillz is a stock one based on ls8, afaik.
Sent from my GT-I9100 using xda app-developers app
[Sorry for double post, I thought it merges automatically]
I truly don't know what was being discussed here, If I posted that is because I must think that all ls8 kernels are in beta.
Man, I really gotta get some sleep
Sent from the little guy
Related
So ive flashed ics on my friends SII but from the beginning it had touch problems, for example in the app drawer i have to tap setting 3 times before it registers the touch. For eveything else it works just fine so im sure its not HW related.
Switching kernel improved it (also improved scrolling lag).
Is this a known existing problem with the current kernels? I dont own a galaxy sII so i dont know the issues that are playing atm.
Thanks in advance!
Sent from my Galaxy Nexus using xda premium
no problem might be bad flash or early beta release that you flashed by mistake
Nah, i thought the same but after flashing again the problem still was there.
Gonna try returning to stock and start again with CM9 Resurrection Edition with Odin. If it still persists i gues the problem is hardware related.
and suddenly everything changes.........!
weren't you on stock ICS before? please use stock with full wipe to test such things.
atifsh said:
and suddenly everything changes.........!
weren't you on stock ICS before? please use stock with full wipe to test such things.
Click to expand...
Click to collapse
I dont think you understood what i said mate
Please check my threads, i know how to test roms but thanks for your reply.
Yes i didnt get it,
Thsts why i said go back to stock using odin after full wipe.
If you already did it, cant help uou anymore.
Hi all, and thanks for reading this tread,
I have some issues and I'm hoping someone here could help shed some light on.
I was on ICS 4.0.3 and avoiding 4.0.4 due to brickbug issues. but I guess I couln't resist anymore and decided to give it a try. I tried to stay far away from buggy kernel so I used mobile odin to flash I9100XWLPT plus siyah 3.5.2 on one go
the result was a failure however, kernel flashed but firmware wiped (S2 logo was appearing but nothing else / softbrick ?).
Then I said oh well its not (hard)bricked or anything so I decided to use odin to flash I9100XWLPT, than siyah. It went ok but I lost mtp connectivity, tried s3 ported ui... didn't fly as well . Maybe something wrong with siyah 3.5.2 I thought, so tried an older siyah which I did not have an issue with h4.0.3. Situation did not improve however.
Then I flashed my old 4.0.3 and wiped, all ok mtp ok, upgraded to 4.0.4, all go, mtp ok.
Flashed siyah 3.5.2, mtp fails again. Tried android's own factory reset (not the on the boot menu, one on the personalization menu). Ended up with soft brick again (no boot only charging animation and odin mode). Flashed 4.0.4 again.
But this trial and eror process is going more dangerous by the minute I guess, so I decided to ask for support.
Do I do anything wrong? I want to upgrade to 4.0.4 everything as close as possible to stock, plus root and tocuhwiz from s3. its not too much to ask I guess.
Any suggestions and any explanations are very welcome also,
I'll thank any useful comments
kind regards,
I have 4.0.4 since 4th July with its stock kernel and it works perfectly well, I upgraded from 4.0.3 but I never did any wipes just updated on top of 4.0.3 and booted the phone, rooted from chainfires CF root thread, try it that way, worked for me and still is working.
ag4751 said:
I have 4.0.4 since 4th July with its stock kernel and it works perfectly well, I upgraded from 4.0.3 but I never did any wipes just updated on top of 4.0.3 and booted the phone, rooted from chainfires CF root thread, try it that way, worked for me and still is working.
Click to expand...
Click to collapse
Thanks If all else fails I'll try that, but siyah is a good kernel and it seems to be more battery efficient too.
If its a problem I failed to check with siyah I can go 4.0.4 kernel way but it makes me nervous to run a buggy kernel.
emk2z said:
Thanks If all else fails I'll try that, but siyah is a good kernel and it seems to be more battery efficient too.
If its a problem I failed to check with siyah I can go 4.0.4 kernel way but it makes me nervous to run a buggy kernel.
Click to expand...
Click to collapse
Totally agree Siyah is good I used it on 4.0.3 but it seems to fail on 4.0.4 at the moment I have not actually tried the latest one so it may well be good but I am looking to upgrade to SG3 next week so just want to keep my phone going for the time being no more playing around with this one until I have my new one.
I am using LQ5 which is reported as the buggiest but I can honestly say I have not had any problems at all, battery life appears good enough to me, depends how much you use it I guess.
Try speedmod k30 kernel, completely safe, fast and battery efficient
Sent from my GT-I9100 using xda app-developers app
Hayth said:
Try speedmod k30 kernel, completely safe, fast and battery efficient
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, pardon me if I'm being paranoid but I just read a tread about nand corruption so, this isn't something like that I assume. (Odin flash failed and left me with soft brick out of the blue). Did not notice anything about siyah 3.5.2 either so the problem may be with my phone memory.
P.S Prior sentence reads as "Please prove me wrong"
I switched to speedmod kernel, and figured siyah had MTP problems with either 4.0.4 ics or 3.5.2
I asked same questions to those kernels' respective topics & thus this tread fulled it's purpose. Thanks kindly for anyone who read & replied
Sent from my GT-I9100 using xda app-developers app
Thread closed
Question answered, thread closed per OP's request
Ok, so ive had a couple of problems with my recently bought Sgs2, ive got all the other problems fixed except this one: when i turn on the camera app, the flash goes on and off once, the same happens when i turn off the camera. Its a very fast flash that occurs.. it doesnt matter what camera app i use, it does it everytime.. the flash does work properly during camera use if needed, and works normally as a torch.
It doesnt bother me much, but would be nice to get fixed..
Any ideas?
If your using a custom jb rom then it's normal. It's a known bug.
Sent from my Galaxy SII
*boy*racer* said:
If your using a custom jb rom then it's normal. It's a known bug.
Sent from my Galaxy SII
Click to expand...
Click to collapse
Im using SlimICS 4.2+ Siyah 5.0.1
So he said.... That if You using not stock rom flash bug be...
Looks like he said: if its a custom JB rom, the bug occurs. Im using ICS and the same thing happened before i even flashed a custom rom. The phone was running a stock Samsung GB rom then..
"He" has a name
And if u said it happened before flashing roms, Then it must be a hardware issue.
Sent from my Galaxy SII
I have the same problem, that the flash will light up shortly when the camera app closed, and when I read the last comments it seems that this is a known issue for quite a while.
How does it come that this is not fixed yet. I'm using custom roms now for a few month now and from the beginning I was wondering about the strange flash behaviour compared to the stock rom.
Is it because there is still no official release from Samsung for JB or why is it so difficult to fix? Are the camera drivers closed source?
*boy*racer* said:
"He" has a name
And if u said it happened before flashing roms, Then it must be a hardware issue.
Sent from my Galaxy SII
Click to expand...
Click to collapse
I feared this was the issue.. oh well, i guess ill just have to live with it until i change my phone again, no biggie
elfrawg said:
I have the same problem, that the flash will light up shortly when the camera app closed, and when I read the last comments it seems that this is a known issue for quite a while.
How does it come that this is not fixed yet. I'm using custom roms now for a few month now and from the beginning I was wondering about the strange flash behaviour compared to the stock rom.
Is it because there is still no official release from Samsung for JB or why is it so difficult to fix? Are the camera drivers closed source?
Click to expand...
Click to collapse
It happened to you after switching to custom roms?
elfrawg said:
I have the same problem, that the flash will light up shortly when the camera app closed, and when I read the last comments it seems that this is a known issue for quite a while.
How does it come that this is not fixed yet. I'm using custom roms now for a few month now and from the beginning I was wondering about the strange flash behaviour compared to the stock rom.
Is it because there is still no official release from Samsung for JB or why is it so difficult to fix? Are the camera drivers closed source?
Click to expand...
Click to collapse
Mongopusher42 said:
I feared this was the issue.. oh well, i guess ill just have to live with it until i change my phone again, no biggie
Click to expand...
Click to collapse
Guys, it has got nothing to do with the hardware, its a random one that happens with all ICS and JB based custom roms
@Sun90
If you read the whole thread , i had the problem before custom roms with a 100% stock Samsung GingerBread rom..
Mongopusher42 said:
@Sun90
If you read the whole thread , i had the problem before custom roms with a 100% stock Samsung GingerBread rom..
Click to expand...
Click to collapse
have u tried flashing a Stock ICS rom (v4.0.3) and seen for the issue
if not give it a try and see, just to confirm whether its really a hardware issue or a software one
nothing to loose though, if the problem gets resolved for u it would be fine right
do a clean wipe before installing.
Sun90 said:
have u tried flashing a Stock ICS rom (v4.0.3) and seen for the issue
if not give it a try and see, just to confirm whether its really a hardware issue or a software one
nothing to loose though, if the problem gets resolved for u it would be fine right
do a clean wipe before installing.
Click to expand...
Click to collapse
Nope. Okk , ill try this when i have some spare time :thumbup:
Sun90 said:
Guys, it has got nothing to do with the hardware, its a random one that happens with all ICS and JB based custom roms
Click to expand...
Click to collapse
I used to get that on my x10i with certain roms.Definitely a software problem.
Same issue here, came about randomly day before yesterday. LED flashes once, quickly, whenever something tries to activate it.
Only ever used stock soft/firmware, and Chainfire's kernel. Cleared all caches, tried factory reset, problem persisted.
Flashed to whatever the latest ICS is for H3G today, problem still persists, I shall try official kernel tomorrow, see if that fixes it -- I don't hold much hope.
*boy*racer* said:
If your using a custom jb rom then it's normal. It's a known bug.
Sent from my Galaxy SII
Click to expand...
Click to collapse
I'm using hellybean 4.2.1 and I don't have this bug!!
Hi all. I'm relatively new to rooting, and was wondering how to flash a decent, stable Kernel, which is compatible with Omega. Baseband is: I9300XXEMV1, ROM details: Omega v44.3 XXUFMB3.
I have tried a few starting with Siyah, but I had skmilar results including instand forcd closes of most apps.l, and sometimes the phone wouldn't even boot. I figure I'm more than likely doing something wrong, considering other users don't have these issues after completion. I have been downloading the Kernels from Omega files and from there I use ROM Manager to boot into recovery. I then flash the kernel which then triggers the issues mentioned above. My gut feeling is that I probably need to use Odin on my pc to avoid these problems. I've heard good things about Siyah kernel which drew me to it. Is it compatible with Omega? Or is downloading and flashing using just my phone a bad idea?
Any advice would be greatly appreciated. If I have posyed this in the wrong topic I do apologize! And please if there is already a topic regarding the above essay please guide me to it and I'll leave you alone.
Sent from my GT-I9300 using xda app-developers app
XsjadoX said:
Hi all. I'm relatively new to rooting, and was wondering how to flash a decent, stable Kernel, which is compatible with Omega. Baseband is: I9300XXEMV1, ROM details: Omega v44.3 XXUFMB3.
I have tried a few starting with Siyah, but I had skmilar results including instand forcd closes of most apps.l, and sometimes the phone wouldn't even boot. I figure I'm more than likely doing something wrong, considering other users don't have these issues after completion. I have been downloading the Kernels from Omega files and from there I use ROM Manager to boot into recovery. I then flash the kernel which then triggers the issues mentioned above. My gut feeling is that I probably need to use Odin on my pc to avoid these problems. I've heard good things about Siyah kernel which drew me to it. Is it compatible with Omega? Or is downloading and flashing using just my phone a bad idea?
Any advice would be greatly appreciated. If I have posyed this in the wrong topic I do apologize! And please if there is already a topic regarding the above essay please guide me to it and I'll leave you alone.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
There are no compatible kernels for Omega 44.3 because is based on the leak 4.2.1 version of jelly bean. I think that until Samsung doesn't release a new version, more stable and with 4.2.2 version, there will be no compatible kernel.
Such a shame. I'll have to start from scratch then I suppose. Thanks for the help!
Sent from my GT-I9300 using xda app-developers app
Finally managed to get my phone working again...But can someone tell me what went wrong?
I was running JB NEATROM with SIYAH 4.1.5 Kernel. Strde I flashed GS2Wiper and then Dorimanx 9.42 kernel, then flashed CM 10.2. Booted and found all normal. went back and flashed Gapps system showing google maps , playstore error . Unable to use phone. Tried back flashing CM 10.2 and Slimbeam Rom working fine, but when flashing Gapps system gets stuck in booting logo.
Finally flashed old siyah kernel 4.1.5 and flashed NEATROM and to my big relief system operational. I want to update to JB 4.3 .Can someone please advice
are you doing a wipe and factory reset after all the different roms you are trying?
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
gastonw said:
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
Click to expand...
Click to collapse
Gaston, good to see you mate! Been stuck in another book for a few weeks?
@ OP: Beautiful summary by gastonw right here. Read the OP of the thread 2-3 times before flashing. You want to make sure it's compatible with your device, other mods/firmware, and that you know what you're doing during the install process.
Hey hopper, no, it's the UFC era now
Sent from the little guy