Battery or board?

I have a Powerbook G4 that's about 5-6 years old. I replaced the hard drive two years ago, and participated in Apple's battery replacement program four years ago and the adapter was replaced about three years ago. Here's the issue: Recently when I boot up my laptop in the morning there's no green or amber light (no light at all) on the adapter it will flash the "powering down to conserve battery" message at me, even though it's been plugged in all night. Then it takes about an average of two weeks for the battery to show a full charge. Here are my battery stats:
Battery Installed: Yes
First low level warning: No
Full Charge Capacity (mAh): 1194
Remaining Capacity (mAh): 1194
Amperage (mA): 0
Voltage (mV): 12441
Cycle Count: 169
As this is the only computer up and running at my house at the moment, it gets left on a desk plugged in all day for anyone's use, though it is not always turned on. I'm going back to school soon and I'm just trying to figure out whether it's worth sinking more money into this laptop, or if it's time to start shopping for a new one. Thanks for your time.
-J

Your battery is about dead, Jenn, and if you want to use the Powerbook portably, you'll have to buy it a battery.

Similar Messages

Diagnostic mode--battery or board?

I have a first generation Nano with a short battery life. Is there a way of using the diagnostic mode to determine if it is due to a battery gone bad or if it is due to a hardware problem? What do the results mean in the power test??
The Nano seems to indicate full charge fairly quickly (whether by wall charger, usb-computer, speaker base), but only provides 2 hours of play time.
Thank you in advance!

I went ahead and replaced the battery--all is well now, the Nano plays at least as long as when it was first purchased!

Combo Drive quit after replacing PMU/Battery board

Hi-
My Pismo (firewire, 400mhz) has a combo drive which barely worked, but worked up until
I had to replace the PMU/Battery logic board. Now it won't recognize a cd or dvd, period.
Up to now, it made a lot of noise but it would load a cd and eventually play it. I wonder if I have to
re-install software for this, or if maybe it was just time for it to finally die. (I reset the PRAM
and the PMU; I tried Disk Permissions; it's listed but no fixes are made available (all the options are in light grey and cannot be selected). I have the 10.3.9 install disk, and a system restore disk;
they don't play.. however i have not tried to reboot from them.
If I do try booting from a system restore or system install disk, will I lose any and all stuff I have now (music, etc).. or will it just update and repair the system?
thanks in advance
sr
ps in my system profiler I see the combo drive is listed twice. It wasn't before.

Here's how I revived my Pismo's failed disc drive. http://macosx.com/forums/howto-faqs/290895-how-resurrect-failed-laptop-disc-driv e.html
 Cheers, Tom

Solution - Battery error is detected. Irreparable damage to the battery has been detected. Replace

I own a T61 7658 I bough on 2008, it worked great with the default power settings until October 22nd I decided to change my power profile to MAXIMUM PERFORMANCE.
Next day I received on Message Center...
10/23/2010 - Battery health is critical. With the current system settings and a full charge, your battery can provide approximately 3.0 hours of use. A new battery could provide up to an estimated 5.5 hours.
I kept using the Laptop with the Max performance until...
11/12/2010 - Battery error is detected. Irreparable damage to the battery has been detected. Replace the battery with a new one.
I have used IBM/Lenovo for years and even had used batteries for 5 years without a single issue.
I have read many posts of people having the same problem not only with T61s, but many other Lenovo models, and also read posts of Lenovo's administrators suggesting this is normal and justifying that batteries should be good for at least 12 months and after that we are on own, basically meaning we should be thankful in name of our own safety that we had that battery protection and we must replace it at our own cost and forget about it. That is a very easy way out, isn’t it.
But certainly, not only batteries with more than 12 months are failing, even new batteries are and have been replaced with multiple exchange programs posted by Lenovo in their website just as in http://download.lenovo.com/lenovo/content/batt/082009/LandingPage.html. and also in multiple MIGR battery replacement campaigns available to all online as well.
Good thing here is that Lenovo has recognized the problem and has exchange the batteries still under warranty and also few of the batteries without warranty limiting to some serial numbers on the MIGR battery replacement campaigns, but the bad side is that Lenovo is leaving behind other clients like me and many others not being selected for replacement. But I’m sure we all have a good battery but turned useless due to the Lenovo programmed safety temperature limits in the power manager and the battery board. Please let me explain.
This is my conclusion. There is nothing wrong with used or new batteries or their cells in 99% of the cases, I'm sure my battery is okay although is being turned useless by the battery protection feature on my T61.
Lenovo must recognize the problem is the settings they have programmed on the power manager and battery protection board. It is very understandable that when users select a Power Scheme that demands higher amounts of power to generate better performance on the system this also demand additional power generating heat on battery and on the power supply as the computer is running at full performance, just as happens on my ipod when watching video, or in my kid’s R/C truck when running continuously and will happen with any other battery powered device.
Therefore any scheme requiring performance is generating heat and is tripping the battery protection and this is not a client’s fault, as are we just using an available scheme provided on our Lenovo system. If the battery protection is not calibrated to support this power demand, then there is a poor design/testing of the capabilities of the system and the battery protection parameters that instruct the battery to save itself from a fire or burning … which is understandable.
The bad side is that there is not possible reset option for the end users, the only option is to buy a new battery at our own cost after the 12 months of warranty, when the cause of the problem is originated in the computer system design settings and can happen at any time, that is way, the system warned me, as in:
10/23/2010 - Battery health is critical. With the current system settings and a full charge, your battery can provide approximately 3.0 hours of use. A new battery could provide up to an estimated 5.5 hours.
The computer is saying! At maximum performance, You are using too much power, and my battery will last just 3 hrs (9 cells on my system) instead of the 5.5 hrs that should last. But not only the running time was reduced, the heat on the power supply system and Battery was also increased due to the higher power demand, the battery can not handle the demand and protect itself to prevent fire or damage.
So who has to pay for this? Can Lenovo do something about it? For us client and for future clients? This not a matter of having or not having warranty, this can happen at any time in any computer.
I'm writing this hoping to be heard and supported and I hope LENOVO provides a satisfactory solution to the issue. I'm not going to say will never buy Lenovo again I already did, I invested my money on Lenovo and with warranty or not I'm looking forward to get a decent response.
Lenovo must change the parameters for tripping battery protection probably handled at BIOS level, and to provide a reset feature to all "locked" batteries there is many people that has lost at least one battery, some other more than that.  Since even if we get a replacement, the chances  the issue will continue is there, as long as I select a high power demand scheme the problem sooner or later will be back.   Even car makers support their clients beyond the warranty if they detect that the issue compromises safety and their reputation.  Fix it.
M.Padron.

amtho, welcome to the forum,
start by looking at this site and also look at this site which is actually linked to from the first one.
Hope this helps
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Only a dead battery...I hope?

Hello,
I've been having recent problems with my 14'' iBook G4. Prior to this computer, I had a 12'' iBook G4 with frequent kernel panics, so I parted that thing out to make a few extra bucks. To my dismay, this "new" iBook G4 (purchased from eBay with a Square Trade Warranty) is having problems. I was on it the other day about to burn a CD via iTunes and as it was preparing the disc, the computer shut off unexpectedly. The battery was at 89% when this happened, so I panicked, remembering the faulty machine I had before this. When I turned the computer back on, it informed that the clock had been reset and applications might behave erratically, and was set to some date in 1969! The computer frequently does this, especially in processor-intensive applications (I.E. converting mp3's to AAC files in iTunes). I looked over the auction at least ten times, making sure I hadn't overlooked some crappy as-is policy, but then saw that the only thing NOT guaranteed was the battery.
Downloaded the coconutBattery app, and its health is at 29%, and the computer does not shut down when connected to power. However, I'm still curious why the clock is being reset. If I take the battery out and then connect it to power and boot up without the battery, the clock is not reset. Is this normal if the battery has reached the end of its useful life?

