[Q] Avatar Rom - touchscreen - Sprint HTC EVO 4G LTE

I flashed the Avatar Rom(stable release) using twrp 2.4.1.0 on my evo with the 3.16 firmware. Everything boots up fine but my touch screen does not work and i dont know why. Does anyone know why the touchscreen might not be working?

You have the 3.16 touch panel. You cannot run aosp roms with that. Look for captain throwback's firmware thread and get the 3.15 touch panel. Or get a 3.16 based Rom.

{ParanoiA} said:
You have the 3.16 touch panel. You cannot run aosp roms with that. Look for captain throwback's firmware thread and get the 3.15 touch panel. Or get a 3.16 based Rom.
Click to expand...
Click to collapse
Will the updated versions of any of the aosp roms be based on the 3.16 firmware?

droth21 said:
Will the updated versions of any of the aosp roms be based on the 3.16 firmware?
Click to expand...
Click to collapse
Not with out kernel source
Sent from my EVO using Tapatalk 2

kernel source out
Sent from my EVO

Related

Hboot 1.4 & ics

Is anyone working on making the latest ICS (with latest kernel) work with HBOOT 1.4?
edufur said:
Is anyone working on making the latest ICS (with latest kernel) work with HBOOT 1.4?
Click to expand...
Click to collapse
The latest OTA ICS from sprint works fine with hboot 1.4. Just be sure to flash the right .zip. Try this Here
Basic Sprint Stock Rom, zip-aligned with a few simple extras.
I'm on 1.4 and tribulattifather 's from works (well)
No need to update hboot with his rom like some others do
But does that include the new KERNEL as well? I noticed that the kernel build wasn't listed. Mean ROM is reportedly working for 1.4 as long as you don't take the new kernel. So my question still remains. Is anyone working on a way to make the new release / kernel / firmware work for 1.4?
coal686 said:
New kernel. MikeyXDA put out a new version of meanROM based on the new ota except uses the vm leak kernel. Works fine for older hboots. Flash the new kernel with it, get bootloop if on older hboot.
So I did some further research and to answer your question, no. Nobody has got the new kernel to work with older hboots. If you want to flash the new kernel, why not upgrade your hboot? People have had success doing that, no ill affects. plus its easy to revert to hboot 1.4 if you want.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse

New OTA and why you have to update build seperately.

Hey guys,
Just had a quick question. I'm not new to the rooting game and have been doing it for a while (g1 fwiw) but just had some questions since the new update came out. I'm s off so flashed the updated radios and packages from captain over in the android development forum. My question though is I don't ever remember having to flash an update like that. Ive flashed radios before but I thought the base came with the roms. Am I wrong? Is this different than usual for a reason or do I just have a bad memory. I might be wording my question weird but yeah, anyone with an idea?
I'm not sure what you mean, you flash the radio/firmware and rom and you're updated.
I guess my question is I thought all of that stuff usually comes packaged in a Rom. Except for the radio I thought the base and all that depended on what Rom you flashed and wasn't fixed.
Get_Out_and_Push said:
I guess my question is I thought all of that stuff usually comes packaged in a Rom. Except for the radio I thought the base and all that depended on what Rom you flashed and wasn't fixed.
Click to expand...
Click to collapse
Radios are stored in a separate partition from the ROM. I don't think I've ever seen a ROM package include one.
Sent from my EVO LTE
Roms are built off of different bases. That hasnt changed.
Flashing a rom will update the base (software version)
Rxpert said:
Roms are built off of different bases. That hasnt changed.
Flashing a rom will update the base (software version)
Click to expand...
Click to collapse
Ok thanks that's what I was trying to ask. No sleep makes me incoherent I guess. So Captains zip with everything from the ota was mostly about the radio since New roms will include an updated base and kernel?
Get_Out_and_Push said:
Ok thanks that's what I was trying to ask. No sleep makes me incoherent I guess. So Captains zip with everything from the ota was mostly about the radio since New roms will include an updated base and kernel?
Click to expand...
Click to collapse
Yes
Get_Out_and_Push said:
Ok thanks that's what I was trying to ask. No sleep makes me incoherent I guess. So Captains zip with everything from the ota was mostly about the radio since New roms will include an updated base and kernel?
Click to expand...
Click to collapse
Correct, the radios and other firmware bits are on the secured partitions that require a signed ruu in order to install if you are not s-off. The base software installs on the system partition so can be installed with just an unlocked bootloader through a custom recovery like twrp. That is why so many people that are s-on and the 1.15 hboot can't take advantage of the new radios. Their only option at this time would be to take the ota. They can however load the new kernel through fastboot or flash GUI and then install a custom rom that has the updated base.
Sent from my icrap 2 using Tapatalk HD

