Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.
Thread: 3GS[new bootrom] completely dead after 5.1.1 jailbreak
is a discussion within the3G[S] Downgrading
forums, a part of theJailbreak / Downgrading / Upgrading
section;Hellooo, I've been tearing my eyes out recently when my 3GS died after I updated from 4.0 to 5.1.1 with preserved baseband . My iphone needs to be jailbroken to
...-
06-18-2012, 02:30 PM #1
3GS[new bootrom] completely dead after 5.1.1 jailbreak
Hellooo,
I've been tearing my eyes out recently when my 3GS died after I updated from 4.0 to 5.1.1 with preserved baseband.
My iphone needs to be jailbroken to work since I need to unlock it and hacktivate it. It worked really good in 4.0 but I felt I needed to update.
So I updated it with a customized IPSW from redsn0w and it went well. But then when I jailbroke it with the same program it has all been a nightmare.
It does only start when i plug it in my wall, and then it restarts after a while. When I pull out the cable it dies. It doesnt start when I plug it in to my PC, and I can't do anything without the wall cable.
I can however re-jailbreak it and update it to 5.1.1 again, but it doesn't make a difference.
What should I do?
Is this a common problem, that it doesn't work without a cord?
Can I downgrade it to some more stable IPSW? I don't have any blobs for my previous versions.
Please help, thanks.
Iphone 3GS, 5.1.1, new bootrom
Windows 7
-
06-18-2012, 02:41 PM #2
it could be either a software or hardware issue, if its a hardware issue, you're gonna have to get it fixed or upgrade to a better iphone
if its software, then its a simple restore and hopefully that fixes it...
the first thing we need to do is check to see if you "actually" dont have any shsh blobs as you said, download the program tinyumbrella and click the "SAVE SHSH" and verify for sure if you dont have any shsh blobs
if you do, you can downgrade to one of those iOS versions and do a test trial and see if the problem goes away
if you dont have blobs, then restore back to 5.1.1 again and do a trial test
-
The Following User Says Thank You to EVO For This Useful Post:
superjens (06-25-2012)
-
06-18-2012, 05:11 PM #3My iPhone is a Part of Me
- Join Date
- Sep 2011
- Location
- Europe
- Posts
- 785
- Thanks
- 9
- Thanked 100 Times in 99 Posts
One thing you can do is take it down to a stock 4.1. You don't need anything special for that... Atleast from there you can see if it will fire up again.
-
06-18-2012, 10:54 PM #4
-
06-19-2012, 11:15 AM #5
Thanks for the replies.
I really don't know if it's hardware/software... but I hope it's a software problem
I checked with tinyumbrella and I can see the blobs from previous versions there. Gonna try to downgrade.
If I downgrade with a stock 4.1, will I still be able to jailbreak, unlock, and so on?
And do I need to add/remove some values in the .host file??
Thanks againLast edited by superjens; 06-19-2012 at 02:50 PM.
-
06-19-2012, 01:52 PM #6
what do u mean regular 4.1?.......you mean a stock 4.1?.......if so then no, you need to create a custom 4.1 to preserve your baseband for unlock
use sn0wbreeze v2.9.6 to create a custom 4.1 firmware, and if you DONT have an official sim card to activate the phone, you need to select the "Activate iPhone" option...
and yes, check your hosts file for the entry
74.208.10.249 gs.apple.com, if its there then delete it..
-
06-19-2012, 02:52 PM #7
Thanks man, sorry, I'm swedish.
Will try that. Right now I can't downgrade to like 5.0.1 with iFaith - stitched IPSW, or any other version. So I hope that the 4.1 will do the trick.
-
06-19-2012, 02:54 PM #8
-
06-19-2012, 03:25 PM #9
In TinyUmbrella, it says
Installed baseband version: 05.13.04-6.4_M3S2
I have now checked the hosts file, and then tried to downgrade to a custom 4.1 IPSW from Sn0wbreeze, but I got a 16xx error from iTunes as usual.
Hmm, the only thing I've managed so far is to re-update it to 5.1.1, two times.
-
06-19-2012, 03:36 PM #10
-
06-20-2012, 06:20 AM #11
Nope, I have been trying with iREB and redsn0ws DFU pwner but nothing works
How come I can't even downgrade to 4.1? Or is it the stock 4.1 that always works?
Really don't know what i'm gonna do now!
-
06-20-2012, 06:42 AM #12
-
06-20-2012, 05:47 PM #13
is it still the 16xx error after putting it in PWNED DFU MODE?
if so, try using either a different usb port or different computer or BOTH...
it should not be this problematic because I just tested restoring to both a STOCK and CUSTOM 4.1 on my 3gs tester, and no errors came, but DONT DO A STOCK firmware, because it will update your baseband
-
06-24-2012, 09:24 AM #14
I have tried a couple of times now. It's really weird!
Gonna try another computer now.
So the baseband gets updated when I downgrade?
-
06-24-2012, 01:20 PM #15
-
06-25-2012, 05:24 AM #16
Allright.
Still can't downgrade with my blobs for 4.1 and a custom IPSW from either sn0wbreeze or iFaith.
Maybe it's time to say goodbye to my (i)faithful servant
-
06-25-2012, 05:49 AM #17
Why can't you? Explain to us what errors you're getting please.
-
06-25-2012, 06:20 AM #18
I get the 1602 or the 1601 errors all the time.
Recently I've just been having the 1601.
I don't know if my blobs are cutting it. Is it any difference with the .shsh-blobs and the .plist-blobs?
I got a bunch of "old" blobs from TinyUmbrella located in a folder on my computer. Have been trying with those but nothing seems to work.
-
06-25-2012, 07:21 AM #19
I'm taking this right from the Apple site for you, I'd reccomend you follow what it says

Errors 1601 + 1602: Follow the steps listed above for Error 1604. This error may also be resolved by disabling, deactivating, or uninstalling third-party security, antivirus, and firewall software. See steps in this article for details on troubleshooting security software.
Error 1604 (Just for your reference): This error is often related to USB timing. Try changing USB ports, using a different dock connector to USB cable, and other available USB troubleshooting steps (troubleshooting USB connections. If you are using a dock, bypass it and connect directly to the white Apple USB dock connector cable. If the issue persists on a known-good computer, the device may need service.
If the issue is not resolved by USB isolation troubleshooting, and another computer is not available, try these steps to resolve the issue:
Connect the device to iTunes, confirm that the device is in Recovery Mode. If it's not in Recovery Mode, put it into Recovery Mode.
Restore and wait for the error.
When prompted, click OK.
Close and reopen iTunes while the device remains connected.
The device should now be recognized in Recovery Mode again.
Try to restore again.
If the steps above do not resolve the issue, try restoring using a known-good USB cable, computer, and network connection.
-
06-25-2012, 08:58 AM #20My iPhone is a Part of Me
- Join Date
- Sep 2011
- Location
- Europe
- Posts
- 785
- Thanks
- 9
- Thanked 100 Times in 99 Posts
Why do you need blobs for 4.1? It's still signed
so just build a standard no BB Ipsw & try that.




LinkBack URL
About LinkBacks
Reply With Quote

