It all started with the vs985 stuck at lg logo. I was browsing through Facebook and then suddenly the phone rebooted. It was Warm to the touch but the 801 processor does get this warm. So I let it cool down a little bit and try to turn on the device. No hope it was stuck at lg logo no Verizon logo. So I figured that it might be at a boot loop state so I download both the .tot and the .kdz files just for the safe side. Download the correct drivers on the LG website and the correct .dll files for it I began to flash and then it failed. It gives me NULL imei and NULL pid and gives an error of model check. So I uninstalled the .tot flashtool and went on to try the kdz method. Still no hopes it just stucks at 4% and gives an usb connection error after performing the S/W Flash via kdz . Then I found a form that recommended me to download another .dll file mainly the lg8974.dll to sort of bypass an force flash it. It brings back the imei but it gives some random error at fails at 6%. I don't know what is left.
Some Questions in Mind
Q1: Am I download the wrong .dll file
Q2: Am I using the wrong method or the wrong firmware file
Q3: Am I just Dumb or don't know about this and there is already a discussion on this topic
P.s: The phone was rooted via kingroot. It was on android lollipop 5.1.1 and the files I tried were the VS98510B_03.tot and VS98512B_00.kdz
I will thank every one you can help me .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, it could be any number of things, but I'll ask this: how old is the phone? I started seeing this issue right after my phone started having problems with the SD Card slot. it was ANY SD card that would become ejected for no apparent reason and it would only remount it either after 30 minutes or so, or a reboot, but it would eventually fail again.
Then, I started getting random reboots and it would hang at the LG logo and then nothing. Screen goes dark, no lights, removing the battery didn't help, etc.
So, many have stated it could be either 1) a bad battery and a replacement will fix your issues or, 2) sadly, your phone is having hardware failures.
I'm taking mine in today to CPR+ to see if they can do a diagnostic on it and maybe they have a spare battery to see if it will work. if not, then my phone is toast. I've already replaced it, but if it was indeed the battery, it would be nice as I'll get a new battery and have the G3 as a spare. Mine was two years old and had just gone off contract when it started failing.
If you can still get into download mode, you might have a shot, but I don't know. Seeing that it just started to randomly reboot into the LG logo and hang, that is probably a sign of hardware failure like mine, especially if you can't flash any more. I couldn't either and now, it will not go into download mode nor charge. No LED lights, nothing. I doubt the battery was an issue for me, but it's worth a look since it's a free diagnostic.
iBolski said:
Well, it could be any number of things, but I'll ask this: how old is the phone? I started seeing this issue right after my phone started having problems with the SD Card slot. it was ANY SD card that would become ejected for no apparent reason and it would only remount it either after 30 minutes or so, or a reboot, but it would eventually fail again.
Then, I started getting random reboots and it would hang at the LG logo and then nothing. Screen goes dark, no lights, removing the battery didn't help, etc.
So, many have stated it could be either 1) a bad battery and a replacement will fix your issues or, 2) sadly, your phone is having hardware failures.
I'm taking mine in today to CPR+ to see if they can do a diagnostic on it and maybe they have a spare battery to see if it will work. if not, then my phone is toast. I've already replaced it, but if it was indeed the battery, it would be nice as I'll get a new battery and have the G3 as a spare. Mine was two years old and had just gone off contract when it started failing.
If you can still get into download mode, you might have a shot, but I don't know. Seeing that it just started to randomly reboot into the LG logo and hang, that is probably a sign of hardware failure like mine, especially if you can't flash any more. I couldn't either and now, it will not go into download mode nor charge. No LED lights, nothing. I doubt the battery was an issue for me, but it's worth a look since it's a free diagnostic.
Click to expand...
Click to collapse
It is about 2 year I keep my old phones with me and yes I can go to download mode but not able to flash anything
Tech core said:
It is about 2 year I keep my old phones with me and yes I can go to download mode but not able to flash anything
Click to expand...
Click to collapse
You might have to try the hard-brick recovery flash then. I can't get into download mode, or when I was able to, it would stay there for about 30 seconds and then the screen would go black. Now I can't even get it to turn on or charge.
The hard brick option, if you're not familiar with it, means you have to expose the motherboard and short two pins. Not too difficult, but can be a pain, but it's a way to flash the phone if it's in bulk mode. Doesn't sound like you are in bulk mode. Otherwise, not sure what else you can try. Hope you get it figured out.
I would say with it being 2 years old, it might be hardware failure. Right around December of this year, more and more people were reporting issues like what you see and what I see, and many turned out to be hardware failure as the devices were coming on 2 years or were over 2 years old. Wear and tear I guess. I know I constantly kept it hooked up to a power chord when playing games like Game of War so I would never lose power, and I think a lot of that caused my issues. The battery was probably on it's last leg, and I know my USB port was loose, so I had to be careful when it was hooked up to the PC or one wrong movement during a flash could cause the USB connection to be lost and then, brick! And I'd have to start over flashing a TOT or KDZ.
Not sure what your usage was of the phone, but if it was like mine (constantly charging it every day, multiple times per day), that can also cause your battery to degrade quickly and in less than two years.
I'm taking mine into Cell Phone Repair Plus today to get a diagnostic done on it, just for giggles. Hopefully, if it IS the battery, they can test it with a new battery to see if it turns on. it will probably go to the LG logo and that's it because the last time I used it was attempting to flash the 10b tot and then it turned off in the middle of the flash, so I have an incomplete flash, but I was able to get it to turn on and go into download mode, but then, it would turn off within 30 seconds to a minute. So either that is battery or it's a hardware issue (or both).
iBolski said:
You might have to try the hard-brick recovery flash then. I can't get into download mode, or when I was able to, it would stay there for about 30 seconds and then the screen would go black. Now I can't even get it to turn on or charge.
The hard brick option, if you're not familiar with it, means you have to expose the motherboard and short two pins. Not too difficult, but can be a pain, but it's a way to flash the phone if it's in bulk mode. Doesn't sound like you are in bulk mode. Otherwise, not sure what else you can try. Hope you get it figured out.
I would say with it being 2 years old, it might be hardware failure. Right around December of this year, more and more people were reporting issues like what you see and what I see, and many turned out to be hardware failure as the devices were coming on 2 years or were over 2 years old. Wear and tear I guess. I know I constantly kept it hooked up to a power chord when playing games like Game of War so I would never lose power, and I think a lot of that caused my issues. The battery was probably on it's last leg, and I know my USB port was loose, so I had to be careful when it was hooked up to the PC or one wrong movement during a flash could cause the USB connection to be lost and then, brick! And I'd have to start over flashing a TOT or KDZ.
Not sure what your usage was of the phone, but if it was like mine (constantly charging it every day, multiple times per day), that can also cause your battery to degrade quickly and in less than two years.
I'm taking mine into Cell Phone Repair Plus today to get a diagnostic done on it, just for giggles. Hopefully, if it IS the battery, they can test it with a new battery to see if it turns on. it will probably go to the LG logo and that's it because the last time I used it was attempting to flash the 10b tot and then it turned off in the middle of the flash, so I have an incomplete flash, but I was able to get it to turn on and go into download mode, but then, it would turn off within 30 seconds to a minute. So either that is battery or it's a hardware issue (or both).
Click to expand...
Click to collapse
Thank you IBOLSKI for the information you helped I did send the phone for repairs just to see if it was a hardware failure turns out it was the battery that caused this problem in the first place my phone will arrive tomorrow with the replaced battery hopefully the guys over there did the flashing and it succeeded. Thank you for all the support you gave me .
Tech core said:
Thank you IBOLSKI for the information you helped I did send the phone for repairs just to see if it was a hardware failure turns out it was the battery that caused this problem in the first place my phone will arrive tomorrow with the replaced battery hopefully the guys over there did the flashing and it succeeded. Thank you for all the support you gave me .
Click to expand...
Click to collapse
Well, that gives me SOME hope. I was about ready to say forget it, but now I'm definitely going to take it into CPR+ and see if they have an extra battery to test it out and see if it turns on. If that IS the case, I'll have a nice spare in case something happens with my S7.
Related
This may or may not work for most but this worked heavily for my 2 units that had the same issue. One with a broken nvflash, the other that faced a bootloop and never booted up again. Took almost a week and I felt almost all hope was gone because the bloody service centre's refused to accept the unit's as they were not purchased from the region, rather online. Scumbag Samsung .
[!] This is usually a 90% fix for both broken nvflashes/deep sleep of death, considering you haven't drowned your Tab by now with no hope . I ask that you kindly attempt this once if you haven't before you QQ to the nearest Samsung center like I did.
- Drain your tablet
And by all mean's do so, The quickest way to get this done in less than 2 days or so (Depending on the battery percent charged) is to get a clear tape and tape around the power button pressed.
- Testing if you have drained it completely/Taped it right.
Connect the tablet via USB to your PC, make sure you have the NV Driver files [http://forum.xda-developers.com/showthread.php?t=1130574]
Just install the driver and proceed to the step where it asks about holding down the [Power button] +[ Volume+] and wait for the constant USB connect/disconnect sounds. It also helps to look at Device Manager to see if it still pops up.
When the battery is completely drained it will stop popping up in the device manager, and your ready to go.
MOST IMPORTANT STEP
You have only 1 and only 1 chance per drain to get this done right. Plug it into the socket charger and see if the charging icon should come up, after being fully drained you should see the charge icon should pop up [100% tested and works, this step is annoying but it's the tablet version of taking out the battery and popping it back in] and what ever you do, DON'T BOOT IT UP NORMALLY, instead press [Power Button] + [Volume -] keys and let go when you see the logo to get into fastboot mode.
Select the android buddy with the [Volume +] key and it will boot into Download Mode.
From here on out everything is easy sailing. Get the right firmware and Odin and flash the firmware you require. It doesn't matter what region you are from, the tablet is made to accept any regional firmware BUT the model number should be the same. Which mean's 7500 for 7500 ONLY.
Edit: Since you have only one chance per drain, I suggest you flash a stock firmware rather than flashing CWM to save it, Because CWM would only fix the recovery, It wouldn't fix the damaged bln. The fastest way to get a stock firmware is grabbing the stock firmware from the Overcome thread
Will taking the battery out work ? or do i have to drain the battery then turn it on ?
and for the duct tape, only power button ? because my computer won't recognise my tablet unless i use the APX mode which is (Power + Volume up), in that case i guess i have to table both power and vol down ??
There's no way to remove the battery since it's like hardbound inside. Drain it to turn it on sir.
Yeah you should get it plugged via APX mode. Press it for 15 secs both then connect it via USB, After that you can hold it down via tape, the power button only.
Maraming salamat po!!!!!!!!!!!!!!!!
(Thank you very much)
I have tried so many ways....but this may actually works..
So did you get it working? If it did I'm glad for you
tried it for the first time, didn't work and i'm giving it another try. I taped the power button to drain the battery completely, i'm gonna leave it for another day. Then tape both (power and vol +) and plug into the computer until it stops popping up ? then plug it into the socket to see if the charging icon show up ?
am i doing it right ?
my tablet is a galaxy 10.1V
Nono, Just the power button to clear the power cycle, No need to tape the volume button, Once it's in the APX mode, you just need to hold down power button and it will keep looping. when it stops appearing in device manager, It's completely drained. Actually, once it's completely drained, you need to plug it via socket charger to see if the charge icon shows up :] Then you're ready for Odin :]
Thanks so much for the helpful post, and detailed instructions.
I've drained my battery, 100% - confirmed by connecting to PC, not detected. Plugged it into wall charger, got the 'battery charging' indicator.
From there, I boot into Download mode, and fire up Odin. The device is detected on an appropriate COM port, and I can push a CWM or stock recovery image, and get a big green PASS. (usually - I've performed these steps several times, and occasionally it Odin will hang)
And yet - the device will never boot to completion, nor can I get into recovery mode.
I'm confident an underlying problem is that the device was (IS) encrypted - which is confirmed when rebooting normally: I get the pre-boot authentication page prompting for (and confirming) the passphrase - and then the android / gear outline, then... black screen. Nothing.
When attempting to select recovery mode - same thing: screen goes black, and nothing (same results whether stock or CWM recovery flashed).
Thanks again for the information - I'll keep reading, and testing - and appreciate any insight anyone may have.
SnoWake4Me said:
Thanks so much for the helpful post, and detailed instructions.
I've drained my battery, 100% - confirmed by connecting to PC, not detected. Plugged it into wall charger, got the 'battery charging' indicator.
From there, I boot into Download mode, and fire up Odin. The device is detected on an appropriate COM port, and I can push a CWM or stock recovery image, and get a big green PASS. (usually - I've performed these steps several times, and occasionally it Odin will hang)
And yet - the device will never boot to completion, nor can I get into recovery mode.
I'm confident an underlying problem is that the device was (IS) encrypted - which is confirmed when rebooting normally: I get the pre-boot authentication page prompting for (and confirming) the passphrase - and then the android / gear outline, then... black screen. Nothing.
When attempting to select recovery mode - same thing: screen goes black, and nothing (same results whether stock or CWM recovery flashed).
Thanks again for the information - I'll keep reading, and testing - and appreciate any insight anyone may have.
Click to expand...
Click to collapse
Actually this is what I mentioned earlier, The problem is you have one chance per drain and you used that to flash CWM If I were you, I would suggest flashing a firmware, Probably 3.2 HC EU/US firmware of your choice. Then when you get it to boot (You should feel that slight vibration when you boot it up) after it works, you need to shut it down properly and flash the CWM.
I made the same mistake Cost me again another 8 hrs, Just for 5mins charging. FML.
However i have updated the OP with a slight "Edit" note
On another note, Updated the OP
i have tried 3 times already, didn't work ... what kind of tablet you tested the on ? mine in galaxy 10.1v.
what i did is .. i taped the power button for about 2 days, then when i plug it into the computer i can see it popping repeatedly and it won't stop because as far as i know its actually charging from my computer ..
i have actullly disassembled it and took the battery out .. but i just turned it on normally and same thing (black screen) , according to you i should not turn it on just like that .. however i should power it into recovery mod.
my question are: is taking the battery out as same as draining the battery ?
because i still couldn't figure out how to drain the battery and test that at the same time
thanks in advance, and i'm just trying to give it coupe of tries before i lose hope
zBarry said:
i have tried 3 times already, didn't work ... what kind of tablet you tested the on ? mine in galaxy 10.1v.
what i did is .. i taped the power button for about 2 days, then when i plug it into the computer i can see it popping repeatedly and it won't stop because as far as i know its actually charging from my computer ..
i have actullly disassembled it and took the battery out .. but i just turned it on normally and same thing (black screen) , according to you i should not turn it on just like that .. however i should power it into recovery mod.
my question are: is taking the battery out as same as draining the battery ?
because i still couldn't figure out how to drain the battery and test that at the same time
thanks in advance, and i'm just trying to give it coupe of tries before i lose hope
Click to expand...
Click to collapse
Actually yes taking the battery out is the same as draining it because in truth the tablet isn't like a phone where you can pop out the battery, You can however remove it since you have disassembled it already. Instead of draining it, Try Power and Vol Down directly after popping the battery back in. Once you get into fastboot mode you need to flash the firmware via Odin. I wouldn't lose hope if I were you :] I had the same issue, Then I fixed mine.
Yeah one was the 10.1v and the 10.1 both were fixed the same method.
This however shall give you hope :] Once bricked for a week, Now alive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my Galaxy Tab 10.1 was bricked second time in one month, this really is a annoying issue, unfortunately samsung doesn't provide warranty in my country, not uptill now. First time I had to give it to the market for repair, the person charged me around $50 for the repair and did that in one week. The symptom were the same, I turned it off and it never came back online.
Second time, i had no choice but to dive into the issue and solve it myself, as it was totally insane to pay this much for every time my tab throws tantrum at me.
This time I discharged it fully, as you told, and tried to check it by plugging it into the system, but every time it appeared as APX device, so out of frustration I just plugged it in to the socket, and voila the battery icon appeard, i let it charge for sometime, pull out the charger and boot it normally by pressing the power button, and guess what it was back online, with all the data and everything. I had a hunch that it would turn on as, the first time, when sent to market, sharing my lattitude with my dad i was appearing at the shop location, meaning it worked there, that stupid opportunist simply wiped it and charged me $50. But now i know how to save that money
PS: I was able to identify the cause of the issue, atleast what happened with me was that i powered off the tab while plugged into socket both of the time, it never came back. Something you might avoid for this problem to occur.
atif.sami said:
my Galaxy Tab 10.1 was bricked second time in one month, this really is a annoying issue, unfortunately samsung doesn't provide warranty in my country, not uptill now. First time I had to give it to the market for repair, the person charged me around $50 for the repair and did that in one week. The symptom were the same, I turned it off and it never came back online.
Second time, i had no choice but to dive into the issue and solve it myself, as it was totally insane to pay this much for every time my tab throws tantrum at me.
This time I discharged it fully, as you told, and tried to check it by plugging it into the system, but every time it appeared as APX device, so out of frustration I just plugged it in to the socket, and voila the battery icon appeard, i let it charge for sometime, pull out the charger and boot it normally by pressing the power button, and guess what it was back online, with all the data and everything. I had a hunch that it would turn on as, the first time, when sent to market, sharing my lattitude with my dad i was appearing at the shop location, meaning it worked there, that stupid opportunist simply wiped it and charged me $50. But now i know how to save that money
PS: I was able to identify the cause of the issue, atleast what happened with me was that i powered off the tab while plugged into socket both of the time, it never came back. Something you might avoid for this problem to occur.
Click to expand...
Click to collapse
For some odd reason it happens different for most tabs, I don't know if this is Samsung's first dedicated tablet apart from the 7" that was a huge wafer or a loaf of bread But as far as I know that was just an oversized phone without much tablet dedication compared to this. In my case dad had turned off the tablet while it was on a bootloop and it never turned on again, that is until I tried out the above method and it worked, So far so good I'm on the CM9 Kang and no issues so far. Thank tablet God.
i've used a terminal app to force my 10.1 p7510 to charge when plugged in into the usb.. now i'm also thinking that it might be charging even while it's on DSOD or bricked.. : /
i guess to avoid getting bricked is to never turn it off.. sigh.. just keep on killing apps, clearing memory, etc..
i'm still hoping and waiting for it to be drained.. tried plugging it in for about 3 seconds to check if the battery icon would pop-up nothing.. so back to plugging it into my pc and taping the power button in..
Quick Update:
the tape keeps on loosening (don't want to stick it too much over the screen since it might pull off the matte screen protector) so i took 2 rubber bands and affixed it to my tablet.. made sure it was tight enough to pull down/in the power button ^^
Eiranova said:
i've used a terminal app to force my 10.1 p7510 to charge when plugged in into the usb.. now i'm also thinking that it might be charging even while it's on DSOD or bricked.. : /
i guess to avoid getting bricked is to never turn it off.. sigh.. just keep on killing apps, clearing memory, etc..
i'm still hoping and waiting for it to be drained.. tried plugging it in for about 3 seconds to check if the battery icon would pop-up nothing.. so back to plugging it into my pc and taping the power button in..
Quick Update:
the tape keeps on loosening (don't want to stick it too much over the screen since it might pull off the matte screen protector) so i took 2 rubber bands and affixed it to my tablet.. made sure it was tight enough to pull down/in the power button ^^
Click to expand...
Click to collapse
I just happened to use one of those 3M Scotch tape I had lying around in the house, was pretty good and didn't leave any tape marks on the device. Yeah offline charging apparently is a bad thing for the tablet which is why I never chose to keep/enable it despite it was already there via Overcome ROM. Easiest way to drain it is by holding the power button down, best be unplugged and leave it to drain that's the only way you'll know it doesn't get charged, should take a max about a day or more depending on the % of charge it has.
One thing I found out was, You can never really brick the tablet completely, Unless ofcourse you flashed some other device's firmware on it. I do hope the ICS official release has some sort of fix to this, rather than the boring immense hours you would have to wait or pay just to get it fixed.
I do however wonder how many have gotten their tablets fixed via this method..
well you know what? i've just arrived from work and i turn on the speaker of my pc and it's still doing the badump-badump sound.. so now i'm guessing it's looping the on and off thing as well as the usb charging feature.. so now i'm gonna leave it again for day UNPLUGGED from my pc and hopefully tomorrow night it'll be all ready for reflashing.. sigh..
Eiranova said:
well you know what? i've just arrived from work and i turn on the speaker of my pc and it's still doing the badump-badump sound.. so now i'm guessing it's looping the on and off thing as well as the usb charging feature.. so now i'm gonna leave it again for day UNPLUGGED from my pc and hopefully tomorrow night it'll be all ready for reflashing.. sigh..
Click to expand...
Click to collapse
Yeah don't worry so much about it, You'll know if you did it right when you plug it into the socket and you see the battery charge icon, That's a sign that's it's completely drained and recharging from scratch Remember to flash a stock firmware first as that fixes the broken bootloader. Recovery module won't do much.
Do keep me updated
argh got home and it's still not drained : /
Eiranova said:
argh got home and it's still not drained : /
Click to expand...
Click to collapse
A fully charged one takes about a week to drain, according to one of the member
Hi Gang,
Posted a few days ago about this issue I am having. During the last firmware update my Prime stopped working. It showed the android avatar doing the update and then it just went black (screen). I waited about 2 hrs and left it alone incase it was just taking a long time to reboot, but it has never turned back on.
If i hold the power button for 8-10 seconds it will vibrate like it normally does when you turn it on but thats about all. I have tried every combination of volume key and power button, reset pin ect. I have downloaded the update alone and put it to my micro sd card in hopes that it may catch it, but no luck. The power LED will only light up when plugged in and not on its own power. I have left it off charge for almost 2 days and it still seems to have power and not draining on its own.
There is 0 screen or volume..just black dead screen and vibration from holding power button 8-10 seconds.
When i plug it onto my pc it says ATX device and then fails to recognize it.
Anyone have any other ideas..at this point I am willing to open it up and reset the chip if possible or any other circuitry in hopes of rebirth.
I loved the prime..and so regret updating it.
I appreciate any suggestions and thanks.
Did you make sure the update zip was on the root of the SD Card? Did you properly put it in the mode to point it to that update zip then flash it?
Did you let battery drain completely then charge it up again? Usually those things will fix issue you described.
demandarin said:
Did you make sure the update zip was on the root of the SD Card? Did you properly put it in the mode to point it to that update zip then flash it?
Did you let battery drain completely then charge it up again? Usually those things will fix issue you described.
Click to expand...
Click to collapse
What would be the best way to type the address line on the micro sd card so it shows the correct path? I show no specific folder listed on my micro sd as /removeable (ect ect). What would be the proper folder name to make so it shows the path?
And i have 0 screen showing on my prime, so how do I put it the correct mode?
I have been letting it drain for 2 days now on its own, but it will take some time because there is no actual process running on it, it just appears to turn off.
I appreciate your help..in so many ways
This exact thing happened to me yesterday. And I just got my Prime...yesterday. I got to use it for about an hour before it asked to update. Frustrating. I have been digging around on the net but nothing is helping yet.
It was about 85% power or so when it started updating, so by the time the battery drained to zero I could have shipped it off to ASUS for repair and maybe it would even be on it's way back....
One interesting little thing, when i plug it into my computer windows detects it as an APX device even though the tablet is "off" (the power light isn't/screen is not on at least.) I installed the APX drivers and it's recognized as a Transformer Prime but I can't issue any ADB commands or anything.
I've tried like every button combination i can think of, the little reset thingiem and nothing makes it wake up. All I can make it do is that vibrating thing. Not a very fun start with this device, although while it was running it seemed to run really, really smooth.
Coaster, paper-weight......
..... sorry I'm in a stupid mood.
Let the flames begin.
Doktaphex said:
Coaster, paper-weight......
..... sorry I'm in a stupid mood.
Let the flames begin.
Click to expand...
Click to collapse
Well at least it vibrates, not bad for a paperweight! I suppose I'll just have to send it off for repair or something on Monday, I don't think it will be waking up anytime soon :-[
_____
Not sent from my Vibrating Transformer Prime using Tapatalk
vt220 said:
Well at least it vibrates, not bad for a paperweight! I suppose I'll just have to send it off for repair or something on Monday, I don't think it will be waking up anytime soon :-[
_____
Not sent from my Vibrating Transformer Prime using Tapatalk
Click to expand...
Click to collapse
I'm confused, if you only just got it, then the seller has to replace it, not the manufacturer and I don't care where in the world you are. That should be standard. practically DOA, no real issue unless the seller is a shyster.
Doktaphex said:
I'm confused, if you only just got it, then the seller has to replace it, not the manufacturer and I don't care where in the world you are. That should be standard. practically DOA, no real issue unless the seller is a shyster.
Click to expand...
Click to collapse
I suppose, I just don't when the place will have more in stock. I got it online from Gamestop and it's the first time I ever shopped with them, but I'd guess I could just get refunded and keep looking around.
Sixfeet01 said:
Hi Gang,
Posted a few days ago about this issue I am having. During the last firmware update my Prime stopped working. It showed the android avatar doing the update and then it just went black (screen). I waited about 2 hrs and left it alone incase it was just taking a long time to reboot, but it has never turned back on.
If i hold the power button for 8-10 seconds it will vibrate like it normally does when you turn it on but thats about all. I have tried every combination of volume key and power button, reset pin ect. I have downloaded the update alone and put it to my micro sd card in hopes that it may catch it, but no luck. The power LED will only light up when plugged in and not on its own power. I have left it off charge for almost 2 days and it still seems to have power and not draining on its own.
There is 0 screen or volume..just black dead screen and vibration from holding power button 8-10 seconds.
When i plug it onto my pc it says ATX device and then fails to recognize it.
Anyone have any other ideas..at this point I am willing to open it up and reset the chip if possible or any other circuitry in hopes of rebirth.
I loved the prime..and so regret updating it.
I appreciate any suggestions and thanks.
Click to expand...
Click to collapse
I have exactly the same problem as you. Did exactly samething you did. Still no solution. Let me know if you find a solution for it. I'll do the same for you. I have send a message to Gary from Asus. Maybe, you shall send one as well that I am not the only one with this problem.
I will keep looking for solutions, trying to figure a way to have it recognized as a storage device on my pc, right now it just lists as a Android phone and I am not able to expore within it.
What is gary's pm ? I will send him some info also.
Cheers
So you never see the ASUS logo ?
Try holding the power and Vol Down buttons for a good 30 seconds, see if you can get the recovery mode up.
If the PC see's it as an APX device its still on, and i'm guessing its in a suspended mode, perhaps used by the factory etc ... ?
Nope, never see Asus logo..screen is off..no backlight and no volume. Have tried every power button / volume configuration concieveable to no avail. But i did manage to get it to show up in device manager under phone, i would like to know how to get it to be listed as storage device.
It has been off charge for 3 days now and still vibrates on power button, because it would seem there is no process running, the battery is just draining from shelf time which could take a very long time to completely drain.
I saw a thread that mentions a reset button on the left of the device, under the microSD port ... i thought it was a microphone, but apparently thats on the top
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You could try sticking a paper clip in that hole ... hey it'll be going back anyway so dont worry
P.s. mic at the top
At this point I'm doubting there's an answer other than return or warranty. Mines going back tomorrow :-\
Not sent from my Periodically Vibrating Non-starting Transformer Prime using Tapatalk
I have exact same problem. Bought mine today. linked up wifi and entered initial data. It asked me to update and same stuff happened.
-Little android guy and gears came up. progress bar after that then turned off never to start up again. World's most expensive push button vibrator.
What a joke! A very expensive joke.
Maybe my battery will drain in a month or so so i can try the update again and go through the misery one more time.
And yes i have tried all the suggested remedies with no luck of course.
WoW... I guess I maybe got lucky for once???
I got my Prime in the mail yesterday. I ordered after seeing several reviews and videos on its performance and even finding a display in a local store. Then after ordering I start finding all these threads on lockups; WiFi and GPS issues and frankly I get worried I just made a terrrible purchase decision.
Yet; my Prime seems to be working fine. I have a 'minor' issue with scrolling and it not being as smooth as reviews and/or displays I checked out; but the WiFi and GPS are working and even after the system update to ICS - no issues.
I did read on another forum however about the hard reset fixing this type of issue. With power off hold Vol-Down and Pwr keys until some text appears on the top of the screen. Takes about 30seconds. Then let go of everything and let it boot on its own.
Give it a try! What's it gonna hurt?
Quote from AC5FF
I did read on another forum however about the hard reset fixing this type of issue. With power off hold Vol-Down and Pwr keys until some text appears on the top of the screen. Takes about 30seconds. Then let go of everything and let it boot on its own.
Click to expand...
Click to collapse
Been there. Done that. I have tried every suggested remedy noted on various forums. The only one left was let the battery drain to Zero which might take a very long time since under normal use the battery will last 6 to 8 hours. There is no way to drain the battery down when it won't turn on. (other than to sit there and press down the power on/off key until it vibrates. Gee I wonder how many vibrations I would have to go through to kill the battery)
Mine is trying to install the same update. Just to throw a question out there, the people that have the bricked primes what are the first 2 digits of the serial number? If anyone has applied the update and it worked what is the first 2 of your serial number. My first prime with a B1 serial number bricked on the first update to ICS. The one that I have now has a C1 serial and has worked awesome before and after the update.
dmartin774 said:
Mine is trying to install the same update. Just to throw a question out there, the people that have the bricked primes what are the first 2 digits of the serial number? If anyone has applied the update and it worked what is the first 2 of your serial number. My first prime with a B1 serial number bricked on the first update to ICS. The one that I have now has a C1 serial and has worked awesome before and after the update.
Click to expand...
Click to collapse
Bricked here - BC0K
Bricked here. Serial number is c10kas022.....
So, let me start
Few weeks ago my phone hard-bricked when i was trying my softbricked (Rom manager fault) O1 unbrick with KDZ. But it is just the start. So my phone was left at service to unbrick it for almost two weeks. When i got my phone , it was running some 2.2 official ROM, but it was strange, filled up with russian applications and widgets. I didn't liked that, so i updated my optimus to 2.3.x (The newest version, but don't remember which) to have the new baseband. Then with super one click rooted, and through terminal i installed CWM (5.0.2.0). Then flashed the newest oxygen. My phone was very unstable. It was just shutting down for no reason, restarting, (and i also got two times kernel panic, when it was clocked just to 748mHz) especially when i was using it. Also battery lasted not long, so i wiped batery stats, but it not helped. So i decided to flash new ROM. I fully wiped everything, and flashed PerfectPeso 2.2. Then flashed fixed scripts, GAPPS, New kernel. IT was also VERY unstable, so i thought old version PerfectPeso is not compatible with new kernel (PP.kernel v1.7), so again i wiped everything and flashed PP 2.3, then GAPPS, new Kernel, Fixed scripts. It was still not stable as it should be.. In the morning phone was just turned off, so i turned it on. In battery stats there were strange things: battery just came down 10 percents as i turned it on, and also it doesn't showed it was turned off at night not all. Phone was connected to charger all night. In a day it was just keeping shutting down, but just then, when the screen was turned on. After that, when i came home, it just turned off, and not turned on, even no LG logo when trying to turn it on (It turned off in my hands, when 20% batt were left). So i just kept trying to turn it on, by removing batt, reconnecting the charger. AND IT TRUNED ON !! but after few moments it went down again. I started trying again to turned it on, it turned on again, just in few attempt's. My phone was showing that 23 percents still were left... So i fully charged it, when i did that i tried to calibrate battery, like the manual said (i typed in su, then calibrate into terminal) but calibrator said i have to turn my phone off, and when it boots, i have to remove batt, and then put it in. I did it few times (with the calibrator help). I thought everything is fine. (But i wanted more performance, so i made EXT2 in my SD, then tried to enable ungaze a2sd by typying into terminal A2SD, but nothing hapened. Then, i tried To ZIPALIGN all APK's Manually, by commands: "su", and then "zpall". The command did something, no errors. Then i wanted to get rid of boot logo by trettet, because it not looked very good, so i went to Settings and disabled my bootlogo. Then i just started playing gta III (now phone was only on default cpu clock speed, because i disabled overclocking on boot, and turned it on when i needed it). Then I pressed home key, opened Dolphin browser, and my phone went down (as usual). Then tried to turn it on, but no signs of life, i did it for over 20 times, but still no luck from yesterday. Can anyone help me to solve this ?
Also, i don't think it is fully bricked, because when i connecting the charger to my phone, phone battery pins gives me around 2.35 V (but when it was full bricked few weeks ago, it gave me no voltage)
Thank you
p.s. sorry for my terrible English
ahaha yes very funny (sarcasm) -.-
Cool story bro..
Can anyone test full-bricked device, what voltage comes to battery pins, when phone is plugged to charger ?
Thanks for the changed name )
ashirviskas said:
Can anyone test full-bricked device, what voltage comes to battery pins, when phone is plugged to charger ?
Thanks for the changed name )
Click to expand...
Click to collapse
Charger should have 3.7V my uncle is good at this stuff and I needed a charger from him... found out Blackberry and Nokia have 5V
If you find "FP" in the above post, this is for you:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seek the signature below the line
vlt96 said:
Charger should have 3.7V my uncle is good at this stuff and I needed a charger from him... found out Blackberry and Nokia have 5V
If you find "FP" in the above post, this is for you:
Seek the signature below the line
Click to expand...
Click to collapse
xDDDDD
I just wanted to know what voltages comes to the battery, (or should come if it is not removed) in the phone ;DD
Anyways, thanks for making me happier )
But i still need to know, how to test if my phone is really bricked :/. I know, it sounds a little bit strange, but i can't explain everything in English because of the lack of knowledge of English words ;DD
ashirviskas said:
xDDDDD
I just wanted to know what voltages comes to the battery, (or should come if it is not removed) in the phone ;DD
Anyways, thanks for making me happier )
But i still need to know, how to test if my phone is really bricked :/. I know, it sounds a little bit strange, but i can't explain everything in English because of the lack of knowledge of English words ;DD
Click to expand...
Click to collapse
Well, the signature isn't for you
Your phone is bricked if it won't start and kdz won't work
If you find "Facepalm" in the above post, this is for you:
Seek the signature below the line
vlt96 said:
Well, the signature isn't for you
Your phone is bricked if it won't start and kdz won't work
If you find "Facepalm" in the above post, this is for you:
Seek the signature below the line
Click to expand...
Click to collapse
Then how another time it didn't show any logo, but after trying it booted up. Also how it could brick, only by opening browser ? (then my phone went down and won't turn on)
ashirviskas said:
Then how another time it didn't show any logo, but after trying it booted up. Also how it could brick, only by opening browser ? (then my phone went down and won't turn on)
Click to expand...
Click to collapse
Well, you can have hard brick or soft brick...
If it has a hardware brick, it is unknown how will it react, best to go to a service...
If it is software brick, try flash stock GB with kdz... if not then it is bricked, go to a service center...
If you find "Facepalm" in the above post, this is for you:
Seek the signature below the line
vlt96 said:
Well, you can have hard brick or soft brick...
If it has a hardware brick, it is unknown how will it react, best to go to a service...
If it is software brick, try flash stock GB with kdz... if not then it is bricked, go to a service center...
Click to expand...
Click to collapse
I know. And also, today i thought that i could try to trun it on, so i took the phone, tried to turn on, but nothing. Then I took the battery out, shaked my phone and "Clapped" it into my leg, inserted the battery, pressed on button and.. the phone showed LG logo !!!
Then it went down, then I plugged in the charger. It charged a for few min. Then i powered on my phone, it turned on succesfully, so i just layed the phone on the table, to charge (It was 4% at the time). After few mi. i took the phone and it was turned off. I tried to turn it on, but no signs of life. So again, my phone is "dead". It is no truning on anymore, and shaking, pulling batt out doesn't seem to help. What should i do ?
uh~`I want to be a romer
peter joe said:
uh~`I want to be a romer
Click to expand...
Click to collapse
?
so, another thing: The phone in yesterday evening started working normally (Exept few turn-offs), i left it charging till this morning. In morning phone was not active, i turned it on by reinserting batt, but phone showed just 75% batt left, even if it was plugged in whole night. Can anyone help me to remove all this sh*t ?
Also I tried few ROMs, but same. Maybe KDZ would help me if it is baseband problem ?
Or maybe it is hardware problem ?
I would be very happy if someone could help me with this
(last time KDZ bricked my phone, so i don't want to use it anymore)
ashirviskas said:
?
so, another thing: The phone in yesterday evening started working normally (Exept few turn-offs), i left it charging till this morning. In morning phone was not active, i turned it on by reinserting batt, but phone showed just 75% batt left, even if it was plugged in whole night. Can anyone help me to remove all this sh*t ?
Also I tried few ROMs, but same. Maybe KDZ would help me if it is baseband problem ?
Or maybe it is hardware problem ?
I would be very happy if someone could help me with this
(last time KDZ bricked my phone, so i don't want to use it anymore)
Click to expand...
Click to collapse
Also it is happening only with sim, never experienced it without sim somehow...
I install a wifi kill app.
It was apparently shutting down wifi? What wifi I have no idea. It was stuck and non responsive for around 4/5 minutes so I thought a battery pull and a restart would get me out of the app.
And now the phone will not respond to me pressing the power button?! Nor will it charge. It's not responsive to being plugged in.
Help...
First time anything like this has happened to me. I am stuck without a phone and worried. Any help is appreciated?! I best not have screwed up the device.
Its a GSM evo, had a high battery charge. Running a custom rom with s off.
Even plugging it in gives no response. :crying:
It has been charged all night. seemed to indicate it was full. This morning it was down to 80% and I left it on charge some more, now this.
I opened up my comand prompt then typed "fastboot reboot-bootloader" and I just get < waiting for device >
I've been through this thread and non of this helps. (link below)
=/
-------------------------------------------
My solution.
Button presses were having no effect I left my phone connected to the mains and re tried the buttons and adb commands with no luck.
Although my battery was reading at around or above 80% before the problems I was sure it wasn't the battery.
I couldn't see how it was appearing to be bricked and unresponsive. I installed an app, it hung and I pulled the battery. So I presumed something had gone wrong with the app.....
I took a chance that the battery had drained fully somehow and the ROM was somehow supplying some dodgy readings.
The battery and wire trick was what I tried. A jump start was needed.
I should have licked the battery first to feel for any charge. But it was the last thing I was thinking about. (I don't have a voltage tester any more around the house)
I set off for a 9 volt battery. Using my trusty tongue again the one in my alarm was out of juice. Thankfully I got a new one though which was laying around.
So if it wasn't going to work I knew this battery wasn't going to be part of a problem.
Striping metal food ties I connected positive to the one positive contact and used another metal strip to tap each of the three negatives, obviously connected to the negative of the battery.
I kept the touches quick barely a second and kept running through all three. Went well, there was no heat from the battery. I did that for about a minute.
Be careful, don't damage your battery! Do not blame anyone else if you do... Make sure not to have your connections touch one another or its game over too.
I used my trusty method of licking the phone battery and bam, it was charged and I knew about it!
Placed it into the phone. Took a bit of time to say my prayers.... Connected the USB and the computer acknowledged that it was working a red light flashed,
My prayers were answered! I powered on the phone and its back to normal.
Strangely telling me the battery is at around 75% plus ...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didn't have a wall charger or a spare battery as you can tell. I got there in the end.
Have you tried booting into recovery?
Try pulling the battery for a few. Then press and hold the camera button and click power on. No idea where i remember this from but it may work.
spirithandler said:
Have you tried booting into recovery?
Click to expand...
Click to collapse
It is not responsive. It wont boot let alone bootloader.
NineInchNails said:
Try pulling the battery for a few. Then press and hold the camera button and click power on. No idea where i remember this from but it may work.
Click to expand...
Click to collapse
Tried this too. Even with volume combinations as suggested in other threads I have looked up. My battery appeared to be charged to at least 80%. I'm hoping its something that hasn't bricked my phone and there is a simple fix. Maybe the battery level has been wrong?
I've left it on charge for now and I will give the buttons another go. At the minute it doesn't appear to be charging.
Can the battery pull cause any damage?
*Anyone else having trouble check this thread ..
http://forum.xda-developers.com/showthread.php?t=1408374 I've tried all these tips here and non are working for me so far. They keep mentioning cwm 5 may cause problems ? I think I was running it because when I s-offed it came with it. Not sure which version it was?
The battery pull wont do any damage but this doesnt sound too good. If you cant boot to recovery or the bootloader your pretty much screwed.
Does the led light up when you charge it? If so it may not be completely bricked. But we need to see if you can power it up at all.
NineInchNails said:
The battery pull wont do any damage but this doesnt sound too good. If you cant boot to recovery or the bootloader your pretty much screwed.
Does the led light up when you charge it? If so it may not be completely bricked. But we need to see if you can power it up at all.
Click to expand...
Click to collapse
No, no light so I was worried. Good news is it's not bricked. I have another problem though.... I will post back in a minute, I will post the fix that worked for me to the top of the thread.
My battery seems to indicate it has charge that's what it appears to be reading at once I booted the phone up I took that picture. But it indicates its been on a while? ? ?
And now ky battery is draining like crazy. Is it just a bad battery? Or one that needs calibration?
Seems strange as only people with a low battery come across this problem. What could have caused it. I'd rather not have it happen again.
Any clues?
Oh wow! Awesome man. My next round of questions were going to be if you had access to a different battery or a friends phone to test it before we claimed it as a brick. Huge props for going above and beyond. Now stay away from the app that caused it but it also couldve been the battery failing and its coincedence.
Was gonna order a wall charger and a spare battery. But would have had to wait until Tuesday with shipping.
Battery level seems a bit all over the place. Why is there a second gap ?
Sent from my HTC EVO 3D X515m using xda premium
Pauly_k said:
I install a wifi kill app.
It was apparently shutting down wifi? What wifi I have no idea. It was stuck and non responsive for around 4/5 minutes so I thought a battery pull and a restart would get me out of the app.
And now the phone will not respond to me pressing the power button?! Nor will it charge. It's not responsive to being plugged in.
Help...
First time anything like this has happened to me. I am stuck without a phone and worried. Any help is appreciated?! I best not have screwed up the device.
Its a GSM evo, had a high battery charge. Running a custom rom with s off.
Even plugging it in gives no response. :crying:
It has been charged all night. seemed to indicate it was full. This morning it was down to 80% and I left it on charge some more, now this.
I opened up my comand prompt then typed "fastboot reboot-bootloader" and I just get < waiting for device >
I've been through this thread and non of this helps. (link below)
=/
-------------------------------------------
My solution. Button presses were having no effect I left my phone connected to the mains and re tried the buttons and adb commands with no luck. Although my battery was reading at around or above 80% before the problems I was sure it wasn't the battery. I couldn't see how it was appearing to be bricked and unresponsive. I installed an app, it hung and I pulled the battery. So I presumed something had gone wrong with the app.....
I took a chance that the battery had drained fully somehow and the ROM was somehow supplying some dodgy readings.
The battery and wire trick was what I tried. I jump start was needed.
I should have licked the battery first to feel for any charge. But it was the last thing I was thinking about. (I don't have a voltage tester any more around the house)
I set off for a 9 volt battery. Using my trusty tongue again the one in my alarm was out of juice. Thankfully I got a new one though which was laying around.
So if it wasn't going to work I knew this battery wasn't going to be part of a problem.
Striping metal food ties I connected positive to the one positive contact and used another metal strip to tap each of the three negatives, obviously connected to the negative of the battery. I kept the touches quick barely a second and kept running through all three. Went well, there was no heat from the battery. I did that for about a minute.
Be careful, don't damage your battery! Do not blame anyone else if you do... Make sure not to have your connections touch one another or its game over too.
I used my trusty method of licking the phone battery and bam, it was charged and I knew about it!
Placed it into the phone. Took a bit of time to say my prayers.... Connected the USB and the computer acknowledged that it was working a red light flashed. I powered on the phone and its back to normal. Strangely telling me its at around 75% plus ...
I didn't have a wall charger or a spare battery as you can tell. I got there in the end.
Click to expand...
Click to collapse
WOW where did you come up with using a battery to charge your phone?
My bet the battery needs to be trained again. Let it die then charge it back to full. The fact the battery failed like that might mean its still going bad so if it were me.. id get a new battery when you could. Trickle charging all the time probably isnt the best either but you do what you have to for a charge.
I just wanted to thank the OP (which I did using the button) for actually posting his solution so future searchers will not just come across the question.
Same thing is happening mine now. I can get into fastboot but from searching everywhere it seems the phone will not charge when its in fastboot. I may aswell go find a square battery somewhere around my house and give this a shot.
I found by searching that there is a fastboot charging script but that seems to be in the One X forum , I tried it anyways and my phone just keeps rebooting into fastboot. Im sickened because a girl I was with on friday night said to me on facebook that she sent me some good pictures but I cant get phone on to look at them ha ha . ill try whats in the first post here now and see how I go. Thanks.
Man my phone is old. Good to know this thread helped a few people.
Sent from my HTC EVO 3D X515m using xda premium
For many months now I had been using the same version of Carbon ROM and whichever kernel was available at that time I installed it. Sometime after flashing that last update I learned that when I started to use my phone heavily enough to drop the battery to less than 50%, it would eventually and randomly shut off well before the battery was completely drained. As I also had also problems with the phone passing the boot screen most of the time so I figured they were just ROM or kernel issues that I would deal with later. I ended up just dealing with these two issues this whole time. Fast forward to now, I finally got around to updating my phone and wiped then flashed both the newest C-ROM and corresponding kernel. Sadly to say, the battery is still causing issue.
So, anywhere from the 40% range down to maybe 15% at the lowest I've seen, my phone randomly shuts off. Attempting to turn the phone right back on fails because it either shuts off again during boot, or immediately after the home screen manages to appear. In one of these instances of the latter I saw the phone reporting it was at <1% battery capacity, not even a minute later, before shutting off a second time.
After connecting a charger for a minute and powering the phone back I can finally pull up the graph like the one below, showing a sudden and unexplainable drop, although the right hand side is usually much lower than ~18% when its turned back on. It then continues to charge as normal.
Granted this is after a few hours of active screen-on time, and I also occasionally see the battery level stop for several minutes at a single value while in use. Is this just an issue with the phone reporting the correct battery capacity, or something else? This is somewhat alarming considering the battery cannot be replaced.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This sounds similar to http://forum.xda-developers.com/showthread.php?t=2505825 but of course there are no replies.
Azbulldog said:
For many months now I had been using the same version of Carbon ROM and whichever kernel was available at that time I installed it. Sometime after flashing that last update I learned that when I started to use my phone heavily enough to drop the battery to less than 50%, it would eventually and randomly shut off well before the battery was completely drained. As I also had also problems with the phone passing the boot screen most of the time so I figured they were just ROM or kernel issues that I would deal with later. I ended up just dealing with these two issues this whole time. Fast forward to now, I finally got around to updating my phone and wiped then flashed both the newest C-ROM and corresponding kernel. Sadly to say, the battery is still causing issue.
So, anywhere from the 40% range down to maybe 15% at the lowest I've seen, my phone randomly shuts off. Attempting to turn the phone right back on fails because it either shuts off again during boot, or immediately after the home screen manages to appear. In one of these instances of the latter I saw the phone reporting it was at <1% battery capacity, not even a minute later, before shutting off a second time.
After connecting a charger for a minute and powering the phone back I can finally pull up the graph like the one below, showing a sudden and unexplainable drop, although the right hand side is usually much lower than ~18% when its turned back on. It then continues to charge as normal.
Granted this is after a few hours of active screen-on time, and I also occasionally see the battery level stop for several minutes at a single value while in use. Is this just an issue with the phone reporting the correct battery capacity, or something else? This is somewhat alarming considering the battery cannot be replaced.
This sounds similar to http://forum.xda-developers.com/showthread.php?t=2505825 but of course there are no replies.
Click to expand...
Click to collapse
Probably a sign of a bad battery. Eventually it will just stop working. If your under your year warranty contact htc and they can perform a repair for free. If your not I would still contact them and they will perform a repair and give you a quote.
Please press the thanks button if I have helped you in anyway.
Jaggar345 said:
Probably a sign of a bad battery. Eventually it will just stop working. If your under your year warranty contact htc and they can perform a repair for free. If your not I would still contact them and they will perform a repair and give you a quote.
Please press the thanks button if I have helped you in anyway.
Click to expand...
Click to collapse
Looks like I'm a several months past warranty. If it is just the battery going bad, which is pretty pathetic given the short amount of time, comparatively, maybe I'll look at replacing it myself. Won't that be fun.
Sent from my HTC6435LVW using Tapatalk
Azbulldog said:
Looks like I'm a several months past warranty. If it is just the battery going bad, which is pretty pathetic given the short amount of time, comparatively, maybe I'll look at replacing it myself. Won't that be fun.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Replacing it would be very difficult. It's fused to the housing of the phone. Good luck.
Please press the thanks button if I have helped you in anyway.
Jaggar345 said:
Replacing it would be very difficult. It's fused to the housing of the phone. Good luck.
Please press the thanks button if I have helped you in anyway.
Click to expand...
Click to collapse
I found at least one video on how to perform the operation, just carefully prying off the glued parts. That will be the last resort.
HTC Support responded to my email and recommended performing a "battery reset" by holding down all three physical buttons while the phone is powered down, for two minutes. Before powering off it was at around 75% battery after charging for a little while. So as I did the button hold and it of course kept flashing the boot screen, but after two minutes I let it boot up fully and the battery was reported at 58%. So either it drained that much charge in those two minutes, or it's now giving a more accurate reading.
I'll have to continue testing to see if it still shuts off.
I have started looking at other battery calibration methods, and will try those as well.
Azbulldog said:
I found at least one video on how to perform the operation, just carefully prying off the glued parts. That will be the last resort.
HTC Support responded to my email and recommended performing a "battery reset" by holding down all three physical buttons while the phone is powered down for two minutes. Before powering off it was at around 75% battery after charging for a little while. So as I did the button hold and it of course kept flashing the boot screen, but after two minutes I let it boot up fully and the battery was reported at 58%. So either it drained that much charge in those two minutes, or it's now giving a more accurate reading.
I'll have to continue testing to see if it still shuts off.
I have started looking at other battery calibration methods, and will try those as well.
Click to expand...
Click to collapse
I also believe your battery is dead. I had the same exact problem with my HTC Amaze. The problem starts with a bad kernel that runs your battery hard heats it up and ends up with a bad broken. I'm sorry to say but there's no way around replacing it. I tried everything to get more juice or of it but it was too late.
Sent from my SGH-M919 using xda app-developers app
Azbulldog said:
I found at least one video on how to perform the operation, just carefully prying off the glued parts. That will be the last resort.
HTC Support responded to my email and recommended performing a "battery reset" by holding down all three physical buttons while the phone is powered down, for two minutes. Before powering off it was at around 75% battery after charging for a little while. So as I did the button hold and it of course kept flashing the boot screen, but after two minutes I let it boot up fully and the battery was reported at 58%. So either it drained that much charge in those two minutes, or it's now giving a more accurate reading.
I'll have to continue testing to see if it still shuts off.
I have started looking at other battery calibration methods, and will try those as well.
Click to expand...
Click to collapse
Any luck?
I was just hoping that it'd be some kind of calibration issue. I saw that same tutorial and it looks kind of hard to put it back together more than anything else.
jjlwork said:
I am already a subscriber to spinvox which is through my carrier (Telus Canada), I get it for 7.50 unlimited so I am really looking for a solution to that service. Like I said in my previous post mvisualvoicemail works great for this it actually identifies which of my email are voicemail and only displays those however I would like an app that pulls in the transcripted version too, so I can be selective in which ones I want to listen to. I figured if a program like throttle launcher can pull in the header information and display it, it wouldn't be too hard to make an app that pulls the information from an emailed voicemail and displays it nicely for review. Maybe I'll post over in the throttlelauncher thread as a request for a plugin actually.
Spinvox apparently has an app for windows mobile in a private beta test but they will not allow subscribers who subscribe through their carrier partners to use it yet.
Click to expand...
Click to collapse
Yeah its a hard phone to perform repairs on.
Please press the thanks button if I have helped you in anyway.
dickcruz said:
Any luck?
I was just hoping that it'd be some kind of calibration issue. I saw that same tutorial and it looks kind of hard to put it back together more than anything else.
Click to expand...
Click to collapse
Well after I did HTC's recommended reset I started to drain the battery to see if it would shut off unexpectedly, but it steadily went all the way down to 1% before doing so like it should. I guess that's an improvement, but I don't know how it will behave in regular usage. I then left it off to charge completely before powering it back on the next morning. Maybe it will get worse but I'll just have to wait and see, at least now it should be reporting the proper values if that was the case.