I need help with my iPhone 3Gs

[danielq12]

I tried updating my iPhone with iPad base band to 5.1.it1 firmware which ended up fine, I activated the phone, and everything went okay. I had to turn it off, and when I tried to boot it back on with redsn0w (because it's tethered) a white screen would pop up, and then the screen would go to a faint green light and, first blue then green/grey, stripes that went from one side to the other horizontally on the bottom half, something like the paint drawing I have added.. ANY help, or advice is greatly appreciated, and I am very desperate to fix this problem. Thank you for your time.

[H4CK3R]

Let's just start off by saying: You made a MAJOR mistake. With devices on iPad baseband, you don't just 'restore' or 'update' them. They can ONLY be updated via a custom IPSW. Otherwise, you'll end up with something you have which can wreck your iPhone.

If you haven't already tried it, try putting the phone in DFU mode and see what happens.

[danielq12]

I did use a custom IPSW that was made with redsn0w, and yes I have tried putting it in DFU mode, when I tried booting it back up it went into DFU mode perfectly.

[H4CK3R]

Just try restoring from there then bro.

[danielq12]

I did try restoring it. First in Pwned DFU mode, with the custom IPSW and I get error 28. Then in normal IPSW without the Pwned DFU mode and I got error 1600.

*Note* When the phone is in this state (with the stripes, etc.) neither redsn0w or itunes will read it, and I can put it into DFU mode again.

[H4CK3R]

It seems to be something with your security software, etc. This is what Apple says about those errors:

These errors typically occur when security software interferes with the restore and update process. Follow Troubleshooting security software issues to resolve this issue. In rare cases, these errors may be a hardware issue. If the errors persist on another computer, the device may need service.

BUT, It could be a hardware issue.

[i.Annie]

Oh god, error 28. Why are these showing up so frequently nowadays? Ugh, okay what you wanna do is let the battery fully drain. Once you get that error 28 the first time, this is what you must first try. Simon and I were just in a thread the other day with an error 28 and the issue was resolved by allowing the battery to drain.

If you know how, you can disassemble your device and take the battery out, let it rest for 30 minutes, then put it back in. If you don't want to open it up, then I would suggest draining the battery. This can take days, maybe 5 days or so. Typically once you get the error 28, everything else you try won't work. I could be wrong, but that's what I've observed.

Edit: Be absolutely sure the battery is complete drained or it won't work. You'll just end up charging it up again when you plug it into your computer for the restore. So be sure it's completely drained.

[H4CK3R]

Oh god, error 28. Why are these showing up so frequently nowadays? Ugh, okay what you wanna do is let the battery fully drain. Once you get that error 28 the first time, this is what you must first try. Simon and I were just in a thread the other day with an error 28 and the issue was resolved by allowing the battery to drain.

If you know how, you can disassemble your device and take the battery out, let it rest for 30 minutes, then put it back in. If you don't want to open it up, then I would suggest draining the battery. This can take days, maybe 5 days or so. Typically once you get the error 28, everything else you try won't work. I could be wrong, but that's what I've observed.

Edit: Be absolutely sure the battery is complete drained or it won't work. You'll just end up charging it up again when you plug it into your computer for the restore. So be sure it's completely drained.

I completely forgot about this, lol! But I believe taking the battery out and letting it sit out for a few hours does the same too, correct? I can't help but think I read this before.

[i.Annie]

Yes lol! I said that H4CK3R! PAY ATTENTION BRO.

[2k1]

Parrot want a cracker.....

[i.Annie]

Hahaha Mikey, you big bully.

[danielq12]

I doubt it was a hardware because it was working fine up until I tried booting it up again.

[i.Annie]

I doubt it was a hardware because it was working fine up until I tried booting it up again.

You're right, I don't think it's a hardware issue as well. Which is why I suggested the battery drain. If it is hardware related, the battery drain will not help anything. If it is NOT hardware related, the battery drain will resolve your issue.

[H4CK3R]

Yes lol! I said that H4CK3R! PAY ATTENTION BRO.

Whoopsy lol. I read the first part and started making a reply lol. Worst. Mistake. Ever.

Parrot want a cracker.....

I don't even eat crackers... Lol.

[danielq12]

is there anything else youvguys suggest I try, because I REALLY don't want to take it apart.

[i.Annie]

Yes if you read my post, I suggested to let the battery drain. It can take 5 days or so to completely drain the battery.

[H4CK3R]

is there anything else youvguys suggest I try, because I REALLY don't want to take it apart.

Honestly, it's not that hard to take it apart. There's tutorials all over the internet on how to do it.

I seriously can't think of anything else to reccomend besides this. But we never said you had to take it apart.

[i.Annie]

If you really want to resolve error 28, you should let it drain. Try as you may everything else, but the battery drain is the best solution I can give. Like I said, I and another moderator had just helped another member resolve this issue the other day specifically with error 28. He took the battery out himself, but it is the same effect if you just let it drain for 5 days or so.

Edit: by "letting it drain" I mean just don't use the phone. Just let it sit, don't charge it, don't use it, just let it sit for a few days.

[danielq12]

okay well I will try it and see what happens thanks a lot for your help.