Hey Christian,
the computer shut off unexpectedly. The battery was at 89% when this happened, so I panicked, remembering the faulty machine I had before this. When I turned the computer back on, it informed that the clock had been reset and applications might behave erratically, and was set to some date in 1969!
So the system clock is controlled by the PMU. It resets itself when when the power to the PMU chip is interrupted. There is a super capacitor (~.22F) that will hold settings for about 30 seconds in a no power situation. This is facilitate a battery swap. It is possible that your super cap is bad and when you're running on battery power a power glitch would cause the clock to reset. The glitch could be caused by a bad battery, bad battery connector, bad battery input board or a loose battery lock.
If the super cap is bad that's not actually such a big deal. If you're running on the net all the time and the "set date & time automatically" box is checked in the Date & Time preferences panel the date and time will reset automatically.
Richard
Message was edited by: spudnuty

Rapid battery drain after Mavericks Install

Hey everyone,
I've spent a lot of time reviewing the existing threads and haven't been able to pinpoint a solution to my issue. I upgraded my late 2008 MacBook Aluminum 2.4 GHZ to Mavericks, and noticed considerable battery drain. I made an appointment at the Apple Store to do a clean install of Mavericks, and this seemed to help but as I installed software required to access internet at school (SafeConnect, AnyConnect VPN, Avast) my battery life has gone down again. Also, the battery drains when the computer is supposed to be in sleep mode. I have a new battery on board (127 cycles, my cycle count has increased a lot due to this battery drain issue). Does anyone have an idea of what could be the offending software and provide me potential alternatives?
Some numbers for reference: With Snow Leopard I have 3.5 hrs of battery life, and after my initial clean install I had 3.5 hrs of battery life (so no improvement, but no worse performance either..). Now I am lucky to make 2 hrs with a full charge.
Loaded kernel extensions:
com.avast.PacketForwarder (1.4)
com.cisco.kext.acsock (1.1.0)
com.avast.AvastFileShield (2.1.0)
Loaded user agents:
com.avast.helper
com.hp.devicemonitor
scClient
com.oracle.java.Java-Updater
com.cisco.anyconnect.gui
com.avast.userinit
com.spotify.webhelper
com.avast.home.userinit
Inserted libraries:
User cron tasks:
System launchd configuration:
User launchd configuration:
Login items:
Flux
iTunesHelper
Safari extensions:
wrc
AdBlock
Restricted user files: 12
Extrinsic loadable bundles:
/Library/Internet Plug-Ins/Flash Player.plugin
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin
/Library/Internet Plug-Ins/SharePointBrowserPlugin.plugin
/Library/Internet Plug-Ins/SharePointWebKitPlugin.webplugin
/Library/Internet Plug-Ins/Silverlight.plugin
/Library/PreferencePanes/Avast.prefPane/Avast.prefPane
/Library/PreferencePanes/Avast.prefPane
/Library/PreferencePanes/Flash Player.prefPane
/Library/PreferencePanes/JavaControlPanel.prefPane
/Library/Spotlight/Microsoft Office.mdimporter
Unsigned shared libraries:
/Library/LaunchAgents:
Safe.Connect.client.plist
com.avast.userinit.plist
com.cisco.anyconnect.gui.plist
com.oracle.java.Java-Updater.plist
/Library/LaunchDaemons:
Safe.Connect.plist
com.adobe.fpsaud.plist
com.avast.init.plist
com.avast.uninstall.plist
com.cisco.anyconnect.vpnagentd.plist
com.microsoft.office.licensing.helper.plist
com.oracle.java.Helper-Tool.plist
net.cloudpath.HelperTool.plist
/Library/PrivilegedHelperTools:
com.microsoft.office.licensing.helper
net.cloudpath.HelperTool
/Library/StartupItems:
Library/Fonts:
Library/LaunchAgents:
com.avast.home.userinit.plist
com.spotify.webhelper.plist

