Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Keep killing iPhones, can't figure out why

fenskezen said:
iTube 302 Valve Amplifier: That would start some conversation!
Click to expand...

http://www.fat-man.co.uk/docs/product_07/Carbon_Trinity_Hybrid_Valve_Amp_with_Speakers.shtml
Their flagship dock. It's a beauty.
And yes, this can actually blow up your iPhone. It pumps 50 watts of electricity, which means there's 10 amps of power to be dealt with at 5V.
5V 10A and 50 watts? Here's for a comparison. Turns out, that cube charger that comes with your iPhone is a monster. It pushes out 1A of power. How's that for a comparison?
 
AlphaDogg said:
Sure it can. I bricked my iPhone 2G while using bootneuter to unlock it. I accidentally hit the home button while it was flashing the baseband and it resprung. I thought nothing of it. Then when I rebooted it, it would only boot to the "connect to iTunes" screen. So I pushed the little i button to see my IMEI and ICCID and it said "unknown" for both. That's when I knew I bricked it. I gave it to my master jailbreaker friend and he told me that the bb chip is screwed. That meant that I needed a new comm board. So what did I do? I bought a 16GB iPhone 2G with a non functioning screen and took the logic board and comm board out of it and put it in my 8GB 2G, making it a 16GB. I leave it on my iHome iP9 and it works just fine as my alarm clock.

Tl,dr: iPhones can be bricked through (not thru :mad:) software. Get off your high horse.
Click to expand...


I did that plenty of times too unlocking iphone 2G's and I even turned off the iphone while it was running bootneuter and never bricked. All it needed was a DFU restore, maybe you should have researched a little further instead of relying on your "master Jailbreaker friend":rolleyes:
The BB chip is screwed? Ok.
You cannot permanently brick an iphone with just software, jailbreaking or unlocking. Get a clue before you talk and maybe teach your buddy about it also:D
Iphones cannot be bricked permanently THRU software.
Stop spreading BS.
 
Applejuiced said:
I did that plenty of times too unlocking iphone 2G's and I even turned off the iphone while it was running bootneuter and never bricked. All it needed was a DFU restore, maybe you should have researched a little further instead of relying on your "master Jailbreaker friend":rolleyes:
The BB chip is screwed? Ok.
You cannot permanently brick an iphone with just software, jailbreaking or unlocking. Get a clue before you talk and maybe teach your buddy about it also:D
Iphones cannot be bricked permanently THRU software.
Have a good night.
Click to expand...

Jailbreaks use various methods to introduce unauthorized code into an iPhone. One process is the Bootrom exploit. If the Bootrom is corrupted by the jailbreak, then you have successfully blocked the OS from booting AND iBoot from loading, which means no Recovery/DFU mode, effectively bricking the phone.
 
Prodo123 said:
Jailbreaks use various methods to introduce unauthorized code into an iPhone. One process is the Bootrom exploit. If the Bootrom is corrupted by the jailbreak, then you have successfully blocked the OS from booting AND iBoot from loading, which means no Recovery/DFU mode, effectively bricking the phone.
Click to expand...

Show me one person that got their Bootrom or any hardware corrupted by the JB in the past few years with the latest JB tools.
Its nice to warn others but if you dont like JB and not sure how the method works and what it does dont post nonsense that the JB with forever brick your device.
Dont you think the JB scene knows a little better and further in depth about what they're doing than what you're posting? If you dont want to JB its your choice but to spread false info and assumptions that jailbreaks will corrupt the bootloader and will forever brick your iphone is absurd.
And to even suggest that JB is what could keep killing his iphones?
If that was the case millions of JB iphones would be "bricked" now according to your logic.
 
Applejuiced said:
Show me one person that got their Bootrom or any hardware corrupted by the JB in the past few years with the latest JB tools.
Its nice to warn others but if you dont like JB and not sure how the method works and what it does dont post nonsense that the JB with forever brick your device.
Dont you think the JB scene knows a little better than what you're posting? If you dont want to JB its your choice but to spread false info and assumptions that jailbreaks will corrupt the bootloader and will forever brick your iphone is nonsense.
Click to expand...

I told you, I jailbroke an iPod Touch 3G 16GB iOS 4.2.1 with Greenpois0n. Luckily it didn't corrupt the main bootrom, it screwed with iBoot.
My friend's iPod Touch 3G 8GB iOS 4.2.1 was recently bricked through Greenpois0n (Bootrom corruption). Before that, his iBoot was corrupted via Limera1n, which was fixed.
My iPhone 4 GSM's iBoot was corrupted to some extent where it was a PITA to fix.
Friend's iPad was bricked due to Greenpois0n. Bootrom corruption.

