Hello
I installed the KANG ROM found in the following thread [ROM][KANG]CM9 ICS 10.1 WiFi Preview 02/08/12 and the boot screen seems to refresh/scroll endlessly. Once the lock screen comes up (which scrolls endlessly as well), if I press the power button to turn screen off and then switch it back on, the display is stable.
I use the Korean Version SHW-M380W (Galaxy Tabl 10.1 Wifi 32GB). I tried Galaxy Task Slim 13.1 and other ICS Roms found on XDA, but the result is same.
Can someone please let me know a fix for this?
Thank you so much.
Ping
Ping...
Doesn't anyone else face this issue?
I don't think it supports the korean tab
Hmm I saw that if I restore /boot from stock image backup in HC 3.2 this issue was solved. Tried and tested it and worked fine. But when I upgrade to ICS, there is no /boot to restore from. Just tried it with the Hc 3.2 /boot and the system hanged.
Probably different ramdisks as ics kang is based of devices they own and custom via the model as the Korean tab is not part of it you may need to request or hope someone donates one to them, and if it was the official update of ics it would work but these are custom made builds based off the source ics package given by Google so it isn't an official update like HC3. 2
Sent from my GT-P7500 using Tapatalk
Thanks
Thank you for your reply.
have you tried romans?
Romans
You mean the AOKP one right? Yeah, I have tried it, but the same issue
I mean, the one from here: http://forum.aokp.co/page/releases
Build 28 to be specific. Strangely, the same (screen jumping) issue was there with CWM as well. And pershoot was kind enough to make a new CWM just for Korean tab. I wonder what changed though (Am quite a newbie to rooting and stuff, so dont really know where to go to)
The pershoots CWM which fixed a screen jumping issue for CWM (not for boot screen though) is found here: http://forum.xda-developers.com/showthread.php?t=1360588
Thanks bro.
So its all fixed?
Oops, I missed the whole point Actually, I had tried that after the [ROM][KANG]CM9 ICS 10.1 WiFi Preview 02/08/12 version, but the issue persisted. Its only with the bootscreen that this issue exists. Once we go to the lock screen, the issues still exists, but a screen off -> screen on (using the power key) quickly restores the screen back to the non-fluctuating version.
Wait, why havent you used kang by Roman? Its already coming to 4.0.4
Build 29
Thanks Misledz: I tried out Build 29 located in the following page:
http://forum.aokp.co/page/releases
Still the problem persists
I think you need a clean wipe, like generally wipe everything off it, a factory reset and stock firmware flash, then see if it persists.
Only this solution worked for me on EU version:
http://forum.xda-developers.com/showthread.php?t=1555984
Tried that but still no luck
snpetit said:
Only this solution worked for me on EU version:
http://forum.xda-developers.com/showthread.php?t=1555984
Click to expand...
Click to collapse
I guess I have the same recovery. The issue is not with the scrolling recovery, but with the scrolling lock screen. Did it get fixed for you as well? Am using AOKP build 30.
Thank You!!!!
snpetit said:
Only this solution worked for me on EU version:
http://forum.xda-developers.com/showthread.php?t=1555984
Click to expand...
Click to collapse
Thank you so very much!! The issue which was bothering me for the last three months is now solved. Life saver..
Hey Guys, With my stock GB and even with ICS update, all were going fine. But when I tried to flash a new ROM like JB, xNovathor, CM9, CM10, CM10.1 (actually I've tried them all!), after flashing completed, I restart my phone. but since then touch doesn't work at all. Start screen appears and even I can take the screenshots, but touchscreen doesn't response at all. If anyone know the solution, please GIve me a Feedback! Thanks in advance!
Sorry to bring up such a silly issue.
But I never encountered any problem like this. So, pls help me out....
I have a WT19i device which being modded with various custom rom at various time.
for more than 1.5 years I didn't got into any kind of problem. and it all messed up.
Yesterday I was trying to install Super jelly bean 8.0 rom.
to do that,
1. I flashed nAa's kernel
2. Wiped whatever needed.
3. Installed rom's zip and gapps
4. Reboot my device.
Everything working well except i don't have any touch response....!
Then I re-flashed my stock 4.0.4 rom, and then everything working fine. (including touch)
Again I flashed cm10 kernel and then installed Cm10 rom
Same problem again, no touch response.....
I really want to install jelly bean rom to my device.
So, pls give me a solution.
Sry if this [Q] is bothering.
I posted this topics to few other places with no solution yet.
Right now, I am on with stock ics rom on my LWW
When I flashed any ics custom or stock rom my touch works fine.
But whenever i tried to flash any custom JB/KK rom to my device according to the procedure i end up with a touchscreen bricked device.
Hardware keys works fine. Everything works fine except touch screen.
I really need some help r8 now.
I tried...
1. cm10
2. cm11
3. Super jellybean 8
4. bean streak etc.
All ends up with a bricked touch screen.
then i flash back to stock and everything is r8.
(I should mention that, I changed my touch screen few weeks ago)
Now plz give me suggestion, what should I do?
Sorry to post this question fellow members, I've been looking for several days without any luck. I was gonna post this quetion in the ROM thread, but thought it was the wrong place.
Currently running LiquidSmooth 4.4.4 on a Verizon LG-VS895 and just NOW noticed the stock camera was gone. I was wondering how to port the stock files back into this rom. I really miss the gimmicky stuff (like magic focus) and was wondering how to eliminate the camera that comes with this rom and revert to the stock camera.
I downloaded a stock rooted rom and tried seeing if i could move files over from it to my phone, but I'm unsure of where to start. Sorry in advance if this has been posted or if I'm a stupid newb, but this is driving me bananas.
I tried flashing camera mod hoping that would restore it, but that didn't work either. So, this question is based off of a fresh install of this rom.
Thanks