BBBOLD 9000 CONNECT TO BOOT ROM PROBLEM

Hi Everyone,
I tried to upgrade my BB Bold 9000 to 5.0, BUT WHEN CONNECTING TO BOOT ROM, THE BB FAILS AND REBOOTS, PLUS I CANT UPGRADE WITHOUT THE BATTERY IN THE BB. :-[ IM STUCK, PLEASE HELP ME!
I have attached the error message
error message gave me some option i tried that tooo but still the same problem.
Someone please help
Thank You
Apperciate.

Are you able to upgrade via wi-fi? Have you done a patch upgrade before using the same Desktop Software/USB cable/PC? I have never seem this error so I'm trying to pinpoint were exactly the problem could be. I'm suspecting you might have had problems on your previous upgrade or you installed a corrupt application? I'll keep in touch.
Thank you for the question (I hope you have backed up all of your important information)
Twitter: @IAmBenGiey | Click " Like " if you want to Thank someone.
If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.
Try my apps:
The Ultimate Currency Converter and T2G - BloGFeed

Similar Messages

Curve 9300 connecting to boot rom problem

Hi everyone, I have a curve 9300 and I tried to install an update to the OS. The problem is when i get to the part that says "connecting to the boot rom" the phone starts rebooting and goes like this 3 or 4 times, resulting on a failed update. I already have tried to use another USB port, another computer, connect the blackberry to the pc with the battery pulled, tried another usb cord, all of which failed. Can anyone help me solving this?

Hello Edi27 and welcome to the BlackBerry Support Community Forums.
Sorry to hear you are experiencing an issue installing your device software.
Did this error come up after the update installed or during the update?
Does the device display any error on the screen or just the BlackBerry start up logo?
Have you tried to reboot your device in Safe Mode as shown in KB17877?
Thanks!
-HMthePirate
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

Reload Software 507 - stuck at connecting to boot rom

1. My Curve 8900 (Orange Unlocked) had an app error 523 and didnt load, so I wiped it with BBSAK.
2. After that, my phone starts and shows a white screen with an image and below the error message "Reload Software:507" and stays like that.
3. I have followed every blog and have followed every step, but the OS is not loading on the device and it gets stuck at connecting to boot rom.
4. When I open the Loader, my PIN number shows without any problem, so I click "next". When I've selected the apps I want to be installed and click "finish", my phone will reboot twice when the PC shows "Connecting to boot ROM" geting a "fatal error message has ocurred [A0x00000001]" on the loader.
I've been stuck at this process for too long and decided to post here for help.
Is there any solution for my device.
Thanks!

Hi vatsal
Welcome to BlackBerry Support Community Forums
You can try JI Cmder to wipe again and then try to load the OS ,But remember you had to click the Next button on the screen as soon it shows USB PIN : UNKNOWN or else you had to try again :
What to do next if Jl Cmder will not connect and wipe
If that fails then as a last resort you can try this :
KB27956 : How to recover a BlackBerry smartphone from any state
Please try it and let us know.
Prince
Click " Like " if you want to Thank someone.
If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.
Click " Like " if you want to Thank someone.
If Problem Resolves mark the post(s) as " Solution ", so that other can make use of it.

Blackberry 9790 STUCK at connected to Boot ROM -- tried all solutions

Desperated!
Blackberry 9790 shows connected to boot rom error and always restarts if clicked retry when upgrading with official new OS, then wiped with javaloader.exe, displaying 507 error, problem persists.
Device can always be deteced when connected to DM/Loader/Device Manager, when tried to continue to load OS using DM/Loader, an error pops the same way as before.
Tried with all suggestion/solutions can be found on forums(including this one) and still no luck. anyone can shed some lights here again?
THANKS IN ADVANCE!
Learning Blackberry API
Solved!
Go to Solution.

k don't worry just went through this,
1.go to this link download the latest beta of blackberry desktop software 7
http://opensourcebb.com/2011/11/leaked-blackberry-desktop-software-7-0-0-32-no-keycode-needed/
2. download and install the update for your 9790 which i assume u already did.
3. open cmd , type cmd in start menu , right lick and select run as admin
4. do the following command to change directory " cd c:/programfiles/commonfiles/apploader/ .... This is just the generic path find the right one on your computer
4. after changing directory type this " loader.exe /nojvm "
it will start and it should reinstall your os . This works. i just did it

Connecting to boot rom

Hello, I tried to upgrade my device 8830 blackberry CDMA phone. From first it seems every thing is working smooth for 20-30 minutes but after that it is doing the process "Connecting to ROM" but it is not going ahead of it. It seems it is hanging there. What could be wrong in this ? Why it's process is not going forward.

Hi,
That is supposed to happen.
The devcie is rebooted and then the PC waits for the device to restat and will then take the new OS from the PC.
But you can check a few things: - ensure that power management does NOT turn off the USB port power when their is no traffic!
Device Manager - Universal Serial Bus Controllers - USB Root Hub (#1 thru to the last one)
Properties - Power Management - UNcheck all.
Do that to all the USB root hubs and try again.
Message Edited by OzBBerry42 on 05-26-2009 11:01 AM
Checked out my Blackberry FAQ's and Links to Needed Articles here
http://darkeen.homelinux.com/index.php/Blackberryfaq

Boot Rom/Hard Drive Problem on Pismo. Any thoughts? CPU?

Hello. Here are the details of my problem, and the chronology of events leading up to it. Any thoughts or information that might lead to a solution would be appreciated.
G3/500 Pismo running 10.4.8 on a recently installed (used) 80GB hard drive. Everything working fine, but weak signal on Airport network (MDD (FW) 2x1.25ghz w/Airport Extreme Card, dialup)
Removed Airport card, installed PCMCIA Belkin F5D7011 125 plus. Worked fine, signal still not great. OS kept creating new ports every time Internet Connect was opened. Weird. I decided to restart to see if that would clear up the problem. Also upgraded Airport software to latest (extreme) version. Later wondered if this might have been a bad idea since the Pismo wasn't originally designed to support 802.11(g) cards, but...
Restarted-- or tried to. Got four beeps and 1 long, 3 short flashes on the sleep LED. Reset and repeated this several times. Switched hard drives experimentally. No more beeps, but hard drive spun up.
Eventually nothing even after reset-- no beeps, no spin-up.
Apple says four beeps is a boot-rom problem. A diagram of the logic board shows the boot rom on the CPU board. (Important note: it has been dry here of late, and I changed the Airport card. Static electricity problem? I didn't notice a discharge but...)
I've ordered a G3/400 CPU from eBay to see if that is the problem. I figure I can resell it if it is not the culprit.
Do you have any thoughts on what else it might be? I'll report back here on whether the CPU replacement fixes the problem. Similar symptoms on a Lombard, minus the four beeps, were corrected by replacing the CPU.
Anybody have a G3/500, G4/550, or G3/900 CPU for sale?
Again, any responses to my inquiry would be sincerely appreciated.
From Northern California,
reidjam7

James,
Your Pismo can run an "extreme" 802.11g wifi PC card in the PCMCIA/CardBus slot with no problem; however, you are limited to the original AirPort card under the keyboard...no extreme.
A few procedures you might try in your diagnosis:
1. Remove all peripherals, including PC cards and the optical drive.
2. Lift off the microprocessor card. Apple recommends you remove the heat sink and CPU card as one unit so as not to disturb the thermal transfer pad between the heat sink and CPU; be very careful as you can mistakenly pop the heat sink off including the plastic bracket around the CPU. If you have removed the heat sink in the past, then this would be the safest procedure.
3. Remove/reseat the lower memory module, then firmly seat the microprocessor card; push down very hard on the right side of the card next to the HD and closest to the palm rest where the multi-pin connector resides on the underside. Press down very hard...you may even hear a snap as it fully seats. At this stage you can just plug in the power adapter and see if it will start. I suggest this procedure only because another user stated he solved his bootROM failure which was apparently due to a poor or oxidized connection. There is a very low probability this will be the solution.
4. If no boot, disconnect the HD ribbon cable from the logic board, then try starting; a working powerbook in this configuration should produce the gray screen with a flashing '?'.
5. If still no boot, disconnect the internal rechargeable backup batteries (the red/black/white pigtail from the two round batteries that plugs into the logic board), then try starting. A dead/internally shorted backup battery can prevent startup.
6. Lastly, disconnect the keyboard ribbon cable, then try starting.

Bold 9700 stuck on boot ROM

i have a 9700 and i have been trying to update to 6.0 os. every time i do it, it gets stuck on "connecting to boot ROM". its a t-mobile phone that is unloked and im over seas. any ideas?

Hey njimenez86,
Welcome to the BlackBerry Support Community Forums.
I would suggest re-doing the update from www.blackberry.com/update
-ViciousFerret
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)!

How can I go back to a previous boot ROM version?

Hi. I've been reading these forums for a long time...first time posting.
The short story: I have a Macbook 5,2 running OS X 10.5 with boot ROM MB52.0088.B06, and I'd like to know how to flash the boot ROM version back to MB52.0088.B05.
The long story:
I have a MacBook 5,2. It came with OS X 10.5. As far as I know, the latest boot ROM for 10.5 on a Macbook 5,2 is MB52.0088.B05 (EFI 1.4) (see http://support.apple.com/kb/HT1237).
A while ago, a friend convinced me to update to 10.6. Apparently, with the 10.6 install, it updated the boot ROM version to MB52.0088.B06. Now, I'm concerned that there is a firmware issue (which I might be wrong about, and the reason I think there is a firmware problem is very convoluted but I'll explain if you want). So I decided I wanted to go back to MB52.0088.B05. I had been thinking about going back to OS X 10.5 anyway. So, I backed up my system using Time Machine to a Time Capsule via ethernet. Then I did an Erase and Install with the original 10.5 install disc that came with my Macbook. Then, I used Migration Assistant to restore most of my system from the backup. I should have taken a look at the boot ROM version before I ran Migration Assistant...but I didnt.
The boot ROM version still says MB52.0088.B06.
I tried downloading the MB52.0088.B05 update and running it anyway, and it says my computer doesn't need the update. When I was still running 10.6, I did try the method described here: http://pubmem.wordpress.com/2011/04/09/flash-efi-firmware-update-manually-on-a-m acbook-51/ (which has apparently worked for someone else on a 5,2; see https://discussions.apple.com/thread/3747472?start=0&tstart=0), and it didn't work. I don't know if it's a good idea to try it again now.
So:
Why didn't my boot ROM go back to MB52.0088.B05 after a clean 10.5 install?
Did Migration Assistant import the previous boot ROM somehow?
Should I do another clean install without MA?
Should I try PubMem's manual method again?
Is there another way I can flack back the firmware?
Thanks a ton!
P.S. I'm posting this in the Time Capsule community as well, since it might be an MA issue. Don't get mad, I'm new. If that's against the rules, I'll take it down.
Specs:
Model Name: MacBook
Model Identifier: MacBook5,2
Processor Name: Intel Core 2 Duo
Processor Speed: 2.13 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 2 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MB52.0088.B06
SMC Version (system): 1.38f5
System Version: Mac OS X 10.5.8 (9L31a)
Kernel Version: Darwin 9.8.0

At least you have made some progress. My inkling is the optical drive is dead.
I think you're right.
To run the AHT you would need the AHT disc that came with the computer, but it's unlikely you have it for that old iBook G4.
I do have it, in fact! But it's not working. Here's the situation, copied from a conversation with Kenichi Watanabe over in iMacs...
I haven't been able to run the Apple Hardware Test. I have the AHT CD that came with the computer (v1.2), and I also downloaded v1.2.6 here and burned that to a CD. In both cases, when I load the CD into the external optical drive which is connected via a firewire cable (exactly what I used for the install disc), restart, and press and hold C, the computer ignores the CD completely and boots from the HD. Any idea how to fix this? Or, is there another function I can use to achieve the same thing, maybe in single user mode?
Regarding the Apple Hardware Test CD, holding down the C key will attempt to boot from the internal optical drive. Since there is nothing in there, it boots from the internal hard drive. I would try starting up with the Option key held down. That should get you to the Startup Manager screen. If that CD is in the external FireWire drive, it should be listed as a startup disk choice. Select it and see if it will start up from it.
Right, that makes sense. Unfortunately, in both cases, when I select the CD to start up from, the screen blinks for a second and then returns to the screen where I am supposed to choose a startup disc. It does this as many times as I try to choose the CD, until I select the HD and start up from there.
When I put either CD in the drive, with the computer on and booted from the HD, the CD mounts, and Disk Utility says it's verified. But when I try to select it as a startup disc from system preferences, it doesn't show up. Ideas??
Update: I tried Hoja's reccommendation from this thread using Open Firmware, but in response to
boot cd:\diags
It says:
can't OPEN: cd:\diags
for both CDs.

Beige G3 boot from **** problem; open firmware issues; bad motherboard?

Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.

The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham

Trying to install boot rom update on 10.7.3 - but will not

I'm trying to install boot camp and I can't install until I update the BOOT ROM. I've downloaded the package macmini2011efiupdate.pkg and this coorsponds with my 5.2 model identifier. I have already updated lion to 10.7.3 and I seem to think that maybe the boot rom update was intended for 10.7.2 and it won't let me install on 10.7.3 because it thinks it isn't compatible?
The message I get when I try to install the Boot ROM update is this software is not supported by your system.
Sincerely, Kevin

Same feeling here... I am not advocate of mac. I bought one only for iPhone development. However the hardware is cool, it is my main home PC with Windows 7. For the OSX I left only 80GB disk space and the rest goes for Windows. Well, things would have been different if the OSX was workable the moment I bought it but it was not the case until this EFI update. Now I do not even think of get rid of the Windows.
Back to your case, what is wrong with your mac so you long for the update so badly? From the link you provided I gathered that your mini 5.2 is the one with ATI Radeon discrete graphic. Are there any problems with those? I thought only the HD3000 were so "crappy" because they were the cheapest version.
Anyway, if you slow down, do not expect too much, you will just gradually get used to the OSX philosophy. It's just different than Windows or Linux (on purpose I think). If you lunch Finder and Navigate to Application->Utilities there are the very useful things for start: "Grab" let you do screen capture and "Console" is like the EventViewer on Windows. You should lunch the Console, select "All Messages" and try the update again - look if there is anything logged from the update package which might help. You can also try to reset the SMC and check if that would help - if I remember correctly, the procedure is to unplug everything from the mini, wait ~5 minutes, plug only the power cord keeping the power button pressed for ~1 minute. The funny thing about that is that you have to follow it literally, I left the mouse and keyboard connected and I got wierd result - the fan was keeping at maximum speed. But try to verify the exact procedure on apple web, sorry I am a bit lazy now to search for it again ( I did it because I was desperate about fixing the sleep-resume problem). Anyway, again I would recommend not touching anything if you do not have any problems with your mac just because it does not want to "get something new". Just a common sense
Well, sory I just have scrolled up, and see your originall post why are you about the EFI update. It's really bad the Boot Camp does such check. It really does not make sense. You can do the install manually if you like, it's not so complicated. First go to disk management app in the Utility folder, and partition your disk formating the new one as FAT32 (the one which would be your windows partition). Next boot your minit keeping left alt pressed - you should see a list of booting devices so if you connected USB DVD (or pen drive with Windows - it's simple to do it yourself, just google for the recipe) you can boot the windows install. During the installation select the FAT32 partition and let Windows format it as NTFS and that's all. You can download from apple web a package for all drivers for Windows 7, and just install it in your windows. To choose which os you would like to boot, you can always do the left-alt select. I opted for installing rEFIt - it's really cool boot menu.

Boot Rom/BIOS emulation issue with latest iMacs?

Hi,
Firstly thanks for viewing.
We've just bought 34 new iMac's and previously had (and still have) 60 odd Aluminum iMac's dual booting OS X/Windows which have no problems.
The new iMacs though seem to be having huge issues with booting Window's the first 2 attempts wether using Apple's Startup Manager or rEFIt.
The first attempt the machine will just hang after at a grey screen after volume selection and the second attempt you will receive a "Disk Read Error" and the third attempt the machine will boot normally and this behavior is happening on all of the brand new 34 iMac's.
rEFIt produces the following error:
Error: Not found return from legacy loader;
Error: not found from locatedevicepath;
Error: not found from locatedevicepath;
Error: load error while (re)opening our installation volume;
Which leads me to believe the issue lies with Apple's Boot Rom and the hand over between EFI and BIOS emulation.
I have tried multiple installs of OS X Snow Leopard with 32 bit XP, 32 bit Vista and & 32 bit Windows 7 as well as using Bootcamp 3.1 which really only add's driver support for Windows 7 no Boot Rom updates.
If anyone is having similar issue's I'd love to hear and any work arounds you may have.
Thanks for taking the time to read my post.
Dave Maltby

Hi Sea Dog,
Thanks for your reply . But I cannot find anything related to my problem in the link you attached (or it’s “sublinks”). One sublink is about an annoying usb3 bug with some problem related to the S3 sleep state. (Maybe this is the one you are referring to?) But I do not have this problem, I can wake my PC from the S3 sleep state via my connected USB devices. The problem I have is that I also start my PC after a shutdown (=S5 state I assume) via my connected USB devices, which I do not want to happen since too easy to start the PC accidently for example by just moving the mouse a little bit. As I write above, I think this is caused by MSI:s choice to configure their BIOS regarding “Resume from S3/S4/S5 by USB Device”. If I am right about the cause to my problem, I guess MSI should have chosen this resume option without the "…S4/S5…" or at least without the "S5" (By the way, I seem to have version C2 of the Z87 chipset if I understand a note correct on the MB box.)
Again, am I correct about my idea to the cause of this problem?? Can someone please advise how to solve it if possible??

Wireless card BCM4313 no connection at boot

Hi,
I have an HP Pavilion dv6 with a Broadcom BCM4313 wireless card. I use NETCFG and before the last kernel upgrade I was able to connect to my home wireless connection at boot without troubles. Now I have to do it manually and I need to try 2 or 3 times to see my connection active.
lspci -vnn
02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:1483]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at c3400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: brcmsmac
Kernel modules: bcma, wl, brcmsmac
lsmod
Module Size Used by
cpufreq_stats 3890 0
radeon 992718 0
ttm 54360 1 radeon
ipv6 290407 22
cpufreq_ondemand 6132 4
uvcvideo 64931 0
videodev 78006 1 uvcvideo
media 10437 2 uvcvideo,videodev
usbhid 35256 0
hid 81635 1 usbhid
v4l2_compat_ioctl32 8292 1 videodev
snd_hda_codec_hdmi 22092 1
joydev 9895 0
snd_hda_codec_idt 55175 1
i915 707307 7
snd_hda_intel 22122 0
snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
drm_kms_helper 25409 2 radeon,i915
lib80211_crypt_tkip 8506 0
drm 183380 5 radeon,ttm,i915,drm_kms_helper
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73856 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 19416 1 snd_pcm
r8169 42643 0
lib80211 4158 1 lib80211_crypt_tkip
snd 57786 7 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
sg 25557 0
hp_accel 13864 0
lis3lv02d 10508 1 hp_accel
i2c_i801 8187 0
serio_raw 4294 0
iTCO_wdt 12717 0
hp_wmi 7738 0
intel_agp 10904 1 i915
arc4 1410 2
btusb 11577 0
evdev 9530 9
bluetooth 138465 1 btusb
soundcore 6146 1 snd
bcma 13762 0
i2c_algo_bit 5199 2 radeon,i915
sparse_keymap 3088 1 hp_wmi
mei 31249 0
i2c_core 20133 7 radeon,videodev,i915,drm_kms_helper,drm,i2c_i801,i2c_algo_bit
iTCO_vendor_support 1929 1 iTCO_wdt
pcspkr 1819 0
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
intel_ips 11213 0
psmouse 55224 0
intel_gtt 14423 3 i915,intel_agp
mii 3995 1 r8169
input_polldev 2882 1 lis3lv02d
battery 10905 0
wmi 8411 1 hp_wmi
ac 3265 0
button 4470 1 i915
brcmsmac 594624 0
thermal 7863 0
video 11228 1 i915
brcmutil 6563 1 brcmsmac
mac80211 215605 1 brcmsmac
cfg80211 160516 2 brcmsmac,mac80211
rfkill 15402 3 hp_wmi,bluetooth,cfg80211
crc_ccitt 1331 1 brcmsmac
acpi_cpufreq 5877 1
freq_table 2451 3 cpufreq_stats,cpufreq_ondemand,acpi_cpufreq
processor 24256 1 acpi_cpufreq
mperf 1275 1 acpi_cpufreq
ext4 369556 2
mbcache 5817 1 ext4
jbd2 71074 1 ext4
crc16 1297 2 bluetooth,ext4
sr_mod 14951 0
sd_mod 28307 4
cdrom 36329 1 sr_mod
ahci 20865 3
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
ehci_hcd 39511 0
scsi_mod 131482 4 sg,sr_mod,sd_mod,libata
usbcore 142544 5 uvcvideo,usbhid,btusb,ehci_hcd
dmesg | grep wlan0
[ 11.715805] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 13.791409] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 16.885059] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 16.886567] wlan0: authenticated
[ 16.890100] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 16.892793] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 16.892798] wlan0: associated
[ 16.894146] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 26.697130] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
[ 87.612906] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 89.754106] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 92.849882] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 92.851661] wlan0: authenticated
[ 92.851823] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 92.854142] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 92.854150] wlan0: associated
[ 92.855920] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 103.719958] wlan0: no IPv6 routers present
[ 105.980215] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
[ 120.237260] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 122.316759] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 125.422195] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 125.423760] wlan0: authenticated
[ 125.423960] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 125.426083] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 125.426090] wlan0: associated
[ 125.428085] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 136.398877] wlan0: no IPv6 routers present
You could see that first I get the connection and then I lost it... for 2 or 3 times, then I could connect without problems.
ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:338 errors:0 dropped:0 overruns:0 frame:0
TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27772 (27.1 Kb) TX bytes:27772 (27.1 Kb)
wlan0 Link encap:Ethernet HWaddr E0:2A:82:A2:B5:88
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::e22a:82ff:fea2:b588/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12484 errors:0 dropped:0 overruns:0 frame:0
TX packets:9606 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13841736 (13.2 Mb) TX bytes:1241490 (1.1 Mb)
iwconfig
wlan0 IEEE 802.11bgn ESSID:"WLAN_A9"
Mode:Managed Frequency:2.452 GHz Access Point: 50:67:F0:AB:4F:D4
Bit Rate=54 Mb/s Tx-Power=19 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=40/70 Signal level=-70 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:82 Missed beacon:0
my wirelessCasa netcfg profile
CONNECTION='wireless'
DESCRIPTION='A simple WEP encrypted wireless connection'
INTERFACE='wlan0'
SECURITY='wep'
ESSID='WLAN_A9'
KEY='s:mykey'
IP='dhcp'
POST_UP="notify-send -u critical -i /usr/share/icons/Faenza/status/48/connect_established.png -t 15000 'Connected to WLAN_A9'"
POST_DOWN="notify-send -u critical -i /usr/share/icons/Faenza/status/48/gnome-netstatus-disconn.png -t 15000 'Connection lost'"
# Uncomment this if your ssid is hidden
#HIDDEN=yes
rc.conf
NETWORKS=(wirelessCasa)
DAEMONS=(syslog-ng dbus net-profiles net-auto-wired !network !netfs crond laptop-mode alsa slim @acpid @cups)
When I execute netcfg for the first time (after boot) I see:
#NETCFG_DEBUG=yes netcfg wirelessCasa
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
:: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
> DHCP IP lease attempt failed.
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_down if_down
DEBUG: wireless_down stop_wpa wlan0
DEBUG: profile_up connect failed
[FAIL]
And the second one:
#NETCFG_DEBUG=yes netcfg wirelessCasa
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
:: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
DEBUG: ethernet_iproute_up hostname archlap
[DONE]
I've tried to use the wl driver but it doesn't seems to work properly.
Could anyone help me please?
Thank you,
enrico