New Touch Panel Firmware?

After upgrading my TP firmware - I am no longer able to run any non 3.16 roms.
I have flashed the 3.15ver. TouchPanel firmware back to phone - but if I install any non 3.16 rom - my screen/touchpanel is dead.
It works in TWRP 2.4.1 only.
Is there any way to once again run CM or AOKP?
Thanks, Jack
Sent from my MeanBean optimized and supercharged ElteVO.
midmadn said:
After upgrading my TP firmware - I am no longer able to run any non 3.16 roms.
I have flashed the 3.15ver. TouchPanel firmware back to phone - but if I install any non 3.16 rom - my screen/touchpanel is dead.
It works in TWRP 2.4.1 only.
Is there any way to once again run CM or AOKP?
Thanks, Jack
Sent from my MeanBean optimized and supercharged ElteVO.
Click to expand...
Click to collapse
Nope, you msut use the 3.15 tp driver for 3.15 roms and aokp, cm etc
Sent from my EVO using Tapatalk 2
You say driver. I believe that is part of the rom. I did flash the 3.15 touch panel firmware back to the phone.
I tried the pac-man cm 10.1 rom as well as miui 4.12.
My touchscreen is dead once the phone boots into the rom. It only works in recovery or meanbean 3.2 (3.16) rom.
Sent from my MeanBean optimized and supercharged ElteVO.
Here try this. It is the old touch panel driver, which, according to the meanbean thread, allows you to use non 3.16 roms.
Just flash the PJ75IMG.zip thru bootloader
Credit to mikeyxda and capt. Throwback
http://themikmik.com/showthread.php...o-1-12-11-1210&p=286650&viewfull=1#post286650
Sent from my EVO using Tapatalk 2
bennyboy78 said:
Here try this. It is the old touch panel driver, which, according to the meanbean thread, allows you to use non 3.16 roms.
Just flash the PJ75IMG.zip thru bootloader
Credit to mikeyxda and capt. Throwback
http://themikmik.com/showthread.php...o-1-12-11-1210&p=286650&viewfull=1#post286650
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much for trying to help - but I already have that file and have flashed it through bootloader. That's what I was doing. From what was written in the meanbean thread - I should have been good to go. But no luck.
Anyone that flashed the new touchpanel firmware can not run any rom other than meanbean 3.? on or the stock 3.16 rom.
Sent from my MeanBean optimized and supercharged ElteVO.
On reverting the touchpanel - I was being a retard. (No offense meant to any MR persons)
You have to install the rom first and then run the 3.15 touchpanel firmware file.
Case solved. You must flash from the bootloader AFTER any non 3.16 rom install the 3.15 touchpanel firmware/driver.
Thanks to anyone that tried to help.
Jack
Sent from my MeanBean optimized and supercharged ElteVO.
midmadn said:
On reverting the touchpanel - I was being a retard. (No offense meant to any MR persons)
You have to install the rom first and then run the 3.15 touchpanel firmware file.
Case solved. You must flash from the bootloader AFTER any non 3.16 rom install the 3.15 touchpanel firmware/driver.
Thanks to anyone that tried to help.
Jack
Sent from my MeanBean optimized and supercharged ElteVO.
Click to expand...
Click to collapse
Ahh, glad you got the problem solved. Thanks for sharing that info as im sure other people will run into the same problem.
Sent from my EVO using Tapatalk 2
bennyboy78 said:
Here try this. It is the old touch panel driver, which, according to the meanbean thread, allows you to use non 3.16 roms.
Just flash the PJ75IMG.zip thru bootloader
Credit to mikeyxda and capt. Throwback
http://themikmik.com/showthread.php...o-1-12-11-1210&p=286650&viewfull=1#post286650
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
How do you flash from bootloader? i place the file on my phone but i go to bootloader and nothing happens
Edit: NVM im s-on

