• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Nexus 4 Touchscreen Problem with 4.2

A

achunt

Newbie
So my nexus 4 is having its issues...but only with 4.2.2 and lower. I'm trying everything possible: flashing with stock Google images, custom ROMs, nothing seems to work and I can't figure out why! Did Google make it where if you have upgraded from 4.2.2 to anything newer 4.2.2 just doesn't work? I've tried other versions (4.3, 4.4, 4.4.2, 4.4.3, 4.4.4, 5, 5.0.1) and they all respond to touch. I even tried locking the bootloader back and it still didn't work. Anyone know why this is happening or have a solution? I do not have a SIM installed, but can get one if that is needed.
 
Hi @achunt :)

Quick question for you - if the more recent versions work, why don't you use them? 4.2 is pretty old in the scheme of things.

Second question: what method are you using to hop across all these versions? Are you flashing the full factory images? You'll need to make sure that you're matching up all the various pieces (recovery, bootloader, radio, etc) to make sure they play nice together. Having a mismatch there could easily cause problems.
 
codesplice said:
Hi @achunt :)

Quick question for you - if the more recent versions work, why don't you use them? 4.2 is pretty old in the scheme of things.

Second question: what method are you using to hop across all these versions? Are you flashing the full factory images? You'll need to make sure that you're matching up all the various pieces (recovery, bootloader, radio, etc) to make sure they play nice together. Having a mismatch there could easily cause problems.
Click to expand...
I'm wanting to use LuneOS, and it requires 4.2.2 to be installed. This isn't going to be my main phone. I'm trying to use the images Google provides, and even CyanogenMod but they both don't work. I'm pretty sure I'm flashing everything correctly because I'm using the flash-all script from Google directly to flash all the images.
 
Then you've checked about everything I can think of. :(

Out of curiosity, if you flash a touch-based recovery on top of 4.2.2, does the touchscreen work there?
 
achunt said:
I'm wanting to use LuneOS, and it requires 4.2.2 to be installed. This isn't going to be my main phone. I'm trying to use the images Google provides, and even CyanogenMod but they both don't work. I'm pretty sure I'm flashing everything correctly because I'm using the flash-all script from Google directly to flash all the images.
Click to expand...

I don't think the flash-all script stops at errors. It might be failing at one of the steps but continuing. If you open up the flash-all script you can see the steps and you can enter them one at a time in a terminal. I'll bet you'll see an error thrown in there somewhere and that would be very helpful. :)
 
lunatic59 said:
I don't think the flash-all script stops at errors. It might be failing at one of the steps but continuing. If you open up the flash-all script you can see the steps and you can enter them one at a time in a terminal. I'll bet you'll see an error thrown in there somewhere and that would be very helpful. :)
Click to expand...
Will try that right now. I'll post anything I find here.
 
Okay, this is what I received as output (with personal stuff removed). The only things I see as an error are the boo/recovery/system.sig but I've been told that those are not anything to worry about. Would the '-w' command be the problem?
p { margin-bottom: 0.1in; line-height: 120%; }
fastboot flash bootloader bootloader-mako-makoz10o.img

sending 'bootloader' (2188 KB)...

OKAY [ 0.148s]

writing 'bootloader'...

OKAY [ 0.328s]

finished. total time: 0.476s

$ fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.001s

$ fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img

sending 'radio' (54593 KB)...

OKAY [ 3.444s]

writing 'radio'...

OKAY [ 3.302s]

finished. total time: 6.747s

$ fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.001s]

finished. total time: 0.001s

$ fastboot -w update image-occam-jdq39.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: MAKOZ10o

Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.48

Serial Number........: 047x0000xx0xx0x0

--------------------------------------------

checking product...

OKAY [ 0.002s]

checking version-bootloader...

OKAY [ 0.002s]

checking version-baseband...

OKAY [ 0.002s]

sending 'boot' (5898 KB)...

OKAY [ 0.372s]

writing 'boot'...

OKAY [ 0.342s]

sending 'recovery' (6398 KB)...

OKAY [ 0.402s]

writing 'recovery'...

OKAY [ 0.405s]

erasing 'system'...

OKAY [ 0.280s]

sending 'system' (523357 KB)...

OKAY [ 34.743s]

writing 'system'...

OKAY [ 34.161s]

erasing 'userdata'...

OKAY [ 1.628s]

formatting 'userdata' partition...

Creating filesystem with parameters:

Size: 6189744128

Block size: 4096

Blocks per group: 32768

Inodes per group: 8048

Inode size: 256

Journal blocks: 23612

Label:

Blocks: 1511168

Block groups: 47

Reserved block group size: 375

Created filesystem with 11/378256 inodes and 50366/1511168 blocks

sending 'userdata' (98413 KB)...

writing 'userdata'...

OKAY [ 13.674s]

erasing 'cache'...

OKAY [ 0.041s]

formatting 'cache' partition...

Creating filesystem with parameters:

Size: 587202560

