[maish]

here's the sad story
1) tried using jlcommander - BIG MISTAKE
2) reloaded OS thru application loader ( and restored data ) - all fine and good
3) blackberry works fine until I try rebooting ( with battery pull) - at which point the blackberry begins the boot process but get stuck at the AT&T orange welcome screen

I am not getting the standard 507 ( no OS ) message . WHich leads me to believe that there is something else blocking boot up - multiple OS 's or fragments?

anyone with some input please offer

Thanx

[Dubdub]

Try reloading the OS again.

What did you do just before you rebooted? And why did you reboot?

[maish]

thanx for trying to help

I have a problem that others have had - even after reloading OS ( thru loader.exe) the boot stops 60% through .

It seems I have a corrupted OS which needs wiping
if I could get jl commander working I could wipe and try reloading a whole new OS

HOWEVER - I cant connect with jl commander
can someone give step by step how to connect

1) should battery be in or out when using JL commander
2) at what point should "javaloader -u wipe " command be entered

keep in mind I dont have the blank white 507 screen. the b- berry is going thru an endless loop trying to boot up which doesnt allow jl commander to connect to the device- how to I break this cycle, connect with jl commander and move to wiping my device?

[Dubdub]

Did you do this?

What to do next if Jl Cmder will not connect and wipe - BlackBerryFAQ

[option94]

Wirelessly posted (T-Mobile 9700)

It can't go through a reboot loop if you do it without the battery in the phone.

[cleverstar]

Similar experience.
Guess OS messed up.
Received my new 9700, then try to upgrade to the latest EastAsian OS, the phone just got stuck when do step 2 "Waiting for device initalization" with error in "Reconnecting to JVM", no 507 error, just failed raw!
Then no matter what version (ATT or non-ATT) of OS and DM I tried, it refused to install, always fail at the same point.
The next day, I tried another PC w/ fresh ATT english OS/DM installed, it seemed to install. Then I take risk to play with the EastAsian latest OS again, thinking it's my old PC's issue, but again, it started to fail at the same point.
Then I revert back to ATT english OS/DM, and managed to reinstall the ATT OS, but then I realized a pull of battery made the phone not rebootable again, no 507 error, just a while screen with a void battery sign and fake progress bar.
Then more play, nothing works again even on the new PC, then not even after I reinstall windows and software and using a new USB port and cable!
Sh!t, the more I try, the more it's messed up.
Finally I returned the unit.

Some guess:
1. the phone's power IC is bad? the booting sequence cannot detect some power unit status when powered up?
2. since I messed up the OS the first time, some mixed OS version fragments sitting in my device and refused to load cleanly w/ the new OS?
3. ATT doesn't support non-ATT OS, and once you risk to test one, it burns your phone?