Do you want any more?
 
Applejuiced said:
I did that plenty of times too unlocking iphone 2G's and I even turned off the iphone while it was running bootneuter and never bricked. All it needed was a DFU restore, maybe you should have researched a little further instead of relying on your "master Jailbreaker friend":rolleyes:
The BB chip is screwed? Ok.
You cannot permanently brick an iphone with just software, jailbreaking or unlocking. Get a clue before you talk and maybe teach your buddy about it also:D
Iphones cannot be bricked permanently THROUGH software.
Stop spreading BS.
Click to expand...

You want proof? PM me your address and I'll send you the comm/logic board connected to eachother.
 
Prodo123 said:
I told you, I jailbroke an iPod Touch 3G 16GB iOS 4.2.1 with Greenpois0n. Luckily it didn't corrupt the main bootrom, it screwed with iBoot.
My friend's iPod Touch 3G 8GB iOS 4.2.1 was recently bricked through Greenpois0n (Bootrom corruption). Before that, his iBoot was corrupted via Limera1n, which was fixed.
My iPhone 4 GSM's iBoot was corrupted to some extent where it was a PITA to fix.
Friend's iPad was bricked due to Greenpois0n. Bootrom corruption.

Do you want any more?
Click to expand...

You use the term bricked loosely though.
That's what I was explaining above.
Yes, things can always go wrong with jailbreaks but nothing that a restore or DFU restore cannot fix to put the phone back to factory firmware. And then try the JB again.
They were not forever bricked/fried or became permanently unusable.
 
Applejuiced said:
You use the term bricked loosely though.
That's what I was explaining above.
Yes, things can always go wrong with jailbreaks but nothing that a restore or DFU restore cannot fix to put the phone back to factory firmware. And then try the JB again.
They were not forever bricked/fried or became permanently unusable.
Click to expand...

If you read, 2 were. Bootrom corruption prevented iBoot or any other layer that comes after it from loading. Which prevented any kind of connection to a computer, or to enter into DFU mode. Therefore, it is effectively bricked through software.

My definition of bricked is a device that cannot be used because nothing runs on it.

Bootrom is not iBoot. Do not confuse the two. Bootrom is the iOS equivalent of the BIOS; iBoot is the bootloader.
 
AlphaDogg said:
You want proof? PM me your address and I'll send you the comm/logic board connected to eachother.
Click to expand...

Ok spell nazi.:D
BTW I spelled it wrong again not just to tick you off but also to remind you from the boards rules below:

"Corrections. There is no need to point out another poster's spelling or grammatical errors unless you think it is causing confusion. Remember that not all members are native English speakers. Communication, not correctness, is our goal. Examples: Don't correct members who spell Mac in all caps or who call the iPod touch an iTouch. etc"

So Im pretty sure you got the point of my post but wanted to act childish like that on your "high horse" cause of a misspelled word.
Anyway, your logic board could have went bad for many other reasons besides the bootneuter and it prob was an isolated issue and not the standard when it comes to unlocking the original iphone. I did it plenty of times also like you without following directions and beeing impatient thinking it would/should have been done doing its thing and none once have I friend a logic board.

Prodo123 said:
If you read, 2 were. Bootrom corruption prevented iBoot or any other layer that comes after it from loading. Which prevented any kind of connection to a computer, or to enter into DFU mode. Therefore, it is effectively bricked through software.

My definition of bricked is a device that cannot be used because nothing runs on it.
Click to expand...


So all these devices you're claiming were forever bricked using limerain and greenpoison?
Yeah ok, I dont buy that one bit but whatever you say:)
 
Last edited:
Applejuiced said:
Your logic board could have went bad for many other reasons besides the bootneuter and it prob was an isolated issue and not the standard when it comes to unlocking the original iphone using it.
Click to expand...

It was the communications board, not the logic board. It doesn't matter whether or not it is the standard in unlocking an original iPhone, it just proves that you can brick an iPhone using jailbreak software that is still being used today (albeit uncommonly). So please stop telling people the wrong thing. You CAN brick an iPhone with a jailbreak.

Applejuiced said:
prob was an isolated issue
Click to expand...
I googled my issue and the error code that I got while restoring, and it was linked to using bootneuter and stopping it while it was flashing. Plenty of people have had the issue I had, which is why I found threads on forums about it.

