One issue we ran into today is if you try to do this across versions. We downgraded a 9530 to 4.7 and we were unable to use JavaLoader to write the COD files to re-upgrade it successfully. But this was using the Windows JavaLoader not bjavaloader.
On Sep 9, 2010, at 4:29 PM, Chris Frey wrote: > On Wed, Sep 08, 2010 at 12:21:47PM -0400, Jon Hylands wrote: >> >> Hi everyone, >> >> I'm trying to refresh a 9530 by reloading all the "default" modules >> onto a wiped phone. Its easy to do using the loader.exe application >> that comes with BB Desktop, but we want to do it from a command line, >> in a batch process, with no user interaction required. >> >> Does anyone know if this is possible using barry? If not, why not? > > Hi Jon, > > I'd never done a full OS wipe and load directly from Linux, so I figured > I'd give it a shot with a device I've reset before, under Windows, > to see how it went. I used a Blackberry 8700 with 4.5.0.180 OS. > > I'm pleasantly surprised! Talk about success. > > I first determined what was on the device to start with: > > bjavaloader dir > dir.txt > > I thought I might need the submodules as well (the -s switch) but I didn't. > > I edited dir.txt until I just had a bare list of module names. I ended up > with 561 module names in a file named mod.txt. This might be a handy > feature to add to bjavaloader... just displaying the module names. > > Then I pulled all the COD modules out of the device and saved them to disk: > > mkdir beforewipe > cd beforewipe > bjavaloader save $(cat ../mod.txt) > > This successfully saved all 561 modules. > > Then came the wipe... I started with a factory reset: > > bjavaloader resettofactory > > This rebooted the device, the OS wiped my settings and data and came back > with the GUI. Then I wiped the device: > > bjavaloader wipe > > This took a couple reboots, the entire device was wiped, and I got the > usual "empty Blackberry" error code 507, with little icon in the middle. > > Then I loaded all the COD files back in, all at once: > > cd beforewipe > bjavaloader load *.cod > > All modules loaded successfully, the device rebooted, and took a looooong > time to come back, which matched my experience under Windows. > > I grabbed a fresh dir after this, and compared mod.txt module names. > They were the same. > > And just to be paranoid, I extracted all the COD files one more time, and > compared them. They were all alike. > > Looks like OS load *is* possible with Barry. :-) > > - Chris > > > ------------------------------------------------------------------------------ > Automate Storage Tiering Simply > Optimize IT performance and efficiency through flexible, powerful, > automated storage tiering capabilities. View this brief to learn how > you can reduce costs and improve performance. > http://p.sf.net/sfu/dell-sfdev2dev > _______________________________________________ > Barry-devel mailing list > Barry-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/barry-devel ------------------------------------------------------------------------------ Automate Storage Tiering Simply Optimize IT performance and efficiency through flexible, powerful, automated storage tiering capabilities. View this brief to learn how you can reduce costs and improve performance. http://p.sf.net/sfu/dell-sfdev2dev _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
