Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Reminds me of when were young: Sorry Mr Police man i wont do it again honest, until next time and i will get burned again.

Ironically I was in the middle of a phone call telling my friend it wasn't worth it to jailbreak his phone and I was going to switch it back. ha.
 
This is sad. I'm sorry that happend to you. I am getting a little worried about mine, but I left the stock boot logo on for that exact reason. :D So just in case, nobody will be able to tell.
 
This is sad. I'm sorry that happend to you. I am getting a little worried about mine, but I left the stock boot logo on for that exact reason. :D So just in case, nobody will be able to tell.

Lets just hope my friend can fix it. :(
 
Oh yeah no problem, let me grab that extra 600 dollars I have lying around.....



Oh wait.

If you took the risk of jailbreaking/unlocking the iPhone 3G then you must have extra money to buy another iPhone.

It also looks as though you took a lot of time to research on how to fix your iPhone in this forum. You should've taken the time to reseach if the unlocking/jailbreaking software was 100% reliable on your iPhone.

Like I mentioned before, you should just another one and if you can fix the bricked phone, then sell that one eBay. I'm sure you'll be able to break even or even make a profit.
 
If you took the risk of jailbreaking/unlocking the iPhone 3G then you must have extra money to buy another iPhone.

It also looks as though you took a lot of time to research on how to fix your iPhone in this forum. You should've taken the time to reseach if the unlocking/jailbreaking software was 100% reliable on your iPhone.

Like I mentioned before, you should just another one and if you can fix the bricked phone, then sell that one eBay. I'm sure you'll be able to break even or even make a profit.


I don't see how me taking the risk of jailbreaking my phone correlates with the amount of money that I have.

I saved up for the iPhone, the pwnage tool is reliable on the 3g phone, because on all of the iphone forums that I've posted on looking for help now that it's actually ****ed, I seem to be the only one having this problem.

I can't afford to buy another phone.
 
I don't see how me taking the risk of jailbreaking my phone correlates with the amount of money that I have.

I saved up for the iPhone, the pwnage tool is reliable on the 3g phone, because on all of the iphone forums that I've posted on looking for help now that it's actually ****ed, I seem to be the only one having this problem.

I can't afford to buy another phone.

This is exactly why Apple doesn't want people hacking their iPhones. Just because you're the only one (you know of) with this problem, doesn't mean that it's safe to jailbreak your iPhone. I don't really feel bad for you because you took the risk on your own KNOWING that you couldn't afford a new phone. If I could help you fix it, I would. I still don't see the advantage of skinning and NES, but that's just me. I personally think that your iPhone crapped out on it's own (regardless of the jailbreak) and now you're stuck with the custom images that points out that the warranty is void, but who can really say?

The reason why I came to this iPhone hacking forum is because I was *thinking* about hacking my iPhone when it comes, but after seeing your thread, I think I'll just keep it stock. Thanks for your story.
 
This is exactly why Apple doesn't want people hacking their iPhones. Just because you're the only one (you know of) with this problem, doesn't mean that it's safe to jailbreak your iPhone. I don't really feel bad for you because you took the risk on your own KNOWING that you couldn't afford a new phone. If I could help you fix it, I would. I still don't see the advantage of skinning and NES, but that's just me. I personally think that your iPhone crapped out on it's own (regardless of the jailbreak) and now you're stuck with the custom images that points out that the warranty is void, but who can really say?

The reason why I came to this iPhone hacking forum is because I was *thinking* about hacking my iPhone when it comes, but after seeing your thread, I think I'll just keep it stock. Thanks for your story.

I'm not asking for people to feel sorry for me, I'm just asking for possibly solutions and suggestions to my problem.

And I'm glad people might decide not to jailbreak after reading this thread.
 
I didn't read the whole thread, but just to make sure, you cycled the power on both the phone and the computers you are trying to restore the iPhone with, right?

I hope it works out for you, but as someone else said, it sounds like it might be a service issue causing this, and not you jailbreaking the 3G. Good luck.
 
I didn't read the whole thread, but just to make sure, you cycled the power on both the phone and the computers you are trying to restore the iPhone with, right?

I hope it works out for you, but as someone else said, it sounds like it might be a service issue causing this, and not you jailbreaking the 3G. Good luck.

yeah i did. :(

thanks
 
yeah i did. :(

thanks

OK try this. just bear with me

1. Plug the iphone into the computer and open up itunes
2. Click restore. if you get an error go to step 3
3. Keep itunes open and the phone plugged in
4. Hold down the power button and the home button for 10 seconds. When you see the apple logo/pineapple logo take your finger off of the power button for 10 seconds

Tell me what happens after that. hey if you have aim tell me your screen name and i can try to help you.

Edit: i found a fix for the 1604 error. Try this

I had the same error when I was restoring my iphone but I found a method that worked for me.

fixed it! All I had to do to get iTunes to finish the reformat without getting that pain in the *** error 1604 was:
1.) turn off the iphone and pull the chord from the computer

2.) uninstall itunes and ALL apple products that installed with itunes 7-4

3.) re-install itunes and ALL apple products that installed with itunes 7-4

4.) Pull the SIM card out of the top of the iphone
http://images.google.com/images?sou...2006-03,GGLR:en&q=iphone+SIM&um=1&sa=N&tab=wi

5.) reboot the iphone and get the dammed yellow triangle of death