litemotiv wrote:
Hmm it seems your card now takes longer to connect, the 'deauthenticating by local choice' often means that the default timeout is reached and netcfg disconnects. You can try adding a specific timeout parameter to your netcfg profile:
TIMEOUT=60
That doesn't explain why it takes longer to connect than before, but at least you should be able to connect in 1 try again.
Hi,
thank you for your time!
I'v tried adding the timeout line to my profile but it doesn't change nothing
I could connect at 3rd try.
Any other idea?

BOOT ROM VERSION ISSUES WITH MINI MAC POWERPC G4 (1.2)

HI,
I AM HAVING SOME BOOT PROBLEMS ON REBUILDING MY MAC MINI. WHENEVER I PUT IN A BRAND NEW COPY OF EITHER PANTHER OR TIGER THE BOOT SCREEN WITH THE APPLE LOGO CRASHES AND FUNNY GRAPHICS APPEARS, RESULTING IN A FORCED REBOOT AND USING F12 TO EJECT THE CD. THE MAC MINI IS FINE BOOTING OFF OF ITS OWN MANUFACTURE CD, WHICH IS A COPY OF PANTHER, BUT WON'T UPGRADE WITH ANY TIGER DISKS. I HAVE EVEN MANAGED TO CHANGE THE DISKS WITH SOMEBODY ELSE WHO WAS SUCCESSFUL IN UPGRADING TO TIGER.
I HAVE LOOKED ON THE INTERNET AND OTHER PEOPLE HAVE EXPERIENCED THE SAME PROBLEM. THEY MENTIONED THAT I SHOULD CHANGE/UPDATE MY BOOT ROM VERSION FROM 4.8.9F1 TO 4.9.8F4.
DOES ANYBODY KNOW WHERE I CAN GET THIS BOOT ROM UPDATE? I HAVE LOOKED ON APPLE DOWNLOADS, BUT NOTHING APPEARS TO HELP. ANY OTHER SUGGESTIONS APPREACIATED.
MANY THANKS
SUPERHEROTIMO

