Help!!!!! Won't Boot! Bricked?

ken830 · #1 (**permalink**) 10-31-2008, 08:53 AM

I'm hoping someone can help me... A couple of days ago, I finally got around to unlocking the phone and flashing Juicy 2.6. It worked fine. Then, last night, I tried to cook my own ROM using the latest TF/GC kitchen, SYS, OEM... Everything worked perfectly...

Then tonight.... I did cooked up another ROM, with less applications... Followed all the instructions... Flashed okay... The phone reset... And now I'm stuck at the Touch Diamond logo screen (with the red text at the bottom)... Tried hard-reseting but it didn't fix it...

It's a Sprint Diamond...

I'm a noob on these phones, so I don't have a great idea of where it's at or my chances of recovery.... Is there a chance I can get into the bootloader and reflash it?

Please, someone help!!!

I followed tobeychris' instructions very carefully...

ilkevinli · #2 (**permalink**) 10-31-2008, 09:11 AM

Did you put it in boot mode and try flashing ?

jgillard · #3 (**permalink**) 10-31-2008, 09:13 AM

Put your phone into bootloader mode (same as hard reset but without the center button) and flash a working rom. You should be fine.

**tobeychris** · #4 (**permalink**) 10-31-2008, 09:17 AM

It seems you did not, or you wouldn't be stuck.

As everyone else has said, get into bootloader (Power + VolDwn + Reset) and run the RUU with any ROM you'd like to flash.

Your phone's fine.

**aceracer24** · #5 (**permalink**) 10-31-2008, 09:19 AM

To be more precise.

You do not need to be connected to Activesync (but need to be connected to the PC still with USB cable) in order to flash as long as you put your phone into the bootloader mode. If I remember right, to do that you will hold down the hangup key, volume down key and the powerbutton at the same time. This will bring up the rainbow screen. From here just start the rom flash utility like normal and the phone should be detected and begin to flash.

Quote:

Originally Posted by tobeychris

It seems you did not, or you wouldn't be stuck.

As everyone else has said, get into bootloader (Power + VolDwn + Reset) and run the RUU with any ROM you'd like to flash.

Your phone's fine.

Actually Tobey, I am not sure it was the instructions that caused this because it happened to me. It is one of the options that was/was not selected that is causing it. Oh and before you say"You need to have the Base Manila selected as well" I already knew that because it says as such right next to base manila

So thats not what caused the issue. It's something else but I never did figure it out.

ken830 · #6 (**permalink**) 10-31-2008, 09:20 AM

Thanks guys... I know I must've missed some instructions...

I couldn't find the key-press to get into the boot loader... I'm in now.. Thanks!

ken830 · #7 (**permalink**) 10-31-2008, 09:56 AM

So I was able to recover back to the stock Sprint ROM... So I tried building another ROM, and the same thing happened again... It's not a problem now that I know the key-sequence to get into the bootloader, but I guess when I find more time, I'll do some experimenting to see if I can figure out what I'm missing from the build... All the esential stuff seems to be in place...

**aceracer24** · #8 (**permalink**) 10-31-2008, 10:21 AM

Quote:

Originally Posted by ken830

So I was able to recover back to the stock Sprint ROM... So I tried building another ROM, and the same thing happened again... It's not a problem now that I know the key-sequence to get into the bootloader, but I guess when I find more time, I'll do some experimenting to see if I can figure out what I'm missing from the build... All the esential stuff seems to be in place...

Make sure you have one of the battery status percents checked. I think I had both unchecked once and that might have caused the problem once, I don't remember though.

**Mr. X** · #9 (**permalink**) 10-31-2008, 10:24 AM

make sure you g'reloc
when your changing in all these diff modules. thats the leading cause of no boot. besides bad drivers.

**aceracer24** · #10 (**permalink**) 10-31-2008, 10:34 AM

Quote:

Originally Posted by Juggalo_X

make sure you g'reloc
when your changing in all these diff modules. thats the leading cause of no boot. besides bad drivers.

I thought it does it automatically? I have not had to do anything special and Ihave gotten roms to work. Some didn't fully boot because of something I checked or didn't check but I have not had to do anything special.