Database Users

OS not detecting proper screen size after flashing CWM

Hello everyone,
I've been a CM6 user on a G1 for some time (came rooted w/CM6), but I finally performed a root and custom rom installation myself for the first time last night on my new Atrix 4g.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1302423
I have the Bat2tF (atrix-specific CM7 build) installed, but what happens is toward the top of the screen, things are more or less correct, but the further down the screen I go, the more the button-to-screen position becomes off. For instance, half-way down the screen I have press about 3/16" below the soft "button" displayed on screen I want to select. This distance increases at a constant rate the further down the screen I go. What makes it so bad is by the time I get to the bottom, when I press the menu/home/back/search buttons, these actually control the dock and left-home/right-home shifters! This means once I start an application, I cannot go back and have to reboot the phone. Arrrrgh! And the orientation of the mis-map is always the same. If I tilt the phone horizontally, it still goes from the motorola label, down(across) to the led-lit menu/home, etc buttons.
It makes sense to me that something is thinking the screen is actually bigger than it is, since the (0,0) coordinate is the upper left of the screen. When I move down, it makes sense that the distance of the offset will become greater.
Some possibly relevant info:
After I unlocked the bootloader and flashed recovery, I booted the stock rom and everything was fine.
I then booted up into recovery backed up the stock rom, then did a factory wipe, followed by a cache wipe, followed by a dalvik cache wipe.
Clockwork then brought me to a page that said "data size" and "back button disabled" with several size options (e.g 128MB, 256MB,..., 1024MB). I wasn't sure what this was and chose 128MB, since my rom was < 100MB.
After this, I did not see an option to install a rom, so I rebooted into the still-present stock rom. This is when I first noticed the problem.
I then rebooted into recovery, which gave me the option to install a rom from sd, which I did.
CM7 flashed fine, but upon boot (and all boots hence), I have the problem.
What scares me is that it doesn't seem to be an OS problem, since it was present in both stock and custom roms. The screen graphics are laid out just fine.
I've searched around but could not find anything (which scares me all the more). Anyone have any suggestions? I want to cry....

someDewd said:
Hello everyone,
I've been a CM6 user on a G1 for some time (came rooted w/CM6), but I finally performed a root and custom rom installation myself for the first time last night on my new Atrix 4g.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1302423
I have the Bat2tF (atrix-specific CM7 build) installed, but what happens is toward the top of the screen, things are more or less correct, but the further down the screen I go, the more the button-to-screen position becomes off. For instance, half-way down the screen I have press about 3/16" below the soft "button" displayed on screen I want to select. This distance increases at a constant rate the further down the screen I go. What makes it so bad is by the time I get to the bottom, when I press the menu/home/back/search buttons, these actually control the dock and left-home/right-home shifters! This means once I start an application, I cannot go back and have to reboot the phone. Arrrrgh! And the orientation of the mis-map is always the same. If I tilt the phone horizontally, it still goes from the motorola label, down(across) to the led-lit menu/home, etc buttons.
It makes sense to me that something is thinking the screen is actually bigger than it is, since the (0,0) coordinate is the upper left of the screen. When I move down, it makes sense that the distance of the offset will become greater.
Some possibly relevant info:
After I unlocked the bootloader and flashed recovery, I booted the stock rom and everything was fine.
I then booted up into recovery backed up the stock rom, then did a factory wipe, followed by a cache wipe, followed by a dalvik cache wipe.
Clockwork then brought me to a page that said "data size" and "back button disabled" with several size options (e.g 128MB, 256MB,..., 1024MB). I wasn't sure what this was and chose 128MB, since my rom was < 100MB.
After this, I did not see an option to install a rom, so I rebooted into the still-present stock rom. This is when I first noticed the problem.
I then rebooted into recovery, which gave me the option to install a rom from sd, which I did.
CM7 flashed fine, but upon boot (and all boots hence), I have the problem.
What scares me is that it doesn't seem to be an OS problem, since it was present in both stock and custom roms. The screen graphics are laid out just fine.
I've searched around but could not find anything (which scares me all the more). Anyone have any suggestions? I want to cry....
Click to expand...
Click to collapse
Happened the same to me; you screw an unique partition which has mac addresses, touchscreen config, serial number, and other things...
You need to follow these thread:
http://forum.xda-developers.com/showthread.php?t=1131649
The fix is there but you will not get back your original configuration, so you will have to use a "universal" one.