Block size: 4096

Blocks per group: 32768

Inodes per group: 7168

Inode size: 256

Journal blocks: 2240

Label:

Blocks: 143360

Block groups: 5

Reserved block group size: 39

Created filesystem with 11/35840 inodes and 4616/143360 blocks

sending 'cache' (10984 KB)...

writing 'cache'...

OKAY [ 1.482s]

rebooting...


finished. total time: 87.546s
 
^ Nope, that all looks good. The "-w" portion of the fastboot update command just tells it to wipe all file systems before flashing. That's a good thing, and it's definitely what you want for this. :thumbsupdroid:

So... I hate to admit it, but I think I'm stumped here. :( Luna?
 
codesplice said:
^ Nope, that all looks good. The "-w" portion of the fastboot update command just tells it to wipe all file systems before flashing. That's a good thing, and it's definitely what you want for this. :thumbsupdroid:

So... I hate to admit it, but I think I'm stumped here. :( Luna?
Click to expand...
That's what the people at XDA said too. It seems that it's not just stock android, its anything that is based on 4.2.x :(
 
You probably have, but have you flashed CM from custom recovery after flashing the 4.2.2 factory image?

I'm grasping at straws here. It would be great if you could get some logcat output going... but that would be pretty tricky without having a working touchscreen to enable it. :-/
 
codesplice said:
You probably have, but have you flashed CM from custom recovery after flashing the 4.2.2 factory image?

I'm grasping at straws here. It would be great if you could get some logcat output going... but that would be pretty tricky without having a working touchscreen to enable it. :-/
Click to expand...
I tried 10.1 and it's a no go with that too. :(
 
Last edited:
codesplice said:
You probably have, but have you flashed CM from custom recovery after flashing the 4.2.2 factory image?

I'm grasping at straws here. It would be great if you could get some logcat output going... but that would be pretty tricky without having a working touchscreen to enable it. :-/
Click to expand...
Log I got from TWRP. Saw it said something about OmniROM or something on line 280.
 

Attachments

Last edited:
achunt said:
Log I got from TWRP. Saw it said something about OmniROM or something on line 280.
Click to expand...
I *think* that OmniROM line is just a part of the build.prop that gets loaded by recovery (based on whatever ROM files were used to compile it - I think). I do know that dees_troy is one of the guys behind TWRP, so it makes sense that his signing test keys would be used.
Code: 
ro.build.description=omni_mako-eng 5.0.1 LRX22C eng.dees_troy.20141223.110921 test-keys
ro.build.fingerprint=google/omni_mako/mako:5.0.1/LRX22C/dees_troy12231110:eng/test-keys

Otherwise, I don't see anything in that log that would help us - it would really be helpful to have access to the logcat/dmesg log that runs while the OS is running. You could pull it from adb - but you'd have to be able to use the touchscreen to allow the adb connection. :-/

The MultiROM route may work, but I'm not entirely sure how it handles conflicting major release versions. Do let us know how it works!
 
codesplice said:
I *think* that OmniROM line is just a part of the build.prop that gets loaded by recovery (based on whatever ROM files were used to compile it - I think). I do know that dees_troy is one of the guys behind TWRP, so it makes sense that his signing test keys would be used.
Code: 
ro.build.description=omni_mako-eng 5.0.1 LRX22C eng.dees_troy.20141223.110921 test-keys
ro.build.fingerprint=google/omni_mako/mako:5.0.1/LRX22C/dees_troy12231110:eng/test-keys

Otherwise, I don't see anything in that log that would help us - it would really be helpful to have access to the logcat/dmesg log that runs while the OS is running. You could pull it from adb - but you'd have to be able to use the touchscreen to allow the adb connection. :-/

The MultiROM route may work, but I'm not entirely sure how it handles conflicting major release versions. Do let us know how it works!
Click to expand...
Doesn't CyanogenMod have adb pre-enabled?
 
codesplice said:
Hmm, that's a good question. It's been a long while since I used CM last; I've just been using stock+root lately.

It could be worth a shot!
Click to expand...
I used AOKP on my nexus 7 when I got it, and I'm pretty sure it had adb enabled by default, same with my optimus g when it worked and I had CM on it. Will look in a bit before a flash MultiROM.
 
achunt said:
It says adb offline, so it won't extract anything. I can't register the computer to work with adb
Click to expand...
That's what I was afraid of. Recent releases (I can't remember how long) have required an explicit whitelist of what computers (based on a fingerprint) are allowed to connect to adb on the phone. It's easy enough to confirm the fingerprint when you get prompted... but you need the touchscreen to work to do that. :(
 
codesplice said:
That's what I was afraid of. Recent releases (I can't remember how long) have required an explicit whitelist of what computers (based on a fingerprint) are allowed to connect to adb on the phone. :(
Click to expand...
Yeah, found a program called adbcontrol but that isn't working. Looking to find something to work.
 
You must log in or register to reply here.
Back
Top Bottom