Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.
08-26-2012, 07:24 PM #1
my iphone 4s is stuck in reboot, help?
so ive got this iphone 4s for sprint...stuck in boot loop..apple logo is there for about 5 seconds, disappears and then shows back up for 5 more seconds and continues for forever. when trying to restore normally i get itunes error 21...if i put it into DFU mode, i get same thing, itunes error 21...if i put it into recovery mode and try to restore, same thing, itunes error 21...if i shift restore while in recovery mode, i get itunes error -1....ive never even heard of negative one and nothing on google even mentions that error...does anyone have any clue at all what i could do? ive even tried ireb, tiny umbrella and recboot...nothing ...any suggestions?
08-26-2012, 08:12 PM #2
Error occurs when one uses the "last ditch" method for preventing baseband updates on the iPhone 4. The baseband does not get updated using this method. Use TinyUmbrella to kick it out of recovery mode.
And error 21
Custom firmware restore fail (PwnageTool since 4.1). You have to put your device into the DFU mode and not into recovery mode. Device won't boot correctly an stuck at the Apple logo after the error. Press and hold power and home button until it reboots.
Error when using Sauriks server for a restore with iOS 5.x in the recovery mode at least on a A5 device.
This error can also happen when you try to restore an iPod with hardware dfu. Use iREB r5 to solve this.
You are trying to update to a beta firmware without UDID activation.
08-26-2012, 08:49 PM #3
thank you but as ive said ive tried all off those in every possible order and condition i could think of and i always get one or the other error. this phone has never been jailbroken before. it was simply plugged in to a computer to charge, went blank and began the continuous reboot. itunes never even launched so idk...
08-26-2012, 11:13 PM #4
You've tried both custom and stock firmware?
08-27-2012, 07:16 PM #5
09-03-2012, 08:24 AM #6
09-03-2012, 10:38 PM #7
I would try restoring from recovery mode to stock firmware on a different computer.
09-14-2012, 06:05 AM #8
It sounds like a defect.