By the way, I was on 3.1.3 and 04.05.04_G (and still am, on the 16GB logic board/comm board).
 
I know more about basebands than all you guys here present, that is not a joke.

Yes, you can permanently brick an iPhone through software. Very possible. However, the chances of doing so are *very* slim and you would have to do something really stupid to accomplish this objective.

Edit - Also,

Bricked != Fried
Please don't confuse both terms. Bricked mean the software did something to make the hardware inoperable, like delete the seczone, bbupdaterextreme, seczone truth table, bootrom or rom.

Fried means overcurrent or overvoltage caused the problem. OPs case sounds like the iPhone dock was giving the device too much power. OP, don't use those speakers again and check your wiring! That is usually a sign of really bad wiring in your house (unbalanced system) that your electronics are frying.

A jailbreak will never fry your iPhone. A jailbreak will brick your iPhone. Both equally bad, but the later, like I said before, you would have to do something incredibly stupid to achieve.
 
Last edited:
jav6454 said:
you would have to do something really stupid to accomplish this objective.
Click to expand...

That is exactly what I did. Bootneuter told me "DO NOT CLOSE THIS APPLICATION WHILE BOOTNEUTER IS RUNNING" or something like that and it made me turn off auto-lock. But as it was flashing the baseband, I hit the home button, causing the baseband to corrupt royally.
 
jav6454 said:
I know more about basebands than all you guys here present, that is not a joke.

Yes, you can permanently brick an iPhone through software. Very possible. However, the chances of doing so are *very* slim and you would have to do something really stupid to accomplish this objective.
Click to expand...

I agree, but lets take the 2G iphone out of the equation and lets say bricking a newer iphone with running JB tools like limerain,redsnow, pwnagetool and greenpoison mentioned above.
How likelly is that causing hardware damage to the phone beyond of what a restore would fix?
Flashing/upgrading the baseband I can see on rare occasions even instances where installing the ipad bb on 3G and 3GS.
 
jav6454 said:
A jailbreak will never fry your iPhone. A jailbreak will brick your iPhone. Both equally bad, but the later, like I said before, you would have to do something incredibly stupid to achieve.
Click to expand...
Like sticking a fork in an outlet? lol.

BTW, this is what I did with Greenpois0n to get my bootrom to get corrupted:
DFU mode
Launch Greenpois0n.exe
Do jailbreak
Says "Failed"
Try to boot up; it doesn't
One lucky go makes it go into DFU mode
iREB does its magic
Greenpois0n still fails
This time TinyUmbrella can't kick it out of DFU, and won't even display an apple anymore.

Nothing stupid. Just extreme bad luck.
 
Applejuiced said:
I agree, but lets take the 2G iphone out of the equation and lets say bricking a newer iphone with running JB tools like limerain,redsnow, pwnagetool and greenpoison mentioned above.
How likelly is that doing hardware damage to the phone beyond of what a restore would fix?
Flashing/upgrading the baseband I can see on rare occasions even instances where installing the ipad bb.
Click to expand...

Taking the iPhone out of the equation and only assuming we have the iPhone 3G, and 3GS, then there is still a chance to brick when trying to unlock, not jailbreak. Currently, the only way to unlock these devices is through the AT+XAP hole found in the iPad baseband 06.15.00. So obviously, if you update to that baseband and mess up the update we will have a problem where the hardware most definitely can be bricked.

However, using jailbreaking tools will not brick your iPhone. At worst (in case jailbreak goes wrong), everything is fixeable through a simple iTunes restore.

Remember,

Jailbreak != Unlock


Prodo123 said:
Like sticking a fork in an outlet? lol.

BTW, this is what I did with Greenpois0n to get my bootrom to get corrupted:
DFU mode
Launch Greenpois0n.exe
Do jailbreak
Says "Failed"
Try to boot up; it doesn't
One lucky go makes it go into DFU mode
iREB does its magic
Greenpois0n still fails
This time TinyUmbrella can't kick it out of DFU, and won't even display an apple anymore.

Nothing stupid. Just extreme bad luck.
Click to expand...

I never use tools not produced or coded by the iPhone Dev Team. Your case was simply doing something stupid. Also, I never recommend anyone using tools outside PwnageTool or RedSn0w.

Here, you went with the cheap answer and you got bitten.
 
jav6454 said:
Taking the iPhone out of the equation and only assuming we have the iPhone 3G, and 3GS, then there is still a chance to brick when trying to unlock, not jailbreak. Currently, the only way to unlock these devices is through the AT+XAP hole found in the iPad baseband 06.15.00. So obviously, if you update to that baseband and mess up the update we will have a problem where the hardware most definitely can be bricked.

