What have I done? Can you help me??

[Gink]

Here's the story:

On Friday I was trying to cache some slacker stations and I was having some trouble. I was trying to use DM to add/remove applications and I got distracted. I lost track of what I was doing (since I was also working) and I cancelled the update in the middle of the process and bricked the phone. All I was getting was the LED blinking 3 times - nothing on the screen at all.

When I got home I loaded a leaked 5.0 hybrid OS and quickly realized it was not compatible with a lot of my stuff so I loaded 4.5.0.175 (Sprint's approved OS). I used it for a couple of days and then had all sorts of weird profile issues and some of my apps weren't working. I was also getting the infamous chirp which made me crazy. The biggest problem was that my BBText2IM program would cause my BB to reboot when I even tried to open the program so I figured those were all bugs with .175.

Last night I downgraded back to my .138 hybrid figuring I would be back to where I was when this whole mess started but now I'm still having trouble with BBText2IM. It's just rebooting the BB randomly. I'm testing my other apps right now to see if any of them are having troubles too. Could the BBText2IM files that I downloaded to the PC be corrupt and that's what's causing my issues?

So what have I done to the BB? Could I have damaged the hardware with what happened Friday? Do I need to wipe and start clean again? What OS should I try? I'm getting very frustrated as I've got many many hours logged on this issue so far.

Thanks for any help/advice you can provide.

[rachel0179]

Could be your media card.. take it out and see if it happens.

[plunkingtom]

Did you wipe with bbsak or jl commander? I would wipe it and load the os you want?

[Gink]

Originally Posted by plunkingtom

Did you wipe with bbsak or jl commander? I would wipe it and load the os you want?

I did wipe it w/ JL cmdr before loading .175 but not before downgrading back to .138. I lose so much when I wipe the device - even when I back-up everything. Don't know how some of you are able to upgrade/downgrade so often without going crazy from resetting everything!

I've been trying to research the best/most stable OS for the 8330 but I'm not having any luck. Recommendations?

Still not sure if I have a HW issue or if it's just SW.

[plunkingtom]

I would load the latest official verizon software to see if it is software. And yes do a wipe before reloading. You might ask or look aaround for xliderider to see what os he would use. He is on Verizon and knows more than me about os problems...

[Gink]

Originally Posted by plunkingtom

I would load the latest official verizon software to see if it is software. And yes do a wipe before reloading. You might ask or look aaround for xliderider to see what os he would use. He is on Verizon and knows more than me about os problems...

Xlider has saved me a few times I'll check with him.

[xliderider]

Thanks for the vote of confidence, but this problem sounds a little complex.

For the OS problems, the ringer/profile problems are a known issue with .175, as is the possibility of chirping on Verizon.

The last OS without any chirping was 4.5.0.131, but the radio isn't the fastest on data transfers, so you will be giving up a lot of browser speed. For me, the occasional chirping is worth tolerating for the fast browser on the .17X OS builds.

If you can't stand the chirping, you can swap the .17X .sfi radio file in the CDMA folder of your OS with the same file from the .131 OS. That should nuke the chirping issue. You can also try swapping in the 3 or 4 profile.cod files from .131 while you are at it to fix the ringers/profiles instability as well, they go in the Java folder. Load them using loader.exe in the Apploader folder where you remove the vendor.xml file from. When Apploader asks if you want to backup and restore everything during the loading operation, select NOT to backup.

For your other problem with the I'm App, try these 2 things. Install fresh from the OTA link, or from Desktop Manager if it is a .zip file. Then when you restore your apps, do an Advanced Restore. Click on File in the upper left of the window and navigate to your backup file and open it. The databases that can be restored will populate the left window pane. Select only the essential databases you need like Address Book, SMS, Messages, BBM, etc. You can select multiple databases by holding the Ctl key down when you click on them. The less you restore, the less chance of transferring over something that is causing you problems with your setup. Then click on the button in the middle with the >> on it to restore the databases.

Good luck.

Posted from my CrackBerry at wapforums.crackberry.com

[xliderider]

If all that swapping radio files and profile.cod file stuff made your head spin, then load this hybrid.

Hybrid OS 8330 v4.5.0.160/.131

It already has the .131 radio and profile.cod files in it.

Posted from my CrackBerry at wapforums.crackberry.com

[Gink]

Thank you Xlider - I'm working on installing that hybrid now. A couple questions for you:

My DM is v5.0 - BnG's instructions say not to use higher than v4.6... is this going to be a problem?

Once I swap over all the files can I use Shrink-A-OS to shrink and install? I've been using that all weekend - could that be causing my problems?

[xliderider]

Originally Posted by Gink

Thank you Xlider - I'm working on installing that hybrid now. A couple questions for you:

My DM is v5.0 - BnG's instructions say not to use higher than v4.6... is this going to be a problem?

Once I swap over all the files can I use Shrink-A-OS to shrink and install? I've been using that all weekend - could that be causing my problems?

No, DM 5.0 isn't a problem, he just made that recommendation because a lot of noobs were having problems with the hidden vendor.xml file that DM5.0 sometimes installs on your computer. If you aren't having problems with loader.exe detecting your OS to load, don't worry about using DM5.0

The only problem I encountered using Shrink a OS on OS 4.5.0.175 was when I removed the set-up wizard .cod files. I got some errors about missing files when the BB booted-up. I reinstalled the 2 setupwizard.cod files and the errors went away.

[Gink]

OK, I'm using CrackMem right now. Should I have just used AppLoader?

[xliderider]

Originally Posted by Gink

OK, I'm using CrackMem right now. Should I have just used AppLoader?

Either will work, even BBSAK uses loader.exe

[Gink]

I think I messed up. When it's running thru the wizard and I get to the point where I would check the apps I want to reload, that's where I should have just hit continue - right? I should not be adding them there, I should be waiting until everything is done and then restore them from backup, right? Am I understanding that correctly?

If that's the case then I just messed up. Should/Can I re-do it CrackMem and wipe the device again?

[xliderider]

Originally Posted by Gink

I think I messed up. When it's running thru the wizard and I get to the point where I would check the apps I want to reload, that's where I should have just hit continue - right? I should not be adding them there, I should be waiting until everything is done and then restore them from backup, right? Am I understanding that correctly?

If that's the case then I just messed up. Should/Can I re-do it CrackMem and wipe the device again?

It's up to you, if you want to load your apps from the Apploader, or later. Considering you were having problems with an IM app, it might be wise to leave that one off for now.

Though if you loaded it, you might as well see if the IM app behaves while using the .160/.131 hybrid.

[Gink]

Thanks Xlider. Looks like everything loaded ok for now. I'll play around with it for a little while and hope everything works brilliantly!!! Thanks for your help.

I am going to try a fresh install of that app however....