11-08-2009 09:26 AM
Tour 9630 - Sprint version
3 times now I have attempted to update to 4.7.1 and 3 times the device got hosed. Luckily, I have the restore procedure down pat now. Each time it hangs at the JVM part and it says the device is no longer connected. Then you get the white screen of death with the 507 - No OS error. To restore, I delete vendor.xml and run loader.exe with the /nojvm switch, then restore my last backup.
Can anybody tell me what the deal is? I have the latest version of Desktop Manager. This seems like a rather nasty bug/defect.
In case anybody needs to know to help me, I run Win XP SP3 and BB Desktop Manager 18.104.22.168. Phone version is 22.214.171.124 (platform 126.96.36.199). Branding version 188.8.131.52. BB system software 4.7.0.
I just won't update my OS, I guess. Phone has been wiped clean and a fresh install done, then the upgrade was attempted, so no software is interfering. This is obviously a BB issue on the software or hardware side. I have seen other posts about this issue, but no answers yet.
Again, just very disappointing that I can't trust my phone to update without losing everything. I backup and restore after re-installing the OS, but then I need to download everything again and its a major PITA. Would love some answers.
11-08-2009 01:19 PM
It may be that you need to utilize the JL_Cmdr method of truly wiping out your BB device OS and then installing it fresh. It's a tricky procedure, but it does work (though I've only had to do it once).
Be sure that you've DL and installed your carriers device OS package. And, it might even not be a bad idea to make sure that DTM is totally clean...here's a procedure for that:
I suggest the following steps (insert plenty of reboots of your PC...not just restarts, but full power down reboots). Also, it is advised that you be logged into the PC on an account with full admin rights. Further, under Vista, use the "Run As Administrator" option for everything.
1) Remove your device OS update package from your PC (add/remove programs)
2) Cleanly uninstall the RIM DTM software:
3) Get a fresh download of the RIM DTM software:
4) Download (to your PC) a fresh copy of your device OS package from your carrier:
5) Install DTM to your PC
6) Install (also to your PC), the device OS package
Hopefully that will get things going again.
Good luck and let us know!
Good luck and let us know!
11-08-2009 01:22 PM - edited 11-08-2009 01:29 PM
Sorry, but I already use JL_Cmder. My bad on assuming that was a given. Its the only way I know to wipe it clean.
I will try to remove DTM and start again. But, if I reinstall DTM fresh, I will probably try to upgrade first just to see if it works. If that fails I will put the latest OS on manually like before.
11-08-2009 01:26 PM
OK -- there are several methods of Wiping...JL_Cmdr being the most drastic.
I'd suggest then trying the clean DTM procedure. I know that I had a couple of challenges on mine when I went up to 5.0. I had left the prior device OS package installed atop DTM. Not sure if that was truly causal since I also migrated up to Win7 at the time. But the total clean uninstall followed by total clean install seemed to allow my situation to work. Also be certain that you have the exact device OS package for your specific BB from your specific carrier.
11-09-2009 09:43 AM
I need a few solid hours, so I probably won't get to this until Wednesday, but I would bet this is caused by the upgrade to DTM v5. Just a hunch. It upgraded fine before the upgrade, so why not afterward? I will let you know.
Thanks a million.