6.) Turn on iTunes if it did not come on already to get itunes to see the iphone

7.) reformat the phone--(it should work by now)

8.) reinsert the SIM card in the iphone

9.) reactivate the phone

10.) Restore your data from the last back up

Taken form the help forums on apple. All I did was uninstall all the itunes stuff off in windows xp and took out the sim card on the iphone. did a fresh reinstall and attempted to restore again and it worked. Hopefully this might help you.
 
OK try this. just bear with me

1. Plug the iphone into the computer and open up itunes
2. Click restore. if you get an error go to step 3
3. Keep itunes open and the phone plugged in
4. Hold down the power button and the home button for 10 seconds. When you see the apple logo/pineapple logo take your finger off of the power button for 10 seconds

Tell me what happens after that. hey if you have aim tell me your screen name and i can try to help you.

Edit: i found a fix for the 1604 error. Try this

There is no "yellow triangle" with the 3g phones. That's the fix for the 1st gen iphones.
 
OUCH!, best of luck honestly :( best I can suggest if your totally snookered, is to shove it up on Ebay :( and begin saving :(
 
Here's a video of me putting it in DFU mode and trying to restore to prove I'm doing it right and it's not working. :(


http://vimeo.com/1397331

I love your voice!

Anyways... I do feel bad for you. I can hear a little bit of desperateness in your voice and I wouldn't want to be in your situation. I think the reason so many people were making sure you're doing DFU correctly is because a lot of of people do it wrong. They don't count, and they just don't know what they're doing. You certainly sound like you know exactly what you are doing and it appears that you are quite knowledgeable about the iPhone and the restore process. So, with that said, I truly am sorry for bashing you. You're a nice person and with good intentions... and my heart goes out to you.

extract from https://forums.macrumors.com/threads/462648/

If you get Error 1600 from iTunes (or if you see in your log a failure to prepare x12220000_4_Recovery.ipsw), try: mkdir “~/Library/iTunes/Device Support”
if that directory already exists, remove any files in it.

Original Poster: Have you tried this yet? Just run the official firmware again after making that directory or removing any files in it.
 
I love your voice!

Anyways... I do feel bad for you. I can hear a little bit of desperateness in your voice and I wouldn't want to be in your situation. I think the reason so many people were making sure you're doing DFU correctly is because a lot of of people do it wrong. They don't count, and they just don't know what they're doing. You certainly sound like you know exactly what you are doing and it appears that you are quite knowledgeable about the iPhone and the restore process. So, with that said, I truly am sorry for bashing you. You're a nice person and with good intentions... and my heart goes out to you.


yeahhh. Every time I try something new, I hold my breath and think "This is going to be it it's going to work again!" and it doesn't. :(

I won't get to see my friend thats a genius until the weekend and he hasn't been online to help me either. It's just sad having it with me all the time and staring at stupid steve jobs cartoon.

Original Poster: Have you tried this yet? Just run the official firmware again after making that directory or removing any files in it.

I've tried it with removing the files from that folder and restoring, and I've also tried deleting the file, and replacing it with another one. :/
 
I've tried it with removing the files from that folder and restoring, and I've also tried deleting the file, and replacing it with another one. :/

Do you use AIM? My screen name is "justspaztik" I'd like to talk to you. Also, I have another idea. What if you got it to the point where it shows the Apple logo, then quickly unplug it and bring it to a store to return it?
 
Do you use AIM? My screen name is "justspaztik" I'd like to talk to you. Also, I have another idea. What if you got it to the point where it shows the Apple logo, then quickly unplug it and bring it to a store to return it?

If I quickly unplug it, I can still hold home and power to turn it off, then once I hit power again the pineapple comes back and it goes into recovery / restore mode whatever it's called.


And yes my screen name is, "quick romances"

CREEPER ALERT!!

jk :p

I thought the name seemed familiar, I see you post on the rev3 forums too ohhoe :D

Yeah I do. Somebody over on the modmyifone forums accused me of being a covert apple employee, I think it's because I said the word "girl" and mentioned something technical in the same paragraph.
 
ok try doing exactly what you did in the video but instead of hitting shift when you click the restore button just hit the restore button.
if that doesnt work do what you did again,and at the end when you get the error go into dfu mode again right when the error appears.
 
ok try doing exactly what you did in the video but instead of hitting shift when you click the restore button just hit the restore button.
if that doesnt work do what you did again,and at the end when you get the error go into dfu mode again right when the error appears.

I've done this. :/
 
And yes my screen name is, "quick romances"

Haha, well glad to see you haven't lost your sense of humor. Truly sorry to hear about your nightmare. I hope someone finds a solution soon. Maybe one of those SIM-based hacks from Brazil may be able to bring your iPhone back. Hang tough! :)
 
Haha, well glad to see you haven't lost your sense of humor. Truly sorry to hear about your nightmare. I hope someone finds a solution soon. Maybe one of those SIM-based hacks from Brazil may be able to bring your iPhone back. Hang tough! :)

That wasn't a joke, it's really my screen name. haha.
 
Judging from the nature of the error, its likely to be a USB fault not a device fault. Do you have access to a USB 1.0 PC? Have you tried new USB drivers? Try motherboard specific usb drivers, i've had issues with my usb ports until i installed original drivers.

Hope it helps, I really doubt its a device fault.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.