However, using jailbreaking tools will not brick your iPhone. At worst (in case jailbreak goes wrong), everything is fixeable through a simple iTunes restore.

Remember,

Jailbreak != Unlock




I never use tools not produced or coded by the iPhone Dev Team. Your case was simply doing something stupid. Also, I never recommend anyone using tools outside PwnageTool or RedSn0w.

Here, you went with the cheap answer and you got bitten.
Click to expand...

I tried it after Limera1n corrupted iBoot. Turns out Chronic isn't that good either.
 
Prodo123 said:
I tried it after Limera1n corrupted iBoot. Turns out Chronic isn't that good either.
Click to expand...

I'll say it once again:

egohotz, chronic dev team are ok guys and know their ways around hacking, but they are bad coders and have bad habits of not releasing patching promptly or not testing tools properly. Also they all have that media craving.... bad. Sorta like Zibri from back in the 1.1.x days, money grabbign attention w*ores

The Dev Team does always take its time to do stuff, hence you rarely see a problem with their stuff. That is the main reason I recommend them.
 
djc6 said:
this is the most thorough threadjack i've ever seen :)
Click to expand...

Trust me, this is nothing... I've seen worse, way worse.
 

Attachments

  • 1289010475614.jpg
    1289010475614.jpg
    30.5 KB · Views: 350
iPhone 4 Corrupt Bootrom struggle

I posted this today in another forum, just came across this informative thread in my research so kindly read my case below & suggest accrodingly..

My 2 months old Factory Unlocked (UK) iPhone 4 was running perfectly stable JB on 4.2.1 using GreenPoison

Only 2 days back, I just Sync'd it with itunes after which without any reason the iPhone will go into "DeepSleep" randomly.. The phone won’t respond or wake when pressing the home or sleep buttons. It won’t ring if someone’s calling though the caller can hear the ring. I have to HARD reset using home+sleep to get it back…

I tried to Reload 4.2.1 but it didn’t help, it would still go into DeepSleep. I tried reloading 4.2.1 3-4 times but everytime in the end it would go into the recovery loop. Tried Tiny umbrella to get out of the recovery but it won’t help. Even if TU kicked it out of recovery, it would load the apple icon but again go into deepsleep and I have to HARD reset using home+sleep
In betw. this struggle, I saw greenpoison screen giving a message “some file not found” to which I predicted that the BOOTROM is corrupt and is still having remains of the GreenPoison code which may be preventing a proper Restore.

I gave it a clean shot once again, where after reloading 4.2.1, in the Recovery Loop where I got “connect to itunes” on my screen, I booted to DFU Mode and ran GreenPoison and voila!! It booted straight into the Activation screen, upon Activating the springboard loaded..
BUT… even after this clean re-install of 4.2.1 I’d still be getting DeepSleep issue.

Finally Frustrated, I loaded the Stock 4.3.1 to my Phone last night, which Completed properly without any errors or rec. loop probs… The phone is running properly NON-JB for the past 10-12 hrs. Though when I loaded 4.3.1 and Shut down the phone it did not come up immediately, rather I had to press home+sleep several times to get it up finally. Haven't Re-Booted to check this again though

Anyhow, atleast the phone is running OK for now.. haven’t Jailbroken yet just to see if my phone is running into a hardware problem or a software(JB glitch) problem.

On the side note, before updating to stock 4.3.1, I tried pwnage tool to create a custom ipsw, I un-checked “Activate….” Before building the IPSW presuming I don’t need hacktivation but when I tired to restore this custom IPSW, it threw error 1600. Then I went on to patch my phone with stock 4.3.1 which I’m running now..

In all this turmoil above, I’m trying to close down on the cause of this struggle. I presume the BootRom exploit used by greenpoison has its after effects.
I want other geeks to shed some knowledge over this, and possible remedies that exist for such a situation. The reading in this thread re-affirms my belief that GreenPoison is not Glitch-Free and will have its side effects.. May be the experienced members are right on saying Dev-team's solutions are much thoroughly tested for stability

My question again, is there a Solution TO FLUSH bootroms for iPhone 4 & other new gen iOS devices to completely clean out remains of bootrom exploits??

2nd please also tell should I try Redsnow or pwnage tool to JB my phone now ???? living without it is impossible….

Thanks for reading the long story… I hope it will help other readers across in future..
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back