So I have a RAZR MAXX HD that has been rooted running Cyangenmod 10.2 and bootloader unlocked for a few months now. But the last couple weeks, each time I plugged phone up to charge, it kept starting a reboot loop. Each time it reached the start of Cyanagenmod boot logo, it restarted. So I thought maybe it was a bug in the latest Cyangenmod. So I tried updating. But I didnt realize that I accidentally chose Cyangenmod 11, thus when it was installing in Clockwork Mod Recvoery, it errored out about 1/3 of the way through. This erased everything.
So I was going to try hooking up to my MacBook and using fastboot to load new OS. However, as soon as i plugged in my phone, my computer shut down and would not turn back on. Had to go to Apple store to do a hard SMC reset. Thought that was a fluke and tried using my computer again and same thing happened. Phone still has CWM recovery working (i think properly). How do I get a working phone again? I tried putting OS on SD card on another phone and putting SD card my MAXX HD in and trying. That installed OS fine but when i rebooted, it still would not go past "bootloader unlocked" warning screen.
Also, I tried once more to plug in to my computer once more last night. However, it did not shut my computer down, but I did get a warning from OSX to unplug the USB device that was consuming too much power.
Any help would be appreciated! Thanks!
i would tend to be more concerned as to why its drawing to much power before trying to get it working again. did you try another usb cable? and check the charging port for debris? seems like something is causing a short circuit. this wouldnt be noticable while charging normally except it would likely take longer than it should to charge. if you rule out the things i have suggested above and its still has the short then there is likely a hardware issue, which over time will certainly get worse to the point of failure.
i dont see how a software issue would effect the charging circuit, i could be wrong.
bweN diorD said:
i would tend to be more concerned as to why its drawing to much power before trying to get it working again. did you try another usb cable? and check the charging port for debris? seems like something is causing a short circuit. this wouldnt be noticable while charging normally except it would likely take longer than it should to charge. if you rule out the things i have suggested above and its still has the short then there is likely a hardware issue, which over time will certainly get worse to the point of failure.
i dont see how a software issue would effect the charging circuit, i could be wrong.
Click to expand...
Click to collapse
Thanks for replying. I have tried multiple USB cables and they all do the same. And I know it isnt my computer USB slot since other devices/phones do not trip my power on my MacBook. Do you or anyone else who might read this reply know if I could send the phone in for repair under warranty considering it is rooted and bootloader unlocked? Im not too sure if unlocking the bootloader could cause power issues like this and if companies would even help for hardware issues since it is rooted/unlocked.
vol4life27 said:
Thanks for replying. I have tried multiple USB cables and they all do the same. And I know it isnt my computer USB slot since other devices/phones do not trip my power on my MacBook. Do you or anyone else who might read this reply know if I could send the phone in for repair under warranty considering it is rooted and bootloader unlocked? Im not too sure if unlocking the bootloader could cause power issues like this and if companies would even help for hardware issues since it is rooted/unlocked.
Click to expand...
Click to collapse
i don't see how rooting or unlock the bootloader could cause this as they are both generally software.
sending it in under warranty is a big risk imo, you would be better off if it was fried and they couldn't see the bl unlock and root. if they see it, they could likely bill you for the replacement phone, if they don't notice, you will likely get a refirb that's updated past the point of unlocking. so there will be no more modding. plus the phone is a couple years old, personally i would look to upgrade.
just some food for thought.
btw, i shelved my rmhd for a g2, the rmhd is a great phone, but the g2 just blows it away in almost every aspect.
bweN diorD said:
i don't see how rooting or unlock the bootloader could cause this as they are both generally software.
sending it in under warranty is a big risk imo, you would be better off if it was fried and they couldn't see the bl unlock and root. if they see it, they could likely bill you for the replacement phone, if they don't notice, you will likely get a refirb that's updated past the point of unlocking. so there will be no more modding. plus the phone is a couple years old, personally i would look to upgrade.
just some food for thought.
btw, i shelved my rmhd for a g2, the rmhd is a great phone, but the g2 just blows it away in almost every aspect.
Click to expand...
Click to collapse
Thanks man.. Yea i was kind of thinking the same thing but wasnt too sure. Maybe I can go somewhere locally and see if they can repair it for cheap. After having a phone that goes 1.5 days on one charge, I got spoiled. LOL plus I love the build quality much more than most oter phones like S3/4 etc.
Related
Hi,
My girlfriend has Desire S, from today's morning, when I call her or she calls me, she cannot hear anything, and neither do I, its completely dead, no answer... She said, that she cannot even hear an ringing, when my phone is ringing, so thats weird, and looks completely gone.
Today morning, when I took my phone(SGSII) off charger, it was dead and not turning on, for some reason, so I had to pull battery out and back, and then my SGSII started working again.
Thinking of this, I am afraid, that the speaker and microphone on her phone got permanently damaged by some overcharge during the night while it was on charger, since my phone got some issues at the morning too...
Any ideas? Her phone is nonrooted and in warranty, so we'll get that exchanged within warranty, if this proves to be the cause, but I am not really certain of it, would anyone here have similar experience?
Zheiko said:
Hi,
My girlfriend has Desire S, from today's morning, when I call her or she calls me, she cannot hear anything, and neither do I, its completely dead, no answer... She said, that she cannot even hear an ringing, when my phone is ringing, so thats weird, and looks completely gone.
Today morning, when I took my phone(SGSII) off charger, it was dead and not turning on, for some reason, so I had to pull battery out and back, and then my SGSII started working again.
Thinking of this, I am afraid, that the speaker and microphone on her phone got permanently damaged by some overcharge during the night while it was on charger, since my phone got some issues at the morning too...
Any ideas? Her phone is nonrooted and in warranty, so we'll get that exchanged within warranty, if this proves to be the cause, but I am not really certain of it, would anyone here have similar experience?
Click to expand...
Click to collapse
Have you tried a normal restart of your wife's phone (the Desire S) to see if the problem still persists?
Not that I can see it would help, but the next step would be to perform a full factory reset before testing again and then if no joy, returning the device under warranty for service with what sounds like a hardware problem.
Leaving these devices on charge all night is not ideal as it's a waste of electricity and risks over heating the device, you should only need a few hours to full charge the device.
Care should be taken not to remove the battery while the Desire S is running, unless you ultimately have to (ensure that Settings->Power->Fast Boot =OFF)
ben_pyett said:
Have you tried a normal restart of your wife's phone (the Desire S) to see if the problem still persists?
Not that I can see it would help, but the next step would be to perform a full factory reset before testing again and then if no joy, returning the device under warranty for service with what sounds like a hardware problem.
Leaving these devices on charge all night is not ideal as it's a waste of electricity and risks over heating the device, you should only need a few hours to full charge the device.
Care should be taken not to remove the battery while the Desire S is running, unless you ultimately have to (ensure that Settings->Power->Fast Boot =OFF)
Click to expand...
Click to collapse
Well, we are at work atm, so I was trying to guide her turning off the phone via SMS, she said she have done it. after arival home, I'll take a closer look on the phone, trying to remove battery completely and checking the FW status. I'll do factory reset using hboot, and check for updates... hopefuly this might help... If not, I'll probably be forced giving her my old Desire to play with till she gets back her beauty
Zheiko said:
Well, we are at work atm, so I was trying to guide her turning off the phone via SMS, she said she have done it. after arival home, I'll take a closer look on the phone, trying to remove battery completely and checking the FW status. I'll do factory reset using hboot, and check for updates... hopefuly this might help... If not, I'll probably be forced giving her my old Desire to play with till she gets back her beauty
Click to expand...
Click to collapse
(sorry to repeat)
Although, before you power down the Desire S do ensure that Settings->Power->Fast Boot =OFF
As the title says.
Thinking of getting this device on the cheap. I have a Moto factory cable that i've used to flash stock firmware onto a couple different devices.
Would that same cable work on this device to get it into fastboot?
Are there any cases of completely hard bricked devices?
Also, if any of you experts know some questions i might want to ask the guy, I'm all ears! Thanks!
Markyzz said:
As the title says.
Thinking of getting this device on the cheap. I have a Moto factory cable that i've used to flash stock firmware onto a couple different devices.
Would that same cable work on this device to get it into fastboot?
Are there any cases of complete hard bricked devices?
Also, if any of you experts know some questions i might want to ask the guy, I'm all ears! Thanks!
Click to expand...
Click to collapse
You can use the moto factory cable on the xoom but that just gives it power to fastboot.
You can have a xoom be hard bricked. If you plug it in and it shows up as a APX device it is hard bricked. (i own one that's sits in the drawer for spare parts for it's replacement) The charge light will still come on.
What type of xoom is it a (wifi 3g/4g family edition)
You should ask what caused it to brick?
was he rooted?
If you buy it post here and I can give a one click restore for it. AI have it for most versions of the xoom.
Be Sure...
Before you buy it I would recommend getting as much information as possible from the seller as this device may be beyond repair. If the device can still be recognized in fast boot then you should be fine.
if it is a 3g/4g xoom you might want to get the esn/meid number and check with verizon if it is clean.
If the bootloader is damaged it is of no use other than spare parts. You must at the very least be able to get to fast boot. If it is not recognised when plugged into the USB there is nothing to be done without serious hardware hacking.
I have one just like that in a box. It is rare, but it happens. It will not even flicker when powered up - nothing.
Grege50 said:
If the bootloader is damaged it is of no use other than spare parts. You must at the very least be able to get to fast boot. If it is not recognised when plugged into the USB there is nothing to be done without serious hardware hacking.
I have one just like that in a box. It is rare, but it happens. It will not even flicker when powered up - nothing.
Click to expand...
Click to collapse
This morning while loading a webpage (20% of battery life left) my MZ601 just froze, didn't respond to any screen or button presses, slowly went to sleep and has resisted all attempts to start since then. Even hooked up to the charger for the last hour, it still doesn't respond no matter what buttons I press, completely blank, no lights, nada...
I'm guessing it's a dead parrot, has anyone else had a similar Xoom death?
EDIT: Just found a more appropriate thread, ignore...
This is very strange. I have my phone completely normal. It's been charged and is running fine. The phone is unlocked, rooted, and running CM10.1. I decide I want to use an external controller to play one of my games. It is a Xbox 360 wireless controller. I load up Beach Buggy Blitz on my device, close all the other apps, and return to my home screen. I then plug in the wireless adapter for the controller via USB OTG. I have used this controller fine on my N7 and maybe even my SGS3 at one point. Everything seems all good and normal. So, I plug in the micro USB into my phone and wtf. It just completely and instantly shuts off and the screen goes pitch black. I mean as soon as I plugged it in, there was an instant and total shutdown of the device. I thought this was weird, so I unplug the USB adapter and try to turn on my device. No dice. I remove the battery and try again. No dice. I hold down the power button for a really long time. I charge the device. Nothing. I charge the device with and without the battery, while pressing and holding the power button and with different button combinations multiple times. Nothing. The device will just not respond in any way. I even tried my N7 charger, but it doesn't work. The USB port feels fine and it seems like the chargers are going in just fine. I'm leaving the device the charge overnight with the battery in it, but I don't know if even that will work. I can't believe this happened. I just plug in a USB and it seemingly kills my device. That doesn't make any sense. Anyway, what should I try? What if it doesn't turn back on? I did buy Squaretrade warranty that covers accidental stuff and I've never made a claim with them yet. Any help will be appreciated, thanks!
TL;DR: I plugged Xbox 360 wireless controller adapter into my completely normal GS3 rooted and unlocked with CM10.1 via USB OTG and now the device won't respond at all despite several and varied attempts.
Your Power Management IC self destructed. It's a common occurrence with S3's. Some devices overload it and it kills the phone.
It should be covered under basic warranty through Verizon, and they'll ship it to you overnight. I'd recommend not mentioning your usage of the OTG though. I've had to get a replacement for the same reason.
Just tell Verizon that your phone won't power on, charge, or show any signs of functionality whatsoever.
themusicmonkey said:
Your Power Management IC self destructed. It's a common occurrence with S3's. Some devices overload it and it kills the phone.
It should be covered under basic warranty through Verizon, and they'll ship it to you overnight. I'd recommend not mentioning your usage of the OTG though. I've had to get a replacement for the same reason.
Just tell Verizon that your phone won't power on, charge, or show any signs of functionality whatsoever.
Click to expand...
Click to collapse
I kind of figured it would be some sort of power issue. But man, completely killing a normal device just by plugging in something for just a second is insane. So does this mean I get a completely new phone (same model) when I send my old one in? Can I retrieve any data still on the device? I hope I have a decent Titanium still on my SD card. Will I have to re-unlock, re-root, and re-flash my ROM? That would be annoying seeing how I haven't unlocked or rooted my device in several months. Thanks.
Dillon610 said:
So does this mean I get a completely new phone (same model) when I send my old one in? Can I retrieve any data still on the device? Will I have to re-unlock, re-root, and re-flash my ROM?
Click to expand...
Click to collapse
They send a refurbished phone, Certified Pre-owned or something, and you keep the back cover, cards, and battery. You'll have to send your phone back in the box, or they'll charge you. Call them ASAP, because I pre-ordered the phone, and my manufacturer warranty expires on the 4th. If they try to charge you, remind them that it's covered under that.
I don't know of a way to get any data off of it, other than physically hacking/repairing your phone of course. If you could do that, you could also fix it yourself
You will have to do all rooting and flashing again, but here's a good tool to root it. http://forum.xda-developers.com/showthread.php?t=2332825
Hi guys,
Been having issues with charging for the past couple of days. When I plug my phone into the charger it states that it's charging, but nothing really happens. The troubleshooting so far:
Have tested it on multiple different chargers, all having same problem. However, my Nexus7 tablet will charge normally on these chargers, so we can rule out it's charger related.
Tested for differences with the phone switched on or off. When phone is switched off it will charge, but not with the speed it normally does.
Running CM11 Snapshot M9. Did a clean install. Battery does not charge normally (read 1% gain per 20 min) on most stripped down version (without gapps + personal apps)
Looks like it's battery related. But I find it difficult to rule out what's causing my phone to act funny. The weird thing is that sometimes my phone will go for a decent charge, but this happens so randomly that it's hard to find any form of sense in this process. Also, when the phone is on and charging, the battery light will sometimes turn off. But when I activate my phone again, the battery light will bleep on as if nothing happened and everything is functioning normally (which is clearly doesn't).
Does anybody have an idea how I can fix this? Any helpful tips that can point me into the right direction to figure out what's causing this? Many thanks in advance!
did some more testing - can anyone help me out?
After some additional testing I'm fairly sure that it's either battery or chip related:
USB debugging does not work at all (storage is set to MTP). When I open Android File Transfer my Mac will recognise the Nexus 7 tablet, but not the Nexus 5. Debugging is switched on in Developer options.
When I try to use adb or fasboot, my device is not listed either, nor are any commands (directed towards phone) executed through bootloader.
In the about Phone section I went to check the Battery info. It will state correctly that the phone is being charged through AC or USB (depending on wether the device is connected to laptop or charger).
Does anyone have an idea how I can figure out if it's chip or battery related? I desperately want to find this out, because I bought my phone in The States and live in Europe... So in the worst case scenario the phone needs to go back to the US due to bureaucratic policies. Already had to go through this horrible proces half a year ago with a bad NAND chip, really want to avoid the hassle and lose my phone for at least a month. So if it's a battery thing I rather order a new one and replace it myself
Really really hope someone can shed light on this issue, running out of luck and options. Please guys, please :angel:
sounds like the usb connection, physical, is going. if it doesnt charge but randomly will, fastboot nor adb see it, i think its an usb connection issue. i had the same with my nexus one a long time ago, if i wiggled the the connection when it was connected, sometimes i could get it to charge some. fortunately, it isnt an expensive repair, and yours should still be under warranty.
simms22 said:
sounds like the usb connection, physical, is going. if it doesnt charge but randomly will, fastboot nor adb see it, i think its an usb connection issue. i had the same with my nexus one a long time ago, if i wiggled the the connection when it was connected, sometimes i could get it to charge some. fortunately, it isnt an expensive repair, and yours should still be under warranty.
Click to expand...
Click to collapse
Thanks for the reply, really appreciate it How much you reckon it will cost? Also, can I do this at any decent phone recovery shop? As stated previously, really want to avoid sending the phone back to the US. Once again thanks!
suikerchiller said:
Thanks for the reply, really appreciate it How much you reckon it will cost? Also, can I do this at any decent phone recovery shop? As stated previously, really want to avoid sending the phone back to the US. Once again thanks!
Click to expand...
Click to collapse
i paid $35 3 years ago(?) at a local repair shop.
@simms22: ordered a USB portal online and replaced it by myself. Phone works again. Thanks for the tip!
I'm having an issue with a 3 year old Google pixel where the phone is no longer bootable due to it dying anytime it is turned on. Symptoms started about a year ago, the device would occasionally die randomly when opening apps especially with a camera like Snapchat. The issue was originally very infrequent but got more and more common until every app that is opened would kill the device if not plugged in. At this stage anytime the device died it wouldn't use to boot until plugged in. About 4 months ago it started dying even if it is plugged in and now it refuses to boot rom or stay alive in recovery long enough to even decrypt the device. Device is also unstable if plugged into a computer as it constantly reconnects and disconnects. The really odd part about all of this is booting into fastboot works just fine and it will stay in fastboot as long as it's plugged in. I'm thinking I'm gonna have to tear down the device and replace the battery manually but I'm not 100% sure if this is the cause so I'm asking here for confirmation first. Any advice would be greatly appreciated as I need to get data off the device to move to my new pixel3
EDIT: Well, f*** me, after looking through q&a section for 2 minutes I found other people have started having this issue around same time frame as me and it turns out the problem is the motherboard is shot which I was also thinking in the back of my head but didn't want it to be true. I'm so not spending $300 to replace the Mobo of a 3 and a half year old phone, but I do need to get the data off of it. My understanding is that adb DOESNT work over fastboot so I think I'm gonna try to plug it into my laptop and see if I can get twrp alive long enough to get any kind of filesystem access.
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
uaDPJ said:
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
Click to expand...
Click to collapse
It's not the battery. Many other sources confirm that this is a motherboard problem. At first it definitely seemed like a battery problem given original symptoms but at this point there is a wide range of random symptoms that point to the board being shot.
On a brighter note I've managed to keep the device alive in twrp long enough to pull data off by plugging into a computer. Wall charger would cause it to die despite charger working fine with several other devices
A bad battery can leak onto the board and fry the board, so you may both be right.