Related
Hi everyone, just got the tablet today and set it up at work, played with it for bit and everthing was working fine.
Got home about 2 hours ago and now when I wake it from Sleep, the touch screen is not responding at all. Have tried everything, power is 98%, plugged into a PC, did the hard reboot, even wiping the data to start setup again. But all to no avail.
The screen isn't responding at all. Its very frustrating as I want to play with it some more!!!
Hope someone has experienced this and can help.
had the same issue once...i turned it off and left it for about 5min...turned it on and the screen works again...
this hasn't occured since then..probably just a system glitch..
Happened to me once, reset the device and it worked. Now it happened again and its been unusable for a day. If it doesn't work tonight, the $hit is going to hit the fan...
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Have you guys contacted ASUS support? They will probably have you RMA it. How long did you guys have it before this happened? Now I'm worried that mine will do the same thing.
ASUS support did want to RMA my TF that was having this problem. However, after leaving it off for a couple hours, I went to turn it on to wipe out all my account settings and the touchscreen started working again.
I have no explanation for why it started working though. The last thing I did before it was magically fixed was go through the normal shutdown procedure by answering the 'do you want to shut down' using the dock's mouse instead of just holding down the power button. Maybe that made a difference?
Blue_Man said:
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Click to expand...
Click to collapse
This is what happened to me. Stuck at the lock screen, no touch at all. After 4 days of waiting for Asus to reply to my email and several disconnected phone calls, I have returned it to newegg. Since this item is still out of stock I expect to receive a full refund. Which is fine by me. June 8th, here I come.
Same thing happened to me, just returned it to fry's and was able to avoid the restocking fee. Going to get the galaxy tab come june 8th now instead.
Sent from my Xoom using XDA Premium App
I have weird little quirky things like this happen from time to time with my TF, such as having to hit the power button or lock button twice before it works. I think it might be more of a software issue than anything to be honest. Hoping that future updates will correct all of these issues.
I hope its a software issue....
Found a solution that worked for me. I booted into recovery mode by holding vol down and power. then I selected vol up to enter recovery. Then the exclamation point came up with the android robot. I left it like that for a few minutes then held down the power until it resarted.
It booted up like normal, no data lost. I then restarted for good measure. Came right back up like normal, touch screen and all.
Thanks jdmnash. I followed your instructions and it worked like a breeze. Should make this part of a sticky help thread.
Found a solution
Update: Tried every fix I could identify on the forums as I was also draining the battery as suggested on several forums. After 4 days waiting for the battery to drain, I was able to restart the TF and get active responses to the touchscreen. Unfortunately I had performed a reset and wipe earlier so I am having to reload everything. I am happy to have a functioning TF again, but have serious concerns about this failure and this awkward repair method. Additionally, I have still not had a response from ASUS support from 5 days ago.
Mine is constantly doing this. Randomly.
Its as if the daemon for screen touch detection crashes. The rest of the unit is fine but that stops and the only fix is a power button off, then on.
Something is not right here. Its vanilla out of the box, no extra software just the 13 FW update.
Will 3.1 fix this? Hopefully, as it stands, this will have to be returned. It is not fit for purpose, constantly failing.
same problem
Just picked up mine. Out of the box at a cafe it worked just fine. Brought it home and same problem as everyone else in this thread. Have tried all of the suggestions in this thread (except waiting for the battery to die). Even installed the 3.1 update via SD. Still no joy. Guess I'll try a few more things before returning it. My guess is a problem in the supply chain with the capacitors that detect screen touch. Doubt that it can be solved solely through a software update (or if it can it definitely didn't make it into 3.1)
my touch screen stopped working a week ago while i was at school. and i got really pissed and just kept on rebooting it and after like 5 or 6 reboots it started working. Havent had same problem since.
Hmm... thanks for suggestion. Tried booting it about 5 times but still borked. Draining the battery now as my last attempt before taking it back.
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Unstable touchscreen
obi-nine said:
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Click to expand...
Click to collapse
Hi , After the battery is zero and then 30 minutes charging, in order to make it work , did you discharge it right after 30 minutes or still you keep it charging ?
I got same problem with my TF which is really a disappointment.. I tried to factory reset, reboot ... but still can't make it work. I have to try this trick by draining the battery to zero. Hopefully, I get advise from all of you for this problem ?
Thanks a lot
Can you guys try using ADW launcher and see if things improve?
I think it did for me.
Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...
He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.
Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...
As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.
Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.
Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!
Ok, stop me if you've heard this one before (I've searched and searched to find a solution to this issue, so I appreciate any help I can get)
I recently rooted my TF101 and have been flashing different ROM's to see which one I like the best. I'm not a complete NOOB, but I've never done flashing on a tablet before. I flashed Megatron 1.6.1 and when I went to reboot I couldn't get out of recovery and it kept looping back to recovery despite my doing a complete re-wipe/flash. When I finally powered down I wasn't able to power back on.
Now the unit will not turn on, either regularly or in recovery. It's completely dead. I've been letting it sit plugged in for a while to see if that helped and still nothing. I've held the power button down in every conceivable way and for different lengths of time and still nothing.
I'm at my wits end... any help would be AMAZING!!! Thank you in advance.
Can you get into APX mode? You may want to nvflash back to stock and try again.
Sometimes the tf not really shutdown, it just freeze in black screen when we thought it already shutdown. Undock it and plug in charger to see if it charging as it might be given up totally battery drained.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Rogueharvest said:
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Click to expand...
Click to collapse
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
redninja007 said:
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
Click to expand...
Click to collapse
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
new damages
farsight73 said:
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
Click to expand...
Click to collapse
i already tried nvflashing back to stock it went back to stock but the screen still wont turn on...i charged it for 12 hours still nothing.but it plays music still ...after getting pissed off,,,my wife hits the tf101 screen and then it turns on finally but the screen was orange and red... then she hit it again then i think she damaged it once more hahhaha....im pissed off too but when thinkin bout her face while hitting the tf101 EPIC hahahha...any help wanted i wanna buy new screen... attatched is the picture she sent me hahaha
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
---------- Post added at 11:47 PM ---------- Previous post was at 11:38 PM ----------
Chichoman said:
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
Click to expand...
Click to collapse
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Chichoman said:
<snip>
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Click to expand...
Click to collapse
This won't do anything for the OP's inability to boot. That's why I said that likely his best bet is to see if he can boot into AP Fastboot, so that he may be able to FXZ back to stock...
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Apex_Strider said:
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
fire_fist_ace said:
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
Click to expand...
Click to collapse
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Apex_Strider said:
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Click to expand...
Click to collapse
The battery reset actually worked! I had to charge it for quite a while on the usb charger since it wouldnt charge on the mains charger. Once it was on i made a backup then cleared the battery stats, and now it detects the mains charger.
Cheers for your help guys i still dont get why it wouldnt charge on the mains charger when the battery was low, even though before it would charge before when the battery wasnt...
Hello. I have problems with my device, a Motorola Razr xt925 HD. It doesn't start, it just keeps the green led blinking when connected to wall charger, and when I plug the USB, makes a sound of a new device detected but only for a few seconds then it makes a sound of an unplugged device, and so on. It doesn't respond to any combination of buttons. I let it charging overnight, even though the battery was nearly full before this happened. Don't know if this is relevant but before this happened, I was going to flash stock Retail Brazil firmware by fastboot and got a flash failure. I turned it off and then it wouldn't turn on again. I never had this happened, I had problems but I always solved them all. Not this time hopefully you guys can help me or tell me what it could be, because I doubt it was the battery. I leave you a video showing my case.
i dont know for certain but the only time i see that green light is when battery is ou and i put it to chrge. Could your phone be in apfastboot and can t charge. It is a bit of a tough situation to troubleshoot.
Did you try keys combo to put it in fastboot, and test it by flashing
or maybe use rsd lite see if it shows you device connected? maybe then you can flash stock
i am sure there are other possibilities, let s hear from you
There's no way to enter in Fastboot by key combos and RSD lite doesn't show my device :/ maybe I need a factory cable, just in case that the battery is empty. I need more suggestions please
me paso lo mismo
did you find any solution?
im having this problem after i start using KK 4.4.2 seems like the phone go to sleeping mood by it self while my screen is locked so i have to keep clicking at power and volume up and down to restart the device now im looking for an update or a fix for this problem, another problem is the device WIFI do not catch my house signal while im away 10 feet from the house the software have bugs
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
chuYxP said:
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
Click to expand...
Click to collapse
i think your your device is dead.
this exact thing happened to me.
it happened on september, i was forced to get a new device.
i love this phone but it was dead.
i hope a fix comes through i would like to have it back
I ll take one of your hand, I need parts if interested
Any update with this? Did you try with a factory cable?
I'm going through the same thing , I read the other day that and the driver installed and nothing more .
keep trying to revive my device.
I'm going through the same thing. When I plug it into my pc , under device manager it shows "Human Interface Device" then it unmounts itself then remounts itself then unmounts. Over and over..... I've even replaced the battery.
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
kilroy1stcav said:
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
Click to expand...
Click to collapse
This thread for the droid Ultra might interest you: http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
There is some discussion of the Razr HD in this thread. It looks like someone with an unlocked device would need to dd their bootloader partition for this method to work.
A few years later .... Any solution? rsrsrs
any update on this scenario?
i have this situation too and the time could give us an answer, i am searching again, i took my device to some 'phone repair stores' and in less than 5 minutes they told me that the phone was dead, but i have my last doubts
Just to add an update here
I ended up with the Green light only and blank screen after trying to fix a battery issue, despite getting a number of batteries my phone wasn't accepting the batteries.
I remembered a battery issue a long while back, so went to reflash my phone to see if it resolved it.
I ended up with the green light and blank screen and no matter what buttons, it would just make a noise then keep rebooting.
I ended up using the Unbrick bat file.
RSD Lite was briefly showing a Medfield device of something starting with Med, but since the phone kept rebooting I couldn't reflash it again.
I did the Pwr and Vol down and as soon as I saw the device, I clicked the UnBrick bat and it managed to get my Moto logo up.
I then booted to Fastboot mode and reflashed and my phone is back,
See this link for the UnBrick, but when you do it, you have to be fast to catch it while the device is seen, otherwise the phone reboots after 4s or soo.
Softely Unbrick XT890 Razr i - Really Unbrick the Zombie
Well do not think that this thread is one among others. It's my experience when i messed up with my Razri. I wish I had this before, so I'm sharing it with you ! Every has his experience and a way to do it, so this is mine First I searched...
forum.xda-developers.com