-
Ok, that wasn't a good idea. I am waiting now for initialization. It won't work. The rebooting reaches every time the same level and starts again.
Lol, no where in the guide to delete the java content. But to copy and replace.
You don't have enough there to load an OS onto a phone
Sent from my BlackBerry 9900 powered by
BerryLicio.us09-08-12 08:00 AM - Please download a fresh OS (.523 or higher) and copy and paste over the java files and hit the loader exe. or load via DM.You don't need to apologies. It's my fault. I want to thank you for everything what you have done and keep doing.
Now let's see how to fix all this.
Don't forget to delete vendor files.
Any further questions, please ask, we are all here to help !
Good Luck !09-08-12 08:27 AM - Actually, Ian, it is more than "certain folk on AT&T" - NO ONE on AT&T with a 9810 or 9900 can run an OS higher than .391 - any OS of .4XX or higher ilk will have the "mic problem" in a good portion of the US. If one lives in a "bad" area or, like myself and many, travel on business to "bad" areas, we are stuck with .391 or lower.
This is the current list of "good" and "bad" areas - and as you can see, the 'bad" area list encompasses a large portion of the US including many major metro areas:
There were no mic problems reported from anyone in:
So. California, Chicago (IL), Miami (FL), Raleigh (NC), Atlanta (GA), Louisville and Bowling Green (KY)and Dallas and Houston (TX) - the New England area seems to have no problems; large parts of NM seem to have no problems;
Mic problems were reported in the following areas:
Baltimore (MD), Boise (ID), Cleveland (OH), Cincinnati (OH), Denver (CO), Detroit (MI), Eugene (OR), New Jersey, NY, Central PA, Philladelphia (PA), suburbs of Philadelphia, Phoenix (AZ), Portland (OR), Seattle (WA), St. Louis (MO), Wilmington (DE), Washington DC, Wisconsin, Minneapolis (MN), Wichita (KS), Glenwood Springs and Aspen (CO)
So - we beg, beseech - (and whatever else is needed
) to Lord Zocster the Omniscient and Guru of all things BB OS to help us poor souls on AT&T (and there are MANY OF US!) enjoy the kind of performance that BerryLicio.us brings to everyone else . . . . .
(OK - maybe the Lord Zocster thing is a bit tacky . . . trying to get my point across LOL!)09-08-12 09:27 AM - If it is the Java that is causing the issue then I would guess that there may be something that Zocs can do to help.Actually, Ian, it is more than "certain folk on AT&T" - NO ONE on AT&T with a 9810 or 9900 can run an OS higher than .391 - any OS of .4XX or higher ilk will have the "mic problem" in a good portion of the US. If one lives in a "bad" area or, like myself and many, travel on business to "bad" areas, we are stuck with .391 or lower.
This is the current list of "good" and "bad" areas - and as you can see, the 'bad" area list encompasses a large portion of the US including many major metro areas:
There were no mic problems reported from anyone in:
So. California, Chicago (IL), Miami (FL), Raleigh (NC), Atlanta (GA), Louisville and Bowling Green (KY)and Dallas and Houston (TX) - the New England area seems to have no problems; large parts of NM seem to have no problems;
Mic problems were reported in the following areas:
Baltimore (MD), Boise (ID), Cleveland (OH), Cincinnati (OH), Denver (CO), Detroit (MI), Eugene (OR), New Jersey, NY, Central PA, Philladelphia (PA), suburbs of Philadelphia, Phoenix (AZ), Portland (OR), Seattle (WA), St. Louis (MO), Wilmington (DE), Washington DC, Wisconsin, Minneapolis (MN), Wichita (KS), Glenwood Springs and Aspen (CO)
So - we beg, beseech - (and whatever else is needed) to Lord Zocster the Omniscient and Guru of all things BB OS to help us poor souls on AT&T (and there are MANY OF US!) enjoy the kind of performance that BerryLicio.us brings to everyone else . . . . .
(OK - maybe the Lord Zocster thing is a bit tacky . . . trying to get my point across LOL!)
However, if it is (as I suspect) the .sfi then even the OS maestro known as Zocs probably has his hands tied as you can't easily mess with the .sfi file.09-08-12 09:34 AM
. It is updating now. Let's see what will happen in a few minutes.
