Device won't stop glitching out even in non-jailbroken state

[andrewwiik]

Hello qwerty,

I woke up to my screen glitching out all crazy (never touched custom screen resolution tweaks) so I decided I'll just reboot... still persists... okay... maybe on more reboot.... still happens when in unjailbroken mode.... okay lets erase all content and settibgs..... nope is still happening. I know this isn't a hardware issue with my screen btw.

[kpwn]

This is a pretty awful bug report, and have absolutely no clue what you might be talking about.

[andrewwiik]

I'm sorry I can't really provide more information. I'm trying to get a picture now of it to upload, it is less glitchy in apps but SpringBoard is totally fucked

[terry-au]

You should probably elaborate on some things: Does it occur when the device is booting, on the boot screen (Apple logo)? Have you checked what it may appear like through Quicktime display mirroring? Does it respond to input? How do you know it's not a hardware issue?

AFAIK, no permanent changes are really made, at least none that would actually be active when booting in a non-jailbroken state.

[andrewwiik]

[OGKevin]

😂😂👌🏾👌🏾 "pretty awful bug report "

On 2 feb. 2017 13:11 +0100, kpwn notifications@github.com, wrote:

This is a pretty awful bug report, and have absolutely no clue what you might be talking about.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub (https://github.com/kpwn/yalu102/issues/374#issuecomment-276941483), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARGTBkuyl8fGInbgceOjgIf_1a-tyY5xks5rYcf0gaJpZM4L1Ba6).

[andrewwiik]

Happens always now, can't be in any state with out it

[kpwn]

Looks like your screen is toast.

[andrewwiik]

It is better in certain apps which is how i know it isn't the screen

[andrewwiik]

and before it starts loading the system and is just in iBoot the screen is also fine

[kpwn]

Certain apps and iBoot may use the screen differently.

Your GPU may be toast, for instance. I am very positive this is a hardware bug, but I will try to make a testcase for you to try. Do you have aptickets saved for 10.2?

[OGKevin]

Can u provide a pick of when ur in an app?

On 2 feb. 2017 13:15 +0100, Andrew Wiik notifications@github.com, wrote:

It is better in certain apps which is how i know it isn't the screen

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/kpwn/yalu102/issues/374#issuecomment-276942462), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARGTBjuvjEW8SshzjoUyXnv378Rsu-Dcks5rYcj0gaJpZM4L1Ba6).

[andrewwiik]

by APTickets do you mean blobs?

[andrewwiik]

[andrewwiik]

this is what i mean about better in certain apps @kpwn

[kpwn]

By aptickets I do mean blobs.

That screen looks awfully like hardware corruption by the way, and it's even clearer in this screenshot (notice the vertical lines? well turns out making a vertical line is not easy for memory corruption, since screen orders pixel left to right overflowing in the next line). I find it hard to believe that this is software induced, although it could be.

[andrewwiik]

Um yes I do I believe, I had someone save them for me, let me see if I can find them hold on

[kpwn]

write your generator to nvram and restore 10.2 and see if issue persists.

[andrewwiik]

okay

[OGKevin]

I also think this is hardware, did u try quicktime mirroring like @terrry1994 said. I think the mirror may look just fine.

On 2 feb. 2017 13:20 +0100, Andrew Wiik notifications@github.com, wrote:

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/kpwn/yalu102/issues/374#issuecomment-276943294), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARGTBg_HkSRiNnQpEbwXYq-y1D5AG5aCks5rYcn_gaJpZM4L1Ba6).

[andrewwiik]

@OGKevin @terry1994 QuickTime isn't giving me the option of my phone as a screen, only mic

[titelheld]

@andrewwiik start quicktime, File > New Movie Recording > recording window should open, next to the record button select iPhone from the dropdown menu.

don't forget to connect your iPhone to your mac.

[andrewwiik]

I know, it only has iPhone for microphone

[TheMoleCZ]

A similar thing has once happened to me when I was jailbroken on iOS 6 or 7. Vertical lines and also everything was displaying only in the left corner of the screen, the rest was either lines or black. Everything was fine after I restored the device so I think this could also be a software issue.

[OGKevin]

Hmm, ill need to do some research. I thought if it was a partial hardware malfunction it should still be able to mirror. So if my initial thought is wrong, then  this means that without a good functioning GPU u  can't use screen  mirroring.

On 2 feb. 2017 13:32 +0100, Andrew Wiik notifications@github.com, wrote:

@OGKevin @terry1994 QuickTime isn't giving me the option of my phone as a screen, only mic — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[OGKevin]

If you have Blobs saved u can indeed try and restore as it wont matter anyway if it was a hardware issue, meaning it will still be present after restore. If its software based then it should be indeed fixed after a restore.

On 2 feb. 2017 13:48 +0100, TheMoleCZ notifications@github.com, wrote:

A similar thing has once happened to me when I was jailbroken on iOS 6 or 7. Vertical lines and also everything was displaying only in the left corner of the screen, the rest was either lines or black. Everything was fine after I restored the device so I think this could also be a software issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[andrewwiik]

Going through the entire guide lol, takes a long time

[andrewwiik]

Request URL set to https://gs.apple.com/TSS/controller?action=2 TSS server returned: STATUS=94&MESSAGE=This device isn't eligible for the requested build. ERROR: TSS request failed (status=94, message=This device isn't eligible for the requested build.) Sending TSS request attempt 1... [Error] sep firmware isn't signed Failed with errorcode=-3

[andrewwiik]

Any ideas?

[andrewwiik]

@kpwn

[Pamnki]

[Error] sep firmware isn't signed You need to use ios 10.2.1's sep

[andrewwiik]

how

[Pamnki]

Just take baseband and sep from ios 10.2.1's ipsw

[andrewwiik]

didn't work? am i getting something wrong? just copy the two files?

[Aerozolic]

@andrewwiik use this guide: http://www.ipodhacks142.com/how-to-restore-to-ios-10-2-unsigned-using-prometheus-on-iphone-ipod-touch-or-ipad/

if you don't have openssh installed you might want to use this guide for ssh instead: https://www.reddit.com/r/jailbreak/comments/5r2mwr/tutorial_how_to_use_dropbear_ssh_via_usb_on/?st=iyogmndz&sh=396a552b

[andrewwiik]

I am, I get the baseband and SEp files from 10.2.1 IPSw and placed them in the Downgrade folder but get that error

[andrewwiik]

WIll have results on whether restore worked in about 10 minutes I believe @kpwn

[andrewwiik]

@kpwn I did a restore using prometheus and I still have the problem, looks like I'm taking a trip to the apple store to buy a new one, now the trouble of finding one on 10.2

[mmhobi7]

@andrewwiik Did you try a simple screenshot? Happened to my friends phone and its stock Easiest fix would be a new phone

[andrewwiik]

A screenshot displays the correct screen for a split second @Aaahh

[OGKevin]

U can get a screen replacement without them updating your 📱.

On 2 feb. 2017 15:56 +0100, Andrew Wiik notifications@github.com, wrote:

@kpwn (https://github.com/kpwn) I did a restore using prometheus and I still have the problem, looks like I'm taking a trip to the apple store to buy a new one, now the trouble of finding one on 10.2

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (https://github.com/kpwn/yalu102/issues/374#issuecomment-276979585), or mute the thread (https://github.com/notifications/unsubscribe-auth/ARGTBoZPygUwVJ0fCfzWFs3HPkVFsscSks5rYe6ngaJpZM4L1Ba6).

[andrewwiik]

The screen isn't the issue @OGKevin It recieves touches fine and if I screenshot it shows the correctView for a split second

[OGKevin]

oh yea true, it is your GPU not sure if they will replace that indeed.

On 2 feb. 2017 16:15 +0100, Andrew Wiik notifications@github.com, wrote:

The screen isn't the issue @OGKevin It recieves touches fine and if I screenshot it shows the correctView for a split second — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[andrewwiik]

@kpwn sorry for this question and you can DM me @andywiik on twitter with the answer if you don't wanna share publicly but when can I anticipate the i7 10.1.1 supported version? I'm asking because I'm debating what device to buy outright if they rep is willing to go through serial numbers

[andrewwiik]

@kpwn I have concluded Yalu was not at fault, you may close this issue, thanks for your time

[kpwn]

I am curious about what was the cause behind this, by the way.

[andrewwiik]

I think the GPU is bad in someway, or processing stuff wrong as screenshots make the screen look fine for a second.

[andrewwiik]

@kpwn I wanted to give you an update along with my conclusion on this whole thing.

So all in all I was able to get phone to work again which meant it was a software thing. But I wanna explain what I think it was and see if you agree.

So when substrate safe-mode was broken I would use the set "Display Zoom" setting in Settings under "Display & Brightness". This "Zoom Mode" is the same way tweaks like Upscale and Littlebrother work. A little over a year ago I was beta testing Upscale on a old iPod 5 and when you set the resolution too high the screen would start to tear and stuff. I now remember it looked very similar to what I had now. I had assumed i had fixed the glitching on my iPhone 6 by pressing on a certain spot on the screen, but that wasn't it... It was right after i had finally been able to get past setting the display zoom after restore. I believe my abusive use of setting display zoom as a easy respring caused it's values to somehow become corrupt, and they finally got corrected after i had gotten past that step in setup.

[mmhobi7]

yeah that makes sense because it was display framebuffer tearing