Avast is garbage. Uninstall it according to its instructions. Avast's uninstaller will remove it completely.
If your school requires you to use Avast you will just have to tolerate its detrimental effects on your Mac's performance and battery life.

Troubleshooting Logic and I/O board on A1370 11" MB Air after wine spill

OK,
My wife spilled about 1/4 cup of wine on the keyboard of her MacBook Air. This is an A1370 (EMC 2471) 11" (Core i5 Mid 2011) model.
I have read the articles in this forum and others on what to do when you spill on one of these computers.
What I would like from this forrum is guidance/help/suggestions/best-guess on determining what I need to replace.
Here are the details.
Directly after the spill, she tells me that the computer turned itself off, and would not come back on - no lights, no start chime, nothing.
I immediately took the back off the computer and mopped up what I could without completely dissasembling the system because it was late at night.
The next morning, one of the kids tried to start the computer (ya, I know that's bad and don't know why the **** he did it but he did). He "fessed up" later and said that when he pressed the power button the keyboard lights came on and chimed then went off and that was it.
I proceeded to take apart the computer, removing the battery, logic board, I/O board, airport, HD, etc.
I noticed that there was wine stain on the logic board and the I/O board and other areas and cleaned it all up with isopropyl and Q-tips.
I then gave the logic board and I/O board a very thorough wash with a cleaning spray by MG Chemicals called "Safety Wash II". Basically alcahol.
I scrubbed the two boards thoroughly with a soft bristle brush for about an hour, then I soaked the entire board in isoproyl alcohol bath for 2 hours then sprayed and scurbbed again until I felt that I got all the wine off.
I did notice a small amount of "purble" on two of the tiny contacts for the LCD connection on the logic board but could not remove no matter how much scribbing I did. The two contacts were number 3,4 if you are counting from right-to-left when viewing the logic board from the bottom of the PC, with the fan to the right.
After a good dry with a hair dryer and letting it sit a few more hours I put it all back together, crossed my fingers, plugged in AC and pushed the power button -- nothing happened.
I had an orange light on AC adapter so I let it charge over night. The next day the AC light was green and the backlight on the keyboard was lit. Tried starting and still nothing.
I took the back off again and disconnected the battery then plugged in the AC adapter. At that point the fan started spinning and I got the start "chime" but nothing on the LCD.
I disconnected AC and plugged in battery and noticed the same thing.
Now whenever I disconnect AC chord and reconnect it I get the chime with fan starting but nothing more.
Also, the backlight on the keyboard stays on all the time and the fan runs all the time if the batter or the AC is connected.
So, I am wondering what I need to replace?
logic board?
I/O board?
keyboard?
all of the above?
Would appreciate guidance.

Zane is right, ....I used to repair laptops for years as well,.....diagnosing such things is FUTILE.
Lucky you there are are almost no parts IN the macbook Air. Its IO and Logic and thats really almost it.
Contact Apple for in shop full diagnosis and parts replacement,......youre not going to "diagnosis" nor "fix" it after a spill (without parts replacement) by any means.
Even if you had a BEST CASE spill.....corrosion and failure would ensue on average 7 to 20 days.......then kaput.
Spills turn the best computer repair person into what looks like (to the customer) dufus......WHY? ......because its a "spin the wheel and GUESS where ALL the liquid went"
replace A......works ok for a week.....whoops, ..........oh yeah, theres a couple drops under under a solder connection on part B........replace that....

PowerBook G4 Won't Charge or Run on Battery

