What NOT to do - Avoiding 'download mode'?? - Page 2

**nuguy** · #11 (**permalink**) 04-10-2008, 10:59 AM

PPC_NOOB and Nickels - Are you two having a cat fight? - haha </jack>

I would think it would make sence that if some people have figured out what they did that causes bricking a thread with a DON'T DO THIS would make sence....

**puff** · #12 (**permalink**) 04-10-2008, 09:15 PM

Quote:

Originally Posted by Nickles

N00B- you also forgot this ->

Quote:

Originally Posted by ImCoKeMaN

What i'm sayin is it's not possible, don't do it. <- PERIOD

errrr, nice cat..........

here's a few more:

Quote:

Originally Posted by ImCoKeMaN

WARNING: RADIOS SHOULD NOT BE USED FROM DIFFERENT DEVICES.

Download Mode suspected cause:

Quote:

Originally Posted by ImCoKeMaN

The problem is there is a section in the radio portion that loads the bootloader. If you mess that up bad enough you will have issues. Ever since the apache days i've tried to warn people not to flash radio roms more than necessary. Maybe now a few more will understand the risks. Don't get me wrong, signed images from a company "should" be fine, but they are much more risky than just grabbing the OS portion and using that. If the OS portion fails you have next to a 100% chance of a full recovery. With radios and SPLs that is not always the case.

and lets not forget this one:

Quote:

Originally Posted by ImCoKeMaN

Of course, if you're crazy like me feel free to make bricks. I could use a new patio.

-> http://forum.ppcgeeks.com/showthread.php?t=23102

**puff** · #13 (**permalink**) 04-10-2008, 09:51 PM

Quote:

Originally Posted by nuguy

PPC_NOOB and Nickels - Are you two having a cat fight? - haha </jack>

hey - who let the cat out of the bag

Quote:

Originally Posted by nuguy

I would think it would make sence that if some people have figured out what they did that causes bricking a thread with a DON'T DO THIS would make sence....

someone else had that very idea, hence this thread was made

Eturnulrs704 · #14 (**permalink**) 04-10-2008, 10:11 PM

Me i figure it like this, Its man made so it can be fix (un-bricked) in some way.. But to avoid that, search search and search some more.. cause ive tested every rom in these forums, with the apache amd the titan.. And i flash back n fourth numerous times "everyday" on both... Havent touched " pun intended my touch yet (vouge)... I guess maybe im lucky..lol or the research before flashing pays off.. Either way.. Search is your friend, Or just stay stock and add what you wanna add...

kraygh · #15 (**permalink**) 04-11-2008, 07:57 AM

I don't think bricking is as widespread as everyone is making it sound, either.

I've been stuck on a few occasions when I made really stupid mistakes while rushing. Once the phone wouldn't turn on or even charge (just a red light) but I searched and found out how to get it into serial link mode and recovered it with a stock rom (the only one that would take).

"True" bricking, where the phone doesn't respond to ANYTHING like it's just a fake display model. Now THAT is where you are screwed.

blueglide · #16 (**permalink**) 04-11-2008, 12:01 PM

Thanks PPC NOOB your posts were helpful. I wasn't suspicious either about the roms themselves. I t seemed the problems were arising from incorrect bootloader and/or radio flashes, flashing back and forth.....ImCokeMan's post explains some of that. Simple, cautionary warnings to users about being careful (and whats compatible) when flashing their radio roms for example was what this thread was about. I also agree with Kraygh that 'bricking' may not be as widespread as thought but if a few simple 'don't do' rules keeps someone from ruining their device then thats helpful. Thanks again...I hadn't seen that one post you quoted from ImCokeMan.

**ImCoKeMaN** · #17 (**permalink**) 04-11-2008, 11:28 PM

Well, I thought i'd have a lot to say in this thread, but it looks like i already said most of it via quotes. Basically, once you go GPS don't go back and you'll be fine.

**puff** · #18 (**permalink**) 04-11-2008, 11:44 PM

Quote:

Originally Posted by ImCoKeMaN

Well, I thought i'd have a lot to say in this thread, but it looks like i already said most of it via quotes.

just be thankful that i didn't quote ALL of your posts

really though, in regards to the subject @ hand.

Quote:

Originally Posted by ImCoKeMaN

I'm not really meaning to be cryptic, but i don't really know a good way to explain it. The radio is actually made of different parts and the part that i can actually access on my phone at this moment is still the same as the one from the 3.16 update i did. I have since put on the 3.35 and went to revert to the 2.17 (bricked in this process, but there were other variables). There are all sorts of different combinations of those parts that could have occurred, but i can't really backtrack at this point and as it's bricked i can't even access all of it to verify. This is what i mean by radio not being over written and my one statement of "it can't be done." =) I'm actually looking at the ram and doing a hex dump looking for version strings and comparing to rom radio updates for this info.

and good ole' shadowmite...

Quote:

Originally Posted by shadowmite

To confirm what cokey has said, to date we have been unable to overwrite a gps enabled 3.x radio with any non gps enabled radio. These radio's have a different nbh header ID given to the bootloader for writing. Non gps radio's are a 0x300, gps radio's are 0x785. If you flash a 2.17 rom onto a 3.x radio device, it might work and appear to be back to normal, but I highly doubt you have flashed back the radio as we have specifically tried to accomplish this for days without success.

Be warned, this is dangerous territory as cokey himself has bricked a device in this process.

Quote:

Originally Posted by ImCoKeMaN

Basically, once you go GPS don't go back and you'll be fine.