hey, any ideas whether it works for the cid TELNZ001. I got the same issue which the touch screen not working when i update to JB from ICS..
Thanks .
it *Could* work, and wont hurt to try, as long as you have a backup of your stock kernel.
hey, any ideas whether it works for the cid TELNZ001. I got the same issue which the touch screen not working when i update to JB from ICS..
Thanks .
I recall seeing a report of it working, worth a try as rjwdon says :good:hey, any ideas whether it works for the cid TELNZ001. I got the same issue which the touch screen not working when i update to JB from ICS..
Thanks .
hey, any ideas whether it works for the cid TELNZ001. I got the same issue which the touch screen not working when i update to JB from ICS..
Thanks .
Do you know if theres a similar boot.img for non-sense roms? Enjoying ViperX but I'm keen to play around with some other roms
Not yet,
but the source has just been released so here's hoping some devs get stuck in to it
Or can the devs make 3.14 based custom ones work with CIDs that are updatet to 3.17?
I guess they could if they looked at the 3.17 source an patched the 3.14 with the necessary fixes.
Unfortunately the usersbase with 3.17 is very small and I think kernel devs will see it as being unimportant. (I hope I'm wrong)
It seems that most devs base every thing off x.xx.401.x. So 3.17 might not come until 3.17.401.x comes out.
Will wait and see
Until then I'll keep using your miui_boot.img on ViperX , thanks mrberni
By that way, did you tried repacking viperx stock boot.img with my boot.img (not boot_miui.img)? Maybe some viperx specific settings/tweaks are lost when using boot_miui.img.
I upgraded hboot from 0.95 to 1.39, flashed ARHD 18.1 and straight away my touchscreen didn't work (nothing unusual I understand). I tried the kernels (both boot.img and boot_miui.img ) and modules supplied by mrberni http://xdaforums.com/showthread.php?t=2120714 which solved the touch issue but then I couldn't get a signal. HOX says no. Tried re-booting, re-flashing, re-everything. If I go through the hboot upgrade process again will that make any difference?
Did you flash the zip file in recovery? (for the modules) this is the biggest cause of no signal when flashing Kernels
going through the hboot update process won't help, trust me I've tried in the past
Dang it!
Yeah, I flashed the zip in recovery. I might try it again, then flash the boot image in fastboot. See what happens.
Try flashing the modules and recovery, then flash boot_miui.img via fastboot and erase cache before first boot.
If that does not work try repacking arhd boot.img with my boot.img.
Got it! Not sure where the problem was occurring, but problem solved.
Started fresh. Full wipe to begin with. Flashed mrberni's boot.img using fastboot. Installed ARHD zip and mrberni's modules in recovery. Now touch is working AND my phone has a signal! (touch still doesn't work in recovery though, but that's no biggie)
A big thanks to adamnz and mrberni for the assist.
Got it! Not sure where the problem was occurring, but problem solved.
Started fresh. Full wipe to begin with. Flashed mrberni's boot.img using fastboot. Installed ARHD zip and mrberni's modules in recovery. Now touch is working AND my phone has a signal! (touch still doesn't work in recovery though, but that's no biggie)
A big thanks to adamnz and mrberni for the assist.
Good to hear you got it sorted,
I'd recommend a non-touch recovery like this http://xdaforums.com/showthread.php?t=1941630&highlight=cwm
It make navigating in Aroma installer much easier.
As a side note, ViperX 3.3.7 works with the new ViperX kernel
If a recovery becomes available for us can we leave a link here? Would be great use to all of us
Sent from my HTC One X using xda premium