TriJetHero
macrumors 601
i would try again to get it in DFU, and restore in itunes as you changed the host file
iPod Touch 4G Bricked?!?! *URGENT HELP*
- Thread starter PlankingBob
- Start date
- Sort by reaction score
PlankingBob
macrumors newbie
It is in DFU, its constantly in DFU, and im trying now, its still stuck on: waiting for ipod... While the ipod displays the logo and the progress bar, with no progress 
FlatlinerG
Cancelled
Ok, its still completely unusable, and if your not going to post anything actually constructive, dont post at all
It is in DFU, its constantly in DFU, and im trying now, its still stuck on: waiting for ipod... While the ipod displays the logo and the progress bar, with no progress
Let's save everyone some time here. How are you putting it in DFU and what does it look like while it's in DFU mode. This will clear up any confusion.
Second, you keep saying it won't turn on and that it's bricked, and yet you tell us that the iPod has a progress bar and an Apple on it...meaning it turns on it just isn't restoring.
Explain what you think is DFU mode and we can start attempting to help from there. Otherwise, everyone in this thread is just going to keep going in circles.
PlankingBob
macrumors newbie
Ok, let me clarify... I did not put it into DFU, and yes, im 100% sure its in DFU, as i opened up redsn0w to try and put it into PWND DFU, but it said was in "soft DFU" The troubles started after a failed update to 6.0.1, and now the screen is completely lifeless, and any attempts to hold buttons etc, is useless... And when i try and restore it, the screen comes to life, with a progress bar that does not move, and itunes constantly saying "Waiting for iPod" BUT when using redsn0w to try and restore, it says "waiting for NAND (Memory)" Hope that helped shed a bit of light on my situation
PlankingBob
macrumors newbie
Well i managed to get it into PWND DFU mode, but still gets stuck on "waiting for iPod" or (using redsn0w) "waiting for NAND" And i dont think its salvageable... Might take it to the apple shop and see if they can do anything with it... Thanks for your input guys! Ahh, so many hours wasted, and now im just giving up, seems a shame :/
Ahh, so many hours wasted, and now im just giving up, seems a shame :/
TriJetHero
macrumors 601
it needs to be in regular DFU not pwned DFU.
PlankingBob
macrumors newbie
Dont worry, tried that too! Ive been in all 3 DFU types and still nothing! Its obviously a hardware issue, as redsn0w says waiting for NAND... Now my question is, would this at all be covered by apple after the 1 year warranty, as it happened during the install of IOS 6.0.1
gngan
macrumors 68000
How will you prove to apple that it happened during the install of iOS 6.0.1? If you can then i suppose Apple would give you an exception.
.macbookpro.
macrumors regular
If your in Europe you may want to know this.
The European Directive 1999/44/EC says all EU countries have to ensure a retailer could be held liable for all "non-conformities" which manifest within two years from delivery.
However, because the Sale of Goods Act (SOGA) meets or exceeds most of the directive's requirements, this overrides the EU directive. The act requires three things: the goods must be as described; they must be of satisfactory quality, which is determined by description, price, durability, freedom from minor defects; and they must be fit for purpose.
Because manufacturers tend to give one year's warranty on goods, retailers will usually push you in their direction if the product breaks inside the first year.
However, SOGA provides cover for goods bought for up to six years – in England and Wales. This means if a TV fails after 13 months, you still have rights. Assuming the item has failed through no fault of yours, and it was "reasonable" to expect it to last longer – given its cost/quality – you should demand, under the Sale of Goods Act, that it be replaced or repaired by the retailed, not the manufacturer. Once the item is six months old, the onus is on you, the consumer, to show the item failed as a result of a manufacturing fault.
Redjericho
macrumors 6502a
I have always wondered if this was true...
What if you -theoretically- brought your device's battery down to where it only displayed the "Connect to charger" symbol, and then repeatedly pressed the home button so it would keep making the symbol appear therefore draining the battery even further. The battery would then get so low that it would not only cease displaying the symbol, it wouldn't even have enough power to recognize that the charger has been connected.
This is a serious issue that Apple needs to address in next-generation devices, or I may quite possibly consider switching to a phone brand that is not plauged by this epidemic, such as the solar-powered F88 Wrist Phone
I hear they are making a serious impact on iPhone sales, Apple had better be taking notes on this -clearly- superior design.
Intell
macrumors P6
I've had a few iOS devices' batteries completely die. They are so dead that the clock is reset to 1970. You just simply plug them into a source of power and they'll turn on within five minutes.
MadDriver13
macrumors newbie
I have the same problem with 2 ipod 4 I try every think I asked many professional technician and all have the same result, put the ipod in garbage if you lose the warranty with apple or give it back to apple and it's gonna charge you $$$ and you'll have a new one, it's like you said a hardware problem, something went wrong with the memories!!
Ever consider it's a HARDWARE issue?
I agree with most of the posts here: It's nearly impossible to "software brick" an iDevice. It is easily possible, however, to have a hardware fault and have it wreak havoc with a restore/software.
At this point, with all the troubleshooting you've done, I'd bet a dollar it's hardware related.
Just look at the oodles and oodles on eBay in great shape that cannot be restored. It's not because of software, it's because of an unknown hardware fault (if the sellers could fix them, they would, it's a LOT more $$$).
Sadly hardware faults (especially on a 4G) mean it's time for a new one (unless you have warranty/AC of course, but I'm guessing that's a big no there?).
Good luck!
I agree with most of the posts here: It's nearly impossible to "software brick" an iDevice. It is easily possible, however, to have a hardware fault and have it wreak havoc with a restore/software.
At this point, with all the troubleshooting you've done, I'd bet a dollar it's hardware related.
Just look at the oodles and oodles on eBay in great shape that cannot be restored. It's not because of software, it's because of an unknown hardware fault (if the sellers could fix them, they would, it's a LOT more $$$).
Sadly hardware faults (especially on a 4G) mean it's time for a new one (unless you have warranty/AC of course, but I'm guessing that's a big no there?).
Good luck!
dontpannic
macrumors 6502
*sigh*
No, itjw, I don't think they considered it was a hardware issue...
I just heard about this new thing called "sarcasm". It's relevant to situations like this. You should investigate further.
dontpannic
macrumors 6502
I'm well aware what sarcasm is, but it didn't come across from your post. Not exactly my fault, is it?
Same problem as OP. Tried running it dead, didn't work. Buttons or reset doesn't do anything, stays on a black screen. Plug in and hit restore and the iPod will freeze at the progress bar with iTunes saying "Waiting for iPod".
Basically I can't even get the Apple logo to come when resetting etc. Any ideas? Doesn't seems like iTunes can't access whatever chip the firmware is written to.
Basically I can't even get the Apple logo to come when resetting etc. Any ideas? Doesn't seems like iTunes can't access whatever chip the firmware is written to.
TriJetHero
macrumors 601
Check the thread you started