Loading Screen Messed Up After Jailbreak! (Pic Inside)

[NocturnalEVO]

Hopefully someone can help me out, cz its buggin the crap outta me..

I jailbroke today, and everything seems to be workin fine, except for 2 things..


I have an iPhone 4 with 4.0.1 firmware


1. When I restart the phone (black screen w/silver apple logo), I'm getting 2 odd lines at the top of the screen. I restored twice and when non-jail broken, they don't appear. However, everytime I jailbreak, they show up, always in the same location.

See picture below:

2. In Winterboard, everytime I exit the application after making a change, the phone restarts (black screen w/silver apple logo, same as above, however it has the spinning loading thing over the apple). And then goes back to the lock screen as normal.

Normally in the past on all my iPhones, after you exit Winterboard, it usually freezes for about 5 seconds on the homescreen, and then takes you to the lockscreen. That's what I'm used to seeing, im wondering if the phone restarting is something messing up, or if its supposed to be like that now.


Regardless, if anyone can chime in, i'd really appreciate it. Thanks a bunch!

 

[Kyeris]

It seems like this is what happens now during a respring.

 

[j3yq]

I have the same thing on my iPad but on the right hand side.

 

[dukebound85]

it is a common thing op. Don't sweat it

 

[bw1128]

happens to me when respring too. seems to be the norm

 

[barr08]

Glad it's not only happening to me!

 

[moussekateer]

It'll happen to everyone who uses the new jailbreak. It's normal. Want a (quite interesting) explanation why it happens?

Comex's jailbreak is a high level userland jailbreak. The problem with userland jailbreaks is the runtime code has to be stored somewhere, and it's more difficult here. So comex and co did something clever. They encrypted the jailbreak payload as coloured pixels and stored it in the buffered frame that displays when iOS is starting up or respringing.

To sum it up, those coloured pixels are the jailbreak code. If you had a good enough eye you could read off the RGB values of the colours and convert them to runtime code.

 

[Chodite]

It'll happen to everyone who uses the new jailbreak. It's normal. Want a (quite interesting) explanation why it happens?

Comex's jailbreak is a high level userland jailbreak. The problem with userland jailbreaks is the runtime code has to be stored somewhere, and it's more difficult here. So comex and co did something clever. They encrypted the jailbreak payload as coloured pixels and stored it in the buffered frame that displays when iOS is starting up or respringing.

To sum it up, those coloured pixels are the jailbreak code. If you had a good enough eye you could read off the RGB values of the colours and convert them to runtime code.

Mind blown.

 

[NocturnalEVO]

Thanks a bunch guys! Really appreciate the consolation lol

moussekateer, thanks a bunch for explaining, much appreciated!

 

[Snowman3459]

It'll happen to everyone who uses the new jailbreak. It's normal. Want a (quite interesting) explanation why it happens?

Comex's jailbreak is a high level userland jailbreak. The problem with userland jailbreaks is the runtime code has to be stored somewhere, and it's more difficult here. So comex and co did something clever. They encrypted the jailbreak payload as coloured pixels and stored it in the buffered frame that displays when iOS is starting up or respringing.

To sum it up, those coloured pixels are the jailbreak code. If you had a good enough eye you could read off the RGB values of the colours and convert them to runtime code.

Just when I think I learned a lot about technology...a genius comes up with this stuff.

Indeed, mind blown.

 

[iWeldonJ]

Just when I think I learned a lot about technology...a genius comes up with this stuff.

Indeed, mind blown.

Hello! of course there's going to be weird things happening here and there. You're messing with a stable product and opening up to anyone so it's going to run weird.

I jailbroke one phone back in the day and it was doing some annoying things. the smoothness was gone and I never jailbroke again and things work great.

 

[Snowman3459]

Hello! of course there's going to be weird things happening here and there. You're messing with a stable product and opening up to anyone so it's going to run weird.