Ah-hah! You are my hero.
So I scanned a few posts in the tread you linked me to. Did you guys determine that this pds partition contains hardware optimization configs (particularly, CPU settings)? I'd like to see if maybe I can find the original atrix pds (perhaps in the backup I created?) *crosses fingers*
In any case, my screen-button mapping is correct again and I'm rockin' CM7. Thank you!

someDewd said:
Ah-hah! You are my hero.
So I scanned a few posts in the tread you linked me to. Did you guys determine that this pds partition contains hardware optimization configs (particularly, CPU settings)? I'd like to see if maybe I can find the original atrix pds (perhaps in the backup I created?) *crosses fingers*
In any case, my screen-button mapping is correct again and I'm rockin' CM7. Thank you!
Click to expand...
Click to collapse
If you did a pds backup, then flash that, there is no optimization, its the same, but your backup has unique information, like teh serial number or the mac address

Okay, gotcha. I didn't specifically do a pds backup, but I do see a pds.tar in my /clockwork/backup directory. No .img, though (looked through the tar itself).
Since everything seems to be working to my satisfaction as of now, I'll pass on tempting fate and run with this. Thanks again!

someDewd said:
Okay, gotcha. I didn't specifically do a pds backup, but I do see a pds.tar in my /clockwork/backup directory. No .img, though (looked through the tar itself).
Since everything seems to be working to my satisfaction as of now, I'll pass on tempting fate and run with this. Thanks again!
Click to expand...
Click to collapse
checkyour cpu speed, there was a pds image which was a developers pds, and it only reach 501 mhz, if you can go to 1000mhz then you are good to go. Use cpuspy or setcpu

SetCPU is showing a full 1 GHz on both cores, using the pds file on the other thread. Sweet!
Now I can finally get back to homework. Yay!

nook color bricked please help me

i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(

Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.

Take a look at the restoring to stock section of the guide in my sig
Sent from space

Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk

i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(

I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.

bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.

i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody

More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.

you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working

Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)

hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...

[Q] No screen input from android / wm

Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.
I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.
I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).
I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.
I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.
Any ideas on how I can get touch working / get a NAND android rom to work again.
Thanks in advance guys

First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen
Go back to the hd2 nand toolkit
1.task29
2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.
3.Select magldr update recovery or cLK install recovery depending on your selection above.
4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.
5. Install ICS from sd card as before

Thanks for the help, I had to flash a different radio version to get magdlr to boot.
I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.
I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?

Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.

htccraze said:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
Click to expand...
Click to collapse
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks

http://forum.xda-developers.com/showthread.php?t=769026
I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.
Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.

Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.

htccraze said:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
Click to expand...
Click to collapse
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.
The ROM you linked, I can find download links on the page, not sure if I'm just missing them.
I just tried an SD card rom, its doing the same thing, no touch input is accepted.
Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.
I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.

Another update: I just restored to default using the method listed below.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.
WM boots fine and everything, but still no input is accepted.

I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
Sent from my HTC HD2 using XDA

Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.

It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
Sent from my HTC HD2 using XDA

This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!
The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.

Vegacomb - drawing is useless

Not sure if this is hardware or software, if it's software, is there a way to fix this?
when I draw anything on the Vega (Vegacomb latest version) in DrawSomething or any drawing app (big canvas), my lines look like I'm on a vibrating plate, it's completely unusable, occasionally vertical lines look OK, but anything else is unrecognisable
any ideas?

