Issue with all 20XXX roms!: No programs then soft reset=hard reset - Page 3

JAChavez99 · #21 (**permalink**) 01-02-2009, 01:59 PM

Fixed using triggered bootloader mode, thanks to Glossman!

Glossman · #22 (**permalink**) 01-02-2009, 02:28 PM

Quote:

Originally Posted by JAChavez99

Fixed using triggered bootloader mode, thanks to Glossman!

I created a how-to post that explains the receovery process you just went through:

http://forum.ppcgeeks.com/showthread.php?t=51508

Thanks again!

JAChavez99 · #23 (**permalink**) 01-02-2009, 02:57 PM

So I guess for now the solution if you want to flash a new ROM is to go to shipped ROM, run the unlocker, then flash?

Ambrose · #24 (**permalink**) 01-02-2009, 03:03 PM

You only have to run the unlocker once. No need to repeat unless you have run the relocker. It doesn't sound like you have...

-Ambrose

JAChavez99 · #25 (**permalink**) 01-02-2009, 03:17 PM

Good deal. I wasn't sure if you used this RUU_VICTOR_C_SPRINT_WWE_PPST_1.09.651.5_Radio_1.00 .00F_NV_1.44_Ship.exe to return to stock it would relock the device or not.

Ambrose · #26 (**permalink**) 01-02-2009, 03:25 PM

Nope, you're still unlocked after running it.

-Ambrose

**Calkulin** · #27 (**permalink**) 01-05-2009, 02:08 PM

After much testing, I think I narrowed this problem down, at least in my ROMs, to Inbox Menu Extensibility. Everytime I use this OEM, my OS becomes unstable, corrupting menus, etc but if I don't use, no problems what so ever. So if you have this problem and are using this OEM/cab, then you know the cause

froghat · #28 (**permalink**) 01-06-2009, 10:58 AM

I just had this happen last night. Using MightyRom 3.9, ActiveSync started complaining about the certificate on my Exchange server (the cert has been fine for many months now). I powered the phone off and when I turned it on again, it had hard reset. I've reflashed with 3.9 but if it happens again I'll try the stock ROM reflash first.

az93civic · #29 (**permalink**) 01-06-2009, 07:52 PM

Quote:

Originally Posted by Calcu

Like I posted in my thread, flash a OEM ROM, then try again. That happened once to me and once I flashed the OEM and flashed back, I have not had that problem again and I have flashed over 20 times since with no problems, so I would suggest you start with that first

I had the same problem, this worked perfectly

**tobeychris** · #30 (**permalink**) 01-07-2009, 12:46 AM

Title should really be fixed to reflect the fact that this doesn't actually happen with all 20xxx ROMs, only certain people's specific flashes.