I've got two PowerBook G4s, both FireWire 800 models and one of them is behaving very oddly. The computer boots and runs perfectly. If the battery is discharged then the power plug shows amber and the battery indicator shows that it's charging but VERY slowly (about 1% every 15 minutes) and only to about 13% charge. At that point the battery indicator says "Battery is not charging" and the power plug shows green. Pull the power plug and the computer instantly shuts off, even though it allegedly had a partial charge.
I have tried:
Completely clean OS install (10.5, fully updated).
Reset the power manager (http://support.apple.com/kb/HT1431).
Replaced PRAM battery with a known good unit.
Replaced laptop battery with a known good unit.
Replaced DC-IN board with a known good unit.
Replaced AC power adapter with a known good unit.
The known-good units came from my other PowrBook G4 which operates perfectly with both DC-IN boards, both PRAM batteries, both laptop batteries, and both power adapters.
Before I call it quits on the motherboard, does anyone know what else could be the problem?

There's only 4.5 components to the charging circuit: Power adapter, DC-In card, battery, logic board, and .5 for the PRAM battery (since it can influence the power circuit).
Unfortunately, there's no test for the charging components, you have to replace them until you find the offending part. You've replaced everything but the logic board, and as long as you're satisfied that the replacement parts from you other PowerBook are good, that only leaves one choice.

Macbook Overheating/Battery?

Hello,
This is my first post on the community boards so I would like to take a minute to say hi and thank you for looking into my problem.
Now to start, I have been having some trouble with my Macbook recently. I have been having an issue where I will be doing something very CPU/GPU intensive, them my computer just randomly shuts off. It has happened twice now, once when rendering video in Final Cut Pro X in Mac OS, and then just now again when I was playing Team Fortress 2 on my Windows partition. I did notice that the temperatures were a bit high (about 180-190 degrees) but I have never had any trouble with it shutting off before. I can be overheating because I know Macs have a failsafe built in to keep them from damaging themselves, but the thing that has been steering me away from this is the fact that my battery gets completely drained when this happens. I will be at about 80% charge while working, then my computer shuts off with no warning, and ALL the charge is dumped out of the battery. So I am not sure if it is just the normal failsafe or if it is the fact that my batter is going. I have been getting the Service Battery announcement as it just passed its 80% life mark but I still have a long way to go before it is completely depleted. If it helps at all, my setup is as follows:
Macbook Pro 13 inch 7,1 (Mid 2010 Model)
2.4 GHz Intel Core 2 Duo Processor
8GB DDR3 RAM at 1067Mhz
120GB OWC Mercury Extreme Pro 6G SSD
250GB 5400RPM HDD (Replaced optical bay)
Nvidia GeForce 320M with 256mb of shared Vram
OS: Mac OS 10.8.3
Dualboot: Windows 7 Ultimate 64 Bit via Bootcamp
Battery: 4331 mAh remaining of the designed 5770 mAh (fluctuates from 75%-83% life)
Battery cont.: 639 charge cycles, 33 months old
Case: Speck Seethru Satin snap on case (put this in because it may restrict airflow if it turns out to be overheating)
Repairs: Upgraded RAM, Upgraded to SSD, Replaced Optical Bay with mounting bracket and HDD, replaced the top case due to a broken keyboard from a cofee spill (about 9 months ago).
So that is pretty much the case. Doing something that works my computer hard, shuts off without warning, and all the charge is drained in the battery. It Even happens when I am plugged in. I have tried resetting the SMC and NVRAM, still no help. Just want to know if it is overheating, battery, logic board, or charging board.
Let me know your suggestions (whether is be taking it to the Genius bar or trying something at home) I am all ears. Keep in mind that I am pretty technical and know this machine inside and out so don't be afraid to ask me to open it up and peek inside, I have already had this machine completely in pieces.
Thanks,
Hank

***UPDATE***
Just recently, on the magsafe part of my charger, I heard a high pitched hissing/whining sound. Almost like a tiny computer fan but a bit of hissing mixed in. I unplugged my chager then plugged it back in and the hissing went away but then comes back after a bit. I am stumped on this one...

Replacement iBook G3 battery not recognised - non Apple brand

Hi World
Try this conundrum for size...
I bought 'new' (non-Apple) battery on Ebay and my iBook does not appear to recognise it. i.e amber charge light does not illuminate - it stays green. I've done a PMU reset, Battery Rest 2.0, Restarted the iBook etc etc - nothing seems to work. The only reason I want a new battery is to avoid resetting the date every time I restart the iBook - I never travel with it and it's always powered from the mains electricity.
For information - the original (dead) Apple battery happily illuminates amber - but obviously can not store a charge.
I have also received a replacement for the intial new battery and it is still showing the same response i.e. no amber glow
Is there a printed circuit in these batteries that is needed to say 'hello' in an exact way and therefore allow charging to occur? If so, if I were to extract the new cells from my new battery and somehow wire them into the old Apple case, would that work? (I have read about spot soldering and it sounds a bit daunting)
Any answers gratefully appreciated
Any answers

FIRST: You wrote "Is there a printed circuit in these batteries that is needed to say 'hello' in an exact way and therefore allow charging to occur? If so, if I were to extract the new cells from my new battery and somehow wire them into the old Apple case, would that work? (I have read about spot soldering and it sounds a bit daunting)"
I think these batteries do contain some electronic circuitry, but I don't know whether that's the source of your problem (read on). In any case, with many years of technical work under my belt, I would be reluctant to attempt the cell transfer you suggest -- batteries have a way of being more dangerous than people think, as there's a fair amount of energy stored there.
But, on to your problem. You might nott want to say, but I'd be interested in the source of these batteries, as I'm in the middle of a "new" battery experience that has some similarities:
For reasons I won't go into, I have four iBooks in my possession -- and all had batteries in various states of decrepitude (some wouldn't take a charge at all, some would take different amounts of charge at different times, all were essentially useless). BUT ALL WERE RECOGNIZED BY THE COMPUTER.
So I purchased, on-line, two new batteries and they were delivered quickly. BOTH of them worked immediately and perfectly in TWO of the four computers, but went totally unrecognized in the other two computers. After considering the possibilities, I concluded that the problem might well be a very small misalignment of the connectors in the computers that didn't work with the connectors on the new batteries. (I'm talking about the plastic-shrouded 6-pin connectors, one in the computer and one on the battery, that engage when you install the battery). There is precedence for this kind of issue, as I have seen reports on the web of people resorting to cardboard shims to improve the engagement of the connectors. But, in my case, there simply is not room for any such shims, and nudging the battery one way or the other (a tiny distance) didn't make them work.
I had unrelated internal work to do on one of the two computers that didn't recognize the batteries.
While I had it apart, I replaced the battery charger board, which incorporates one of the mating connectors. (+I didn't suspect the electronics of that board, rather the physical positioning of the board as secured in the computer case, or of the connector on the board+.) The result was that this computer now worked with one of the new batteries but continued not recognizing the other new battery.
What this comes down to, I think, is a physical tolerance issue -- probably with the lateral positioning of the connectors, either in the computer, or on the battery, or a combination of both. It could also have to do with the connector condition. The connector in the computer is obviously (usually) as old as the computer itself; the connector on the battery is . . . who knows? Although the battery is said to be new, the battery manufacturers may somehow make use of old battery cases (and connectors). Most if not all connectors rely on some spring tension in the contacts to keep the contacts mated, and the contacts can also be affected by corrosion -- and deterioration of older connectors is simply a real possibility.
Would be really interested in what approach you take and the results. Please post back.
There seem to be a lot of sources for these batteries on-line, but it's possible they all come from a small number of outfits (or even just one outfit) that builds (or rebuilds) them. If, ultimately, all the battery cases (with the connector) come from just one source, then the problem might be likely to show up no matter what your source (or the name on the battery, etc.) If I'm correct on this, then it's going the be a gamble as to whether a battery purchased from another source will solve the problem.
But, what choice is there? I think your best bet might be to return that second battery and then buy another one from . . . ? (somebody different). Or maybe someone who follows this forum can name a recent supplier with which there has been no problem whatsoever.
Message was edited by: osimp

SONY XPERIA Z1C NOT BOOTING SONY/BATTERY LOGO WHEN CHARGED - THATS ALL.

Hello. I got problem with my "new-used" Z1Compact. I get it 2 days ago.
Phone is not starting, only bootlooping with sony and battery logo when charger is plugged.
There is no reaction for power button.
When i turned phone ON(plugged to power) i can "make a move" but i can only restart it, with power+vol, im getting 3 vibrations, and phone is restarted. (after restart when im trying vol+ or vol- i dont get nothing)
At first i thought it was matter of crashed ROM when somone updated, so i get STOCK for EU, and i plug phone to USB( same screen with sony + battery logo) with flashtool, he detects phone in flashboot and flash mode, so ive flashed my phone with D5503_14.4.A.0.108_Central Europe (1280-7864), but with no efect(i wasnt abble to WIPE in flashtool..).
Pc companion does not detects him, there is a Windows pip, but program dont recognize Z1C, but if i turn phone in flash mode( with vol-down) he is abble to detect device, like a Sony/Sony Ericsson.
For Windows i'm SONY ADB Interface Device.(ive installed Flashtool Drivers for all Z phones).
So i dont know what i can do to fix my sony. Any advise?
I'm not a pro in tel-service. Can someone can tell me do why system is not loading ?
No bootloader? Something wrong with flashing ? No drivers in PC ? When ive briked my sony Z1, i was in same situation, but phone was reacting for power, and i was ablle repir him with PC Companion.

If it's not switching on without power been connected then you have a battery issue or the connection between battery and board is faulty so you would need to either return your device to the place of purchase or contact Xperia care and have your device inspected http://www.sonymobile.com/global-en/support/contact-us/
For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. Richard P. Feynman

PRAM Battery for Powerbook G4 17" 1.33 problem

I have an Aluminum Powerbook G4 17" 1.33 GHz computer and need to replace the PRAM battery. This poses a problem. Typically they sell the PRAM battery/USB board as one replacement because the two rechargeable 3.7 v coin CGL 2430 batteries are spot welded & soldered to the USB board in parallel. The replacement part is 922-6064. When I look for a replacement, all I can find are used parts which mean that the batteries have a diminished life. Panasonic stopped making those batteries in 2005 and I can't find anything comparable. Even the places that advertise new parts say they only have used in the end. Next model up, the 1.5 GHz Apple made a battery pack that can be replaced. NewerTech makes that replacement. I would like to replace the batteries on my present USB board - new ones can be soldered or a plug can be added, but I have run into these problems. Those coin batteries are not available and I know the voltage, but not the amperage of those coin batteries that were used. NewerTech can't tell me the voltage/amperage of their battery pack for the newer version Powerbooks, so I don't know if jury-rigging one of those packs would work with my version of the Powerbook. I can't find Apple's specs anywhere for the voltage/amps that should go into the PRAM/USB boards in the 1.33 model and the 1.5GHz model so that I can figure how to do this repair modification. The USB boards for both models look the same, but I don't think that they are, but what is the difference? Anyone have an idea how I can do this modification to add PRAM power to my USB board?

Actually, this is a very minor problem, if the negligible incidence of posts here about replacement PRAM batteries dying is any indication. Apparently there are very, very few users of Powerbooks (going all the way back to the G3s of 1998-2001) whose use of these machines has outlasted a second PRAM battery. I still have a working 2003 Titanium Powerbook with its original PRAM battery in place, a working 1998 Powerbook G3 with its original PRAM battery in place, and a working 1997 Powerbook 1400C with its original PRAM battery in place. I doubt that new replacements are available for any of those batteries, but I wouldn't hesitate to buy used ones if I intended to use any of those computers for several more years. I suggest you go ahead and do the same, and install the used battery yourself to keep the cost down.
Message was edited by: eww

Some keys still do not work on my Macbook Pro 13"

i have a 13" macbook pro running OS Mavericks
My laptop was on the bed and i found it with dog pee on the right side of the keyboard. i immediately cleaned the top of the keyboard and turned it upside down so liquid would come out. It was clean and the computer was still running so i thought everythings ok. i read 2 magazines and then tried to use my laptop again and noticed the keys were not functioning properly. i pressed several keys to test it and then turned it off. i lifted the laptop and noticed it was still wet underneath. i then felt liquid coming out of the right side. i turned the laptop on its right side so that i could force the liquid to come out. i pressed the power button and it didnt turn on. i attached the charger and noticed the battery was charging but the laptop would still not turn on. i opened the back casing. and saw liquid on top of battery, cd drive and hard drive. i wiped it and dried it with a hair drier. i also dried the keyboard but it would still not turn on.
i waited a few hours and went to the apple store. The service person immediately said the engineers would have to quote me for a new logic board and top case. all he did was stare at the logic board. there was a bit of corrosion but it was like small. i did not go through with the replacements since it would cost me $1330 just replacing and no service fee yet.
i went home and took out the battery, logic board and hard drive. i was able to clean underneath the keyboard which was still a bit sticky with dog pee. i wasn't able to remove the cd drive because the screws were so tight. i the reset the SMC and PRAM. The laptop started. When i was able to see the screen where it had different options like restoring and resetting preferences and something about drives i did not know what to do so i shut it down again. i still could not use the power button so i reset the SMC again. it is the only way to turn on my laptop.The laptop opened. The fan started and the screen showed the login grey screen. I noticed the keyboard was still not working. I could not login to my Admin account because it was password protected. i logged into guest. i went to system preferences and deleted my password for Admin So i could log in to my main account. All the while i was using the on screen keyboard to type which can be opened using keyboard preferences. I realized that my laptop was okay except for the keyboard.
I was able to login to my main account. However i noticed that i could not use my Wi-Fi. It had an error that said -- Wi-Fi: No hardware installed -- i then shut down the laptop once more and disconnected the wires attached to the logic board. i reset SMC again. i logged in my main Admin Account without password and it still showed Wifi hardware not installed. I went to System Preferences and connected the ethernet cable to my laptop. I followed instructions and set up my internet using a dsl connection. i typed my username and password still didnt work i typed my IP address, Subnet mask, Router, DNS server. I got the information from my iphone 4s which was using my current wifi. it still did not work. I kept trying to connect the ethernet restarting the procedures over and over again till suddenly the wifi started working out of the blue.
I then downloaded a remote keyboard app that allows me to use my iphone as a keyboard and trackpad so that i can use my laptop. After one day i can use almost all the letters on my laptops keyboard. however i still cannot use the function keys (except volume down), number keys, delete, enter, arrow keys and most of the punctuation keys do not work. fortunately the option and command keys work i noticed that the left side which i was able to clean from underneath is functioning properly while the right side is not. i also notice that the right side which was peed on has significantly lower back lighting than the left side. im wondering if there is anything else i havent done to fix this issue. pls help and thanks in advance
i will try to open the right side part from underneath to clean it but im apprehensive as i dont want to lose the current progress i have with the laptop.

your mac is not going to get better. liquid damage usually gets worse over time.

Mid-2010 Macbook Pro 13" Sleep Problems

Recently, whenever my Macbook goes to sleep, it is unresponsive when I try to wake it up. I have to hold down the power button for a few seconds and force quit it with no indication that it is off, however, when I press the power button again, it turns on. But it doesn't turn on how it normally should. It does a double-take startup. The disk drive (or whatever it is that makes the sound at the startup) makes the sound and the screen pops up white, but after about a second, it goes out, almost as if it force quit itself, but after about another second, it turns on normally and since I put in a Samsung SSD about 3 months ago, it boots right up in a matter of seconds.
So far, this kind of stuff has been tolerable but probably not good for my computer.
But the worst case happened tonight when I put my Macbook into sleep mode. I was gone for about an hour and 20 minutes and when I got back to my computer and opened up the lid, it was pretty hot and the fans were probably running between 4000 and 5000 rpm. All this was happening when the computer was supposed to be in sleep mode and again, when I opened it up nothing appeared on the screen and it was unresponsive. This time when I force quit, I knew when it worked because I could here the fans turn off. I manually clicked Sleep this time, but I think this happened a few days ago too when I simply closed the lid to put it in sleep mode, however the computer wasn't running this hot.
I'm hoping it isn't the Logic Board and just maybe a software issue, but I have a strong feeling it isn't the software. I'm running Mavericks 10.9.5 so I'm hoping that an upgrade to Yosemite might fix it, but I doubt it.
I've already had to replace the battery, logic board, disk drive, trackpad, and I'm on my 3rd hard drive, and this computer is only 4 and a half years old. Thankfully, Apple Care covered most of the costs and basically none of the issues were due to my neglect, but it is out of warranty now. I would like to think I just got a bad computer right out of the box.

Here is the Console Log from the event I mentioned:
12/1/14 10:12:12.000 PM kernel[0]: Opened file /var/vm/sleepimage, size 1073741824, partition base 0x0, maxio 2000000 ssd 1
12/1/14 10:12:12.000 PM kernel[0]: hibernate image major 1, minor 0, blocksize 4096, pollers 5
12/1/14 10:12:12.000 PM kernel[0]: hibernate_alloc_pages act 77766, inact 63980, anon 46689, throt 0, spec 25243, wire 60358, wireinit 36014
12/1/14 10:12:12.000 PM kernel[0]: hibernate_setup(0) took 0 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_setall(preflight 0) start 0xffffff80346f1000, 0xffffff8034726000
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_setall time: 94 ms
12/1/14 11:34:34.000 PM kernel[0]: pages 271737, wire 61704, act 33386, inact 39, cleaned 0 spec 10, zf 44669, throt 0, compr 42810, xpmapped 40000
12/1/14 11:34:34.000 PM kernel[0]: could discard act 44499 inact 19273 purgeable 114 spec 25233 cleaned 0
12/1/14 11:34:34.000 PM kernel[0]: WARNING: hibernate_page_list_setall skipped 96949 xpmapped pages
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_setall found pageCount 182618
12/1/14 11:34:34.000 PM kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0
12/1/14 11:34:34.000 PM kernel[0]: IOHibernatePollerOpen(0)
12/1/14 11:34:34.000 PM kernel[0]: encryptStart 14000
12/1/14 11:34:34.000 PM kernel[0]: bitmap_size 0xe028, previewSize 0x6c8620, writing 179644 pages @ 0x6ea648
12/1/14 11:34:34.000 PM kernel[0]: booter start at 5399 ms smc 0 ms, [6, 0, 0] total 1386 ms, dsply 473, 38 ms, tramp 283 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_machine_init: state 2, image pages 60529, sum was 27699e7c, imageSize 0x18f15000, image1Size 0x6598000, conflictCount 324, nextFree 1d6
12/1/14 11:34:34.000 PM kernel[0]: hibernate_page_list_discard time: 110 ms, discarded act 44499 inact 19273 purgeable 114 spec 25233 cleaned 0
12/1/14 11:34:34.000 PM kernel[0]: hibernate_newruntime_map time: 0 ms, IOHibernatePollerOpen(), ml_get_interrupts_enabled 0
12/1/14 11:34:34.000 PM kernel[0]: IOHibernatePollerOpen(0) 23 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_machine_init reading
12/1/14 11:34:34.000 PM kernel[0]: PMStats: Hibernate read took 2563 ms
12/1/14 11:34:34.000 PM kernel[0]: hibernate_machine_init pagesDone 181443 sum2 d28892fc, time: 2563 ms, disk(0x20000) 117 Mb/s, comp bytes: 307064832 time: 398 ms 735 Mb/s, crypt bytes: 311939072 time: 1894 ms 157 Mb/s
12/1/14 11:34:34.000 PM kernel[0]: Wake reason: EHC1 OHC1 EHC2 OHC2 (User)
12/1/14 11:34:34.000 PM kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
12/1/14 11:34:34.000 PM kernel[0]: Previous Sleep Cause: 5
12/1/14 11:34:34.000 PM kernel[0]: Previous Shutdown Cause: 3
12/1/14 11:34:34.000 PM kernel[0]: NVRM: 0x702a called in D3
12/1/14 11:34:34.000 PM kernel[0]: NVRM: 0x7037 called in D3
12/1/14 11:34:34.000 PM kernel[0]: com_apple_driver_AppleUSBCardReaderUMC:: Stop::Controller Reset
12/1/14 11:34:34.000 PM kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
12/1/14 11:34:34.000 PM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
12/1/14 11:34:34.583 PM WindowServer[89]: CGXDisplayDidWakeNotification [3966319317291]: posting kCGSDisplayDidWake
12/1/14 11:34:34.604 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: Reordering authw 0x7fad0957ec70(2000) (lock state: 3)
12/1/14 11:34:34.629 PM configd[17]: network changed: v4(en1-:149.160.140.151) v6(en1:2001:18e8:2:28c2:f000::244) DNS! Proxy SMB-
12/1/14 11:34:34.631 PM configd[17]: setting hostname to "Aarons-MacBook-Pro.local"
12/1/14 11:34:34.646 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: err 0x0
12/1/14 11:34:35.000 PM kernel[0]: considerRebuildOfPrelinkedKernel prebuild rebuild has expired
12/1/14 11:34:35.000 PM kernel[0]: USBMSC Identifier (non-unique): 000000009833 0x5ac 0x8403 0x9833, 2
12/1/14 11:34:35.757 PM UserEventAgent[11]: Captive: CNPluginHandler en1: Inactive
12/1/14 11:34:35.758 PM configd[17]: network changed: v6(en1-:2001:18e8:2:28c2:f000::244) DNS- Proxy-
12/1/14 11:34:36.000 PM kernel[0]: IOBluetoothUSBDFU::probe
12/1/14 11:34:36.000 PM kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x8213 FirmwareVersion - 0x0207
12/1/14 11:34:36.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0xe400 ****
12/1/14 11:34:36.000 PM kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed -- 0xe400 ****
12/1/14 11:34:36.000 PM kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0xe400
12/1/14 11:34:36.000 PM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
12/1/14 11:34:36.000 PM kernel[0]: **** [IOBluetoothHCIController][protectedBluetoothHCIControllerTransportShowsUp] -- Connected to the transport successfully -- 0xcd40 -- 0x1800 -- 0xe400 ****
12/1/14 11:34:36.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xe400 ****
12/1/14 11:34:40.923 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:40.924 PM digest-service[414]: digest-request: init request
12/1/14 11:34:40.934 PM digest-service[414]: digest-request: init return domain: 149-160-140-151 server: AARONS-MACBOOK-PRO indomain was: <NULL>
12/1/14 11:34:41.031 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:41.031 PM digest-service[414]: digest-request: init request
12/1/14 11:34:41.035 PM digest-service[414]: digest-request: init return domain: MACBOOKPRO-EE1C server: AARONS-MACBOOK-PRO indomain was: <NULL>
12/1/14 11:34:41.172 PM eapolclient[464]: en1 STOP
12/1/14 11:34:41.749 PM Apple80211Agent[491]: [EAPOLControl.c:178] EAPOLControlAuthInfoIsValid(): Ignoring SaveCredentialsOnSuccessfulAuthentication since no credentials were specified
12/1/14 11:34:41.761 PM eapolclient[492]: en1 START uid 501 gid 20
12/1/14 11:34:41.000 PM kernel[0]: MacAuthEvent en1 Auth result for: 6c:f3:7f:bb:c0:e0 MAC AUTH succeeded
12/1/14 11:34:41.000 PM kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
12/1/14 11:34:41.000 PM kernel[0]: AirPort: Link Up on en1
12/1/14 11:34:41.000 PM kernel[0]: en1: BSSID changed to 6c:f3:7f:bb:c0:e0
12/1/14 11:34:41.979 PM eapolclient[492]: en1 PEAP: successfully authenticated
12/1/14 11:34:42.000 PM kernel[0]: AirPort: RSN handshake complete on en1
12/1/14 11:34:42.000 PM kernel[0]: flow_divert_kctl_disconnect (0): disconnecting group 1
12/1/14 11:34:43.284 PM DashboardClient[494]: 10.4-style NSNumberFormatter method called on a 10.0-style formatter, which doesn't work. Break on _NSNumberFormatter_Log_New_Methods_On_Old_Formatters to debug. This message will only be logged once.
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.333 PM WindowServer[89]: _CGXSetWindowHasKeyAppearance: Operation on a window 0x16 requiring rights kCGSWindowRightOwner by caller Dashboard
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.342 PM WindowServer[89]: _CGXSetWindowHasMainAppearance: Operation on a window 0x16 requiring rights kCGSWindowRightOwner by caller Dashboard
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tm0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TW0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tm0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TW0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:43.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b4c3000
12/1/14 11:34:46.080 PM configd[17]: network changed: DNS* Proxy
12/1/14 11:34:46.080 PM UserEventAgent[11]: Captive: [CNInfoNetworkActive:1655] en1: SSID 'IU Secure' making interface primary (cache indicates network not captive)
12/1/14 11:34:46.081 PM UserEventAgent[11]: Captive: CNPluginHandler en1: Evaluating
12/1/14 11:34:46.083 PM UserEventAgent[11]: Captive: en1: Not probing 'IU Secure' (cache indicates not captive)
12/1/14 11:34:46.084 PM UserEventAgent[11]: Captive: CNPluginHandler en1: Authenticated
12/1/14 11:34:46.090 PM configd[17]: network changed: v4(en1!:149.160.140.195) DNS+ Proxy+ SMB+
12/1/14 11:34:46.109 PM configd[17]: setting hostname to "149-160-140-195.dhcp-bl.indiana.edu"
12/1/14 11:34:47.185 PM apsd[78]: Unrecognized leaf certificate
12/1/14 11:34:50.353 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [ICS Error for file: BEGIN:VCALENDAR
VERSION:2.0
There was an extremely long list of iCal Events on here due to the entire 82 game Indiana Pacers schedule.
12/1/14 11:34:50.371 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.371 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.371 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.372 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:50.372 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Hit Max ICS log messages for file! (200)]
12/1/14 11:34:50.373 PM CalendarAgent[161]: [com.apple.calendar.store.log.ICS] [Invalid address property:CN=Pacers Schedule 2014-2015]
12/1/14 11:34:51.223 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:51.224 PM digest-service[414]: digest-request: init request
12/1/14 11:34:51.228 PM digest-service[414]: digest-request: init return domain: MACBOOKPRO-EE1C server: 149-160-140-195 indomain was: <NULL>
12/1/14 11:34:51.248 PM digest-service[414]: digest-request: uid=0
12/1/14 11:34:51.248 PM digest-service[414]: digest-request: init request
12/1/14 11:34:51.257 PM digest-service[414]: digest-request: init return domain: 149-160-140-195 server: 149-160-140-195 indomain was: <NULL>
12/1/14 11:34:51.409 PM sandboxd[268]: ([495]) netbiosd(495) deny mach-lookup com.apple.networkd
12/1/14 11:34:52.024 PM AirPlayUIAgent[230]: 2014-12-01 11:34:52.024264 PM [AirPlayUIAgent] Changed PIN pairing: no
12/1/14 11:34:52.029 PM AirPlayUIAgent[230]: 2014-12-01 11:34:52.029266 PM [AirPlayUIAgent] Changed PIN pairing: no
12/1/14 11:34:52.690 PM AddressBookSourceSync[482]: *** -[IADomainCache init]: IA domains cache couldn't be read.
12/1/14 11:34:52.691 PM AddressBookSourceSync[482]: -[IAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.
12/1/14 11:34:59.544 PM configd[17]: network changed: v4(en1:149.160.140.195) v6(en1+:2001:18e8:2:28c2:f000::244) DNS! Proxy SMB
12/1/14 11:35:05.517 PM Console[505]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
12/1/14 11:35:06.850 PM WindowServer[89]: disable_update_timeout: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
12/1/14 11:35:07.004 PM WindowServer[89]: common_reenable_update: UI updates were finally reenabled by application "Console" after 1.15 seconds (server forcibly re-enabled them after 1.00 seconds)
12/1/14 11:35:09.487 PM com.apple.SecurityServer[15]: Killing auth hosts
12/1/14 11:35:09.487 PM com.apple.SecurityServer[15]: Session 100026 destroyed
12/1/14 11:35:09.491 PM com.apple.SecurityServer[15]: Session 100027 created
12/1/14 11:35:11.470 PM netbiosd[495]: name servers down?
12/1/14 11:35:15.465 PM loginwindow[58]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

HP Envy 14 wont turn on...

Hi to everyone! Well as the subject says, i own a HP Envy 14 notebook (model XQ101AV) which after a year of normal usage ,all of a sudden stopped charging(plugged in not charging),and once the battery drained itself it wouldnt boot back on (no activity whatsoever) .
First of all i tried the usual stuff - trying replacing the battery,removing the HDD and memory modules,pressing power button for more then 15 seconds,trying different power adapter and such.
And so as i dont have warranty anymore i tried replacing the power connector cable (component nr. 608380-001 as it was most suspicious because the led wouldnt turn on -neither white nor orange)but the problem was not solved.And so i thought the worst happened and i ordered and replaced the system board (component nr. 608364-001 - for my Core i5 processor)reassembled the whole laptop but it still wouldnt turn back on.
And now before i order the third and final thing i could think of that causes the laptop not to turn on (Battery connector board ,component nr. 617265-001)i wanted to ask if anyone knows if the battery connector board powers the motherboard as it does the battery or ONLY the battery, or if you dont think that is the issue, to try and recommend any other things i could've missed. Im trying to avoid taking it for repairs as i live outside of US and i know it would be quite expensive.I am quite handy around PC repairs cause i am electronic and computers tehnician so i know i connected everything as it should be and checked everything for errors (best to my knowledge).
Sorry for a rather long post and thank you in advance :-)

Hi!
I did manage to fix my laptop. Of all the things i've tried it was the faulty battery charge board.I found a replacement one on ebay,tried to change it and it worked like a charm. I dont know if it's the same case with your latpop but if you are willing to try here's the part number : HP 617265-001 BATTERY CHARGE BOARD.
Or in case you have a different laptop model (mine was HP ENVY 14 1200-CTO, XQ101AV)refer to your service manual (find it online) and there should be a list of all parts and their numbers so use those one.
Hope you have luck in fixing it!

Battery or board?

Similar Messages

Maybe you are looking for