Welcome to the Apple Discussions!
First, a word of etiquette, writing your post in ALL CAPS is considered the same thing as yelling. Please don't use ALL CAPS when writing your messages.
Exactly which Mac mini do you have? Is it a G4 Mac mini running at 1.2, 1.3, 1.4 or 1.5GHz? (If it came with Panther install disks, it couldn't be an Intel Mac mini.) Which version of Mac OS X came with your Mac mini? Some of the earlier Mac minis shipped with Mac OS X 10.3.7 and will not startup from any earlier version (most of the retail copies of Panther are 10.3.0 or 10.3.4). If it's a Mac mini that shipped later, it would have come with Mac OS X 10.4.2 and, again, won't startup from any earlier version (most retail copies of Tiger were 10.4.0 but now have 10.4.4). Trying to startup from a disk that's the wrong version will usually cause a "kernel panic" and force you to restart.
So, if your Mac mini shipped with Mac OS X 10.3.7, you should be able to use any retail copy of Mac OS X 10.4 (Tiger) to update your computer. However, you won't be able to update to 10.4 from the install disk that came with another Mac. You will need to buy a retail copy of your own.
There are no firmware updates available to download to upgrade the "Boot ROM" on your G4 Mac mini, so that option is really not available.
-Doug

3 yr old macbook pro boot up problems

Hi, I bought a 13” macbook pro 3 yrs ago.. Its running the latest version of Lion.
I have a boot up problem.
Initially the boot up sound will go off and get stuck on a white screen.
I’ve left it on for 30mins….it took me to a disk disk utility screen…
I’ve clicked on repair disk….after about 15mins
Its saids
Checking Journaled HFS Plus volume
Invalid B-tree node size
The volume could not be verified completely
Then I restart….now… not only does it get suck on the white screen, but the boot up sound keeps repeating
Im currently living in Hong Kong, what should I do now, and if it requires repairs…how much would It cost.
Thanks,
WB

I don't know what happened. It is not a common occurrence. It can be caused by power outages, abnormal shutdowns, software glitches, etc.
I would think seriously about a backup strategy for the future:
Basic Backup
Get an external drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
Carbon Copy Cloner
Data Backup
Deja Vu
SuperDuper!
Synk Pro
Tri-Backup
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.
Although you can buy a complete external drive system, you can also put one together if you are so inclined. It's relatively easy and only requires a Phillips head screwdriver (typically.) You can purchase hard drives separately. This gives you an opportunity to shop for the best prices on a hard drive of your choice. Reliable brands include Seagate, Hitachi, Western Digital, Toshiba, and Fujitsu. You can find reviews and benchmarks on many drives at Storage Review.
Enclosures for FireWire and USB are readily available. You can find only FireWire enclosures, only USB enclosures, and enclosures that feature multiple ports. I would stress getting enclosures that use the Oxford chipsets especially for Firewire drives (911, 921, 922, for example.) You can find enclosures at places such as;
Cool Drives
OWC
WiebeTech
Firewire Direct
California Drives
NewEgg
All you need do is remove a case cover, mount the hard drive in the enclosure and connect the cables, then re-attach the case cover. Usually the only tool required is a small or medium Phillips screwdriver.

Boot camp assistant won't run - says must update boot ROM.

Just updated my mid-2010 13" MacBook Pro to ML 10.8.2. When trying to run boot camp assistant, I get the following:
No firmware or Boot ROM update seems to be available, however. EFI update 2.5 is not for my Mac, nor is v.2.6 - others don't install, either.
Anyone have the answer to this problem?

Hey thanks!
i spend a lot of time finding the update and the solution!!! and after this post save the day!
thanks gvoyager9

BBBOLD 9000 CONNECT TO BOOT ROM PROBLEM

Similar Messages

Maybe you are looking for