Its probably the touchscreen causing the problem as most roms fail to calibrate the screen correctly because of a flaw in the it7620 driver.
Try installing this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
The next release of vegaics should contain an improved driver that will enable proper calibration. The same driver can be used for vegacomb but would require someone building a rom with the driver included. As far as I know no one has done this yet and I dont think anyone is working on Vegacomb (I may be wrong) as ICS is getting all the love.

richardmlea said:
Its probably the touchscreen causing the problem as most roms fail to calibrate the screen correctly because of a flaw in the it7620 driver.
Try installing this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
The next release of vegaics should contain an improved driver that will enable proper calibration. The same driver can be used for vegacomb but would require someone building a rom with the driver included. As far as I know no one has done this yet and I dont think anyone is working on Vegacomb (I may be wrong) as ICS is getting all the love.
Click to expand...
Click to collapse
tried VegaICS, got the same, run calibrate in shuttle tools, got the same, did as you suggested above, installed the ROM, calibrated, formatted etc, installed ROM again, calibrated, then installed VegaICS again, got the same, rant calibrate in shuttle tools, got the same
it's not just me either, a work colleague has the same issue

camera all green and hangs

its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?

jnktechstuff said:
MOD : EDIT
try dleeting you who system, except your recovery , there should be a system whipe that should work, then reflash ur rom
Click to expand...
Click to collapse
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..

yeatsie said:
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
Click to expand...
Click to collapse
check you camera connector. It may come lose from the motherboard. Try reseat the connector.
Sent from my A500 using Tapatalk
.

opened up the A500 last night - all looked good, all connectors in place, nothing obviously wrong?
Noticed the screen when i switch to the rear camera has artifacts from other screens in the background (ie Pulse app title heading etc) suggesting some kind of software glitch?

yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
Known issue in the CM10 alpha test ROM. You should go to the one in general rather than making your own thread which WayDownSouth is unlikely to see.
http://forum.xda-developers.com/showthread.php?t=1789711

yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD

Moscow Desire said:
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Click to expand...
Click to collapse
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.

yeatsie said:
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
Click to expand...
Click to collapse
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD

Moscow Desire said:
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Click to expand...
Click to collapse
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..

yeatsie said:
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
Click to expand...
Click to collapse
Boot loader is different from cwm recovery. When you boot, it should say in white text.
If in doubt, run Acer recovery installer from the market. It will tell you which version.
MD

ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app

I have always had this intermittent problem on my a500. I have always used the stock ROM since I purchased it, and it's been the same since each OTA upgrade, so I doubt that it's a problem inherent to one custom ROM or the other.
A Dalvik cache clean has never worked for me, sometimes a restart has helped, but more often than not it doesn't help.
If someone discovers a set of steps that fixes this problem every time it occurs, I would be glad to hear of it.

yeatsie said:
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi, What was your final solution to this problem? I'm trying to fix mine right now.
-Thanks-

No fix as yet, pretty much gave up trying to use the camera.
Sent from my Nexus 7 using Tapatalk 2

If anyone else's having this problem with ONE OF THE CAMERAS (Not both of them but frontal OR main) then this should be the solution:
Watch this video someone uploaded https://www.youtube.com/watch?v=Cjevl8I6rIA but HAVE THIS IN MIND:
That cord (FLEX) he's talking about is for the FRONTAL camera. Not related with the main or back camera. So that should fix the green trouble for the frontal one.
But, if the main camera shows green image or weird lines, that's likely because its connector is not correctly attached to the main board. That connector is NOT a flex, but it's a built in block in the board of the same camera unit. You need to remove or lift the main board, totally remove the main camera unit, clean the connector (both male and female) with alcohol and connect it again applying some pressure. If the trouble really was the connector not being correctly placed, that totally fixes it.
If it worked, let me know

That totally worked and fixed my green screen camera problem, thanks! (was a total pain to re-seat the camera but worth it)