[Q] Camera broken after flashing Beastmode RC7 kernel

I just tried to open my stock Camera, and it immediately force closes.
The only thing I can think of that is causing this, is that I recently flashed a new kernel: http://forum.xda-developers.com/showthread.php?t=1800399 - ([Kernel][Sense][Dec 08] Beastmode-LTE Sweep2Wake | MpDecision [Linaro][Linux 3.0.56])
Now, I'm running stock rom 1.13.651.3 with latest updated "Firmware" - http://themikmik.com/showthread.php...wel-Firmware-Collection-Latest-3-16-651-3-OTA - (3.16.651.3 JellyBean OTA - LATEST)
"Full" Firmware zip
Includes Radio 1.12.11.1210, PRI 2.97_003 & a few other smaller updates.
NOT INCLUDED IN ZIP: HBOOT.img, recovery.img (stock), boot.img & tp_SYN3202.img*
*tp_SYN3202.img is touch panel firmware, which affects interaction with the touch screen. This latest firmware is ONLY compatible with ROMs that use the 3.16.651.3 boot.img/kernel, and TWRP Recovery version 2.4.1.0 or newer. If you plan on using an older base ROM, an AOSP ROM, or older version of recovery, then you should NOT install the below standalone file (as it will cause your touch screen to be unresponsive). However if you would like to run a 3.16-base ROM for a while to test it out and then go back to AOSP or the old base, you can downgrade to the 3.15.651.16 tp firmware from that section below PRIOR to changing to a different (non-3.16-base) ROM.
---
Has anyone else experienced this? I really use my cers on a daily basis. Sidenote: I know for a fact that the camera worked before flashing the new kernel. Also, I tried an aftermarket camera app, and it doesn't show anything in the background; just blackness.
PLEASE HELP ME FIX THIS! I really love the new kernel and don 't want to uninstall the kernel _just_ for a working camera.
Thanks in advance! - kal
Make sure you downloaded the right kernel. It appears that there are several kernels posted-one for the older base, which you are still on, and then others for the 2.13 base, which is slightly newer. Flash the one for the older base (at the top of post #2). If that doesn't fix it, try a different kernel altogether, as some kernels behave differently with some phones.
U can't use that kernel as its a ics kernel and ur runing jb
Sent from my EVO using xda premium
luigi311 said:
U can't use that kernel as its a ics kernel and ur runing jb
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Look again. He's on ICS SOFTWARE, not Jelly Bean.
The advice is free....the bandwidth, not so much
Why not just re-flash the rom
Ohhh I assumed that since he updated the firmware to the new jb firmware he was running jb
Sent from my EVO using xda premium

[Q] back again

ok so last week i was on here saying that i was having problems flashing roms to my phone. found out that because im s-on (also my hboot is 2.09) most roms i have to flash the kernal. so i was told to get the app flash image gui. i got it, flashed the kernal, it worked, but...... after the rom loaded my touch didnt work. i couldnt unlock the phone at all. so i went back to the previous rom. i tried another rom using the flash image gui and it did the same thing. it was as if the touch imput was gone. any reason why this happened? something i did wrong? thanks
What ROM did you flash and what version of TWRP are you on? If you took the latest OTA to software version 3.16 then you also got an update to the touch panel. Unless you get S-off and downgrade the touch panel, you have to use 3.16 ROM's and TWRP 2.4+.
Sent from my EVO using xda premium
FinZ28 said:
What ROM did you flash and what version of TWRP are you on? If you took the latest OTA to software version 3.16 then you also got an update to the touch panel. Unless you get S-off and downgrade the touch panel, you have to use 3.16 ROM's and TWRP 2.4+.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
the rom is jewel_PAC_JB_4.2.2-v22.0.1_20130401-180210.zip im using the TWRP 2.4 but flashing to 2.5 now
Like fin said, if you had the 3.16 ota on your device, the new touch panel drivers won't allow you to use PAC, you can't use anything but 3.16 based sense ROMs. You really will need to get s-off to enjoy your device. Good luck.
Sent from my EVO using xda premium

Categories

Resources