I jailbroke one phone back in the day and it was doing some annoying things. the smoothness was gone and I never jailbroke again and things work great.

I'm not exactly sure why you quoted me. I'm not the one who freaked out about it...

 

[xraytech]

It'll happen to everyone who uses the new jailbreak. It's normal. Want a (quite interesting) explanation why it happens?

Comex's jailbreak is a high level userland jailbreak. The problem with userland jailbreaks is the runtime code has to be stored somewhere, and it's more difficult here. So comex and co did something clever. They encrypted the jailbreak payload as coloured pixels and stored it in the buffered frame that displays when iOS is starting up or respringing.

To sum it up, those coloured pixels are the jailbreak code. If you had a good enough eye you could read off the RGB values of the colours and convert them to runtime code.

HOLY COW!!!

REALLY?!?

 

[Emberwild]

Was worried about this too. First time jailbreaking so thanks!

 

[LoLife]

Man the stuff that you people know and figure out is amazing

 

[sidewinder]

They encrypted the jailbreak payload as coloured pixels and stored it in the buffered frame that displays when iOS is starting up or respringing.

Hold on a second. Let's not make this sound more amazing than it is. They did not encrypt the jailbreak payload as colored pixels. They stored the code in the file used for the reboot image. That code "corrupts" part of the image and that is what we see as colored pixels.

S-

 

[ahfu25]

Hold on a second. Let's not make this sound more amazing than it is. They did not encrypt the jailbreak payload as colored pixels. They stored the code in the file used for the reboot image. That code "corrupts" part of the image and that is what we see as colored pixels.

S-

HATER!!.....JK!...LOL......Yes you are correct!

 

[x.leviathan]

Hello! of course there's going to be weird things happening here and there. You're messing with a stable product and opening up to anyone so it's going to run weird.

I jailbroke one phone back in the day and it was doing some annoying things. the smoothness was gone and I never jailbroke again and things work great.

Might I direct you out of the iPhone Hacks section? Probably more appropriate for you.

 

[dhlizard]

Might I direct you out of the iPhone Hacks section? Probably more appropriate for you.

My thoughts exactly.

If one has decided jailbreak wasn't for them, what is to be gained by monitoring these threads ? That said, of course everyone is entitled to browse where ever they choose.

 

[MajesticNJ]

Mind blown.

+1

 

[revirus]

It'll happen to everyone who uses the new jailbreak. It's normal. Want a (quite interesting) explanation why it happens?

Comex's jailbreak is a high level userland jailbreak. The problem with userland jailbreaks is the runtime code has to be stored somewhere, and it's more difficult here. So comex and co did something clever. They encrypted the jailbreak payload as coloured pixels and stored it in the buffered frame that displays when iOS is starting up or respringing.

To sum it up, those coloured pixels are the jailbreak code. If you had a good enough eye you could read off the RGB values of the colours and convert them to runtime code.

Where do you get this info?

 

[moussekateer]

Where do you get this info?

Some programming experience and lots of previous jailbreak experience and peeking at the jailbreak code. Also this:

The glitches on the boot screen are normal. You're looking at the kernel shellcode jailbreakme uses (temporarily stored on the framebuffer).
9:18 AM Aug 2nd via web

@planetbeing So if we were to accurately re-encode the color data on the screen into its RGB values we would get shellcode?
9:28 AM Aug 2nd via web

@FxChiP If your camera or eyesight is good enough, sure.
9:32 AM Aug 2nd via web in reply to FxChiP

But sidewinder is right, it is more correct to say the coloured pixels are a consequence of the code corrupting the image rather than the code being encoded itself. But you could still theoretically work backwards from the colour of the pixels to get the code again.

Hold on a second. Let's not make this sound more amazing than it is. They did not encrypt the jailbreak payload as colored pixels. They stored the code in the file used for the reboot image. That code "corrupts" part of the image and that is what we see as colored pixels.

 

[revirus]

Thank you for the info.