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

Root something is not right...

surfologist87

Android Expert
Ok, so i have a new evo im rooting for my wife, and i rooted it, just like i have with mine many many times, and everything was fine. Used unrevoked 3.2.
Then, i flashed netarchy 4.1.8...which ive used many many times, same file that ive had, works great.

But, when i put it on hers, it screwed up the display, there were all these lines and it was flickering....so on.
I reflashed netarchy, and it went away.
Then today i rerooted my phone, and when i flashed netarchy, i got the same weird display lines, flickering, colors were kinda off...
and then magically it disappeared.

What the heck is this...Ive rooted many many times and never seen this..why did it all of a sudden show up?
 
Maybe it has something to do with the havs?? Thats the only thing I can think of. But its defiantly weird its never done it before...
 
Maybe it has something to do with the havs?? Thats the only thing I can think of. But its defiantly weird its never done it before...

Well, i read about the bugs with HAVs and i havent used those yet. On netarchys page here, im using the kernel underneath the havs, the "Older non-universal builds".

But the weird thing is, i have it saved on my computer, and its the same one that ive reflashed back to my phone countless times, but it just now started this issue.

And ive rerooted because ive completely wiped and started from scratch a few times, been trying some new and different things.
 
Also, just to be clear, this was all using the 'stable' 4.1.8
I havent even used 4.1.9 or even 4.1.9.1

I just put 4.1.9.1 with aggressive undervolting on and ima try it out today
 
if I recall correctly 4.1.8 had some issues that had to do with nova panels vs epson panels

he corrected 4.1.9 to work well with either
 
Here's where i meant to post this....

I had this EXACT same issue. I thought i killed the screen, but notice that it doesn't do it during bootup. It first happened to me on netarchy's kernels (tried 3 of 'em), then tried King's #11 and had the same issue. It was intermittent though, would only happen after about 2 reboots using any different kernel. Ultimately, i performed the dalvik/cache wipes in RA recovery and resorted back to the stock #10 kernel. I've been too weary of trying a different kernel ever since...
 
That is really odd.. I wonder why it does that.
Oh well. Using the stock #10 kernel, does the wireless tethering app still work?
Ive read that wireless tethering had some issues with stock kernels..
 
Back
Top Bottom