Related
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
I tried following this guide, though without success. The phone still has that white LED lit when it's connected to the PC.
After a reply on this thread I also made, it might be possible that the battery is charged, but the phone refuses to boot at all. Is there any way to unbrick the phone in this state?
Do you think your device is really BRICKED?
If so, you can try to flash your original sbf file into your phone. Guide here: http://forum.xda-developers.com/showthread.php?t=696845
If you are using a Linux, google for "sbf_flash".
I agree with my front floor..ermm, u dont need to worry about its 'dead'. just flash original sbf can rescure your phone.
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
algopem said:
I had the same problem too, but good news is I tried to revive my phone successfully recently, btw your phone is not 'dead', it's just staying in limbo state, the solution is to pull out the battery and don't connect to any usb, don't try to power it up, it must be completely out of power wait about 12 hours, and then try to power your phone, I think there is some capacitors in the phone which retain the phone state, to make it out of power will wipe out it's state, good luck
Click to expand...
Click to collapse
"My phone is in limbo state... "
That's a pretty cool statement.
From technical view, it might have happened that something caused a kind of deadloop when reading scratchpad SRAM inside OMAP processor.
This SRAM, as well as the internal RTC is powered by a small battery soldered on the mainboard, while the phone is shut down and the battery is taken out.
What you did was, to wait untill this battery became uncharged.
All SRAM and RTC setting as well then gets erased.
Afterwards the CPU will start up with empty scratch SRAM, might be called a "real" cold boot
Normally the phone should not behave like this. Even if SRAM is not valid the phone should boot up...
...but anyway as you observed it like this, it might happen.
@andoruB:
Apart from that, the Milestone is hard to brick in general.
Might happen though, if you do evil things while flashing new firmware.
Especially while flashing bootloaders...
If you got some more information about the things you did, would be helpful!
Good luck anyway!
scholbert
andoruB said:
After an unfortunate rooting session with my Motorola Milestone, the phone now returns into an "dead" mode. It refuses to start at all. I tried charging it and see if it starts by itself, but it doesn't budge and the little while led doesn't lit. The only time when it lit is when I connect it to the PC. I tried putting in it a new battery, taking out the SD card and SIM, but to no avail. I remember seeing a video where a guy used a dissected USB cable to spark the phone into turning on again, so I take it I'll have to use a "hardware approach"? Please help.
Click to expand...
Click to collapse
how did u root it? can u give a more detailed description? and hows ur phone? sometimes, the milestone would just shut off and wont come up if the battery is gone. Try charging it for maybe 2-3 hours, untouched, and see what happens.
Have this exact problem. Was doing a nandroid recover when the phone got stuck. Pulled the battery out. Placed it back in, pressed the power button. Nothing.
Led lights up only when connected to the computer's USB. Battery was charged before Nandroid recover. Used nandroid a lot of times but for some reason, my stone stopped playing nice.
I just removed the battery. Hoping this works. Can someone please post if you got this same issue resolved? I like this phone no matter how slow it goes sometimes. Thanks!
I completely forgot about this thread, sorry guys!
I don't remember exactly what happened, it's been so long... but I do remember I left the phone "inactive" (it's not like i had much of a choice! XD ) for 1 or 2 months, with the battery out. After I got hold of a wall charger, I plugged in the battery, after I plugged in the charger, and what do you know? It worked! It started charging (was 60% charged, fully charged, I unplugged it, but after putting it to charge again just to make sure it was fully loaded before I would flash a new ROM, it was charged up to about 80%, weirdly, so I guess it was a weird battery problem)
I do remember I didn't do anything to it, so I'm not sure what to tell you guys to do, except leave out the battery for a month or so ^^;
Hey all,
Before I even start here, please no snide replies about using the search box on here or anywhere... if the answer is out there, I'm at a loss for the keywords to get it. Fair enough? As FYI, bootloader is (was??) unlocked, rooted, and has cwm recovery.
So I dropped my MB886 cracking the screen (round of applause please) and in the process of disassembling the case to install replacement I tore (severed) the battery connection cable. Fast forward to phone now reassembled with new screen and battery installed --> -->
The phone now has a green LED that will respond with blinks to button certain presses i.e. the simulated battery pull, but the device doesn't show up in lsusb output or device manager. I've read of similar problems where the phone has been brought back, and I've read of the exact problem with no solution. Basically the only two things I've really read that supposedly work are battery pull button sequence and using OEM charger/cable to get battery to take a charge.
Unlike, say the Atrix 2 where the lonely white LED is there to serve as a reminder that it is a hard brick and that's all you're ever going to get from it again, I haven't even read that this is in fact the #1 sign device is now a brick. So could someone verify it is or isn't? I've never tried to access a device this way, but Is JTAG an option?
I don't get why this should be, despite battery issue, it's all simple hardware swapping involved here as the software wasn't touched and was 100% working even with cracked screen.
Thanks for anyone with an answer or the direction to one.
2 things it could be then: you over- or under-tightened the new battery cable screws to where there isn't a good connection with the board. The screws have to provide equal pressure on the positive or negative contacts or otherwise there's a fault in the circuit.
OR
Your new LCD/digitizer is defective OR wasn't seated well.
Since it was working before, and since you didn't break anything else (to your knowledge), those are the two things I would check.
Dr. Orange said:
2 things it could be then: you over- or under-tightened the new battery cable screws to where there isn't a good connection with the board. The screws have to provide equal pressure on the positive or negative contacts or otherwise there's a fault in the circuit.
OR
Your new LCD/digitizer is defective OR wasn't seated well.
Since it was working before, and since you didn't break anything else (to your knowledge), those are the two things I would check.
Click to expand...
Click to collapse
--
hey, thanks for the input. I remember battery connections being snugged when I originally took it apart, and to be honest, short of having a mini torque wrench I don't know I could put them back any closer to that. the digitizer could certainly be either defective or perhaps have a bad connection, and i am certainly willing to test/check for either, however do you know that this would prevent the phone from booting or cause it to only display the green led as a sign of life? something of the "halt on all errors" in pc bios? seems logical that the led would (or could've) been used like the oc speaker and blink out some code relaying you've got a bad O2 sensor or the gas cap isn't tight.
Over tightening can cause problems. So loosen them a bit if it's just-short-of torque wrench tight. I don't know why it does, but I've read people had problems when they over tightened those screws. That green light could be telling you that the battery is connected poorly.
Is there a possibility that the battery is so depleted that it won't charge? For that, you need a factory cable to charge the battery with power off.
Sorry, to clarify, no I just snugged the battery connections when reassembling, I only meant that i don't think i could get them any closer to the way they were originally without aid of something like a torque wrench.
As for battery charge as a potential issue... to be fair, I only have a OEM Moto wall charger and I think the cable I am using is Samsung. Surely the cable itself isn't the weak link in this chain? A car battery on a multimeter reading 12.0 volts is something like 50% charged and about 12.8 volts is looking pretty good, anyone know what I should get out of the 3.8V Li-Ion on a meter?
PS I double checked the both data cable connections to the motherboard, so I doubt just a bad connection is to blame here.
slerros-1.0 said:
Sorry, to clarify, no I just snugged the battery connections when reassembling, I only meant that i don't think i could get them any closer to the way they were originally without aid of something like a torque wrench.
As for battery charge as a potential issue... to be fair, I only have a OEM Moto wall charger and I think the cable I am using is Samsung. Surely the cable itself isn't the weak link in this chain? A car battery on a multimeter reading 12.0 volts is something like 50% charged and about 12.8 volts is looking pretty good, anyone know what I should get out of the 3.8V Li-Ion on a meter?
PS I double checked the both data cable connections to the motherboard, so I doubt just a bad connection is to blame here.
Click to expand...
Click to collapse
You should get from 3.8 to 4.1.
slerros-1.0 said:
As for battery charge as a potential issue... to be fair, I only have a OEM Moto wall charger and I think the cable I am using is Samsung. Surely the cable itself isn't the weak link in this chain?
Click to expand...
Click to collapse
When I say "factory" cable, I'm not talking about the cable that came with the phone. There is a special Motorola cable (that you can even make yourself) that can charge your phone in situations when your phone is normally not willing to accept a charge.
If all else fails, try this: http://forum.xda-developers.com/showthread.php?t=1077414
Yes! This is brilliant and certainly answers a few questions. It'll take me a bit to get this together to try it, but I'll post back when I get a result. Cheers!
slerros-1.0 said:
Yes! This is brilliant and certainly answers a few questions. It'll take me a bit to get this together to try it, but I'll post back when I get a result. Cheers!
Click to expand...
Click to collapse
Scratch my previous answer. Seems I misunderstood what a "factory cable" is for. It can't actually charge your battery, instead it is used to power the phone so that you can flash/diagnose it, even when your battery is dead. Normally, you need a working phone to charge the battery (with the stock "charging cable").
This information may or may not help you. At the very least, using a "factory cable" may allow you to power your phone on, which would tell you whether the problem is your battery or the phone.
quasihellfish said:
Scratch my previous answer. Seems I misunderstood what a "factory cable" is for. It can't actually charge your battery, instead it is used to power the phone so that you can flash/diagnose it, even when your battery is dead. Normally, you need a working phone to charge the battery (with the stock "charging cable").
This information may or may not help you. At the very least, using a "factory cable" may allow you to power your phone on, which would tell you whether the problem is your battery or the phone.
Click to expand...
Click to collapse
well, i'll take it regardless... i've acquired one of these mythical factory cables and it gets me into fastboot and recovery, so i'd wager, even though i haven't seen it, that it would boot all the way. so being that i don't have either the original charger (although have one that's motorola) or cable (samsung), my best bet is probably just find a store that has both an OEM motorola charger and cable even if they're not for the MB886? surely one for a moto x would work to charge battery, no?
or is this like a chicken and egg problem i now have? a catch 22? i can't charge the battery without a working phone, and i can't have a working phone without a charged battery? golly gee, anybody out there with an MB886 want to charge my battery for me? can i just hotwire the battery to a couple of leads from a charger and bypass using the phone as the charging device? at least to give the battery say 15%-20% to get something to happen... like get this rain cloud perpetually parked above me to blow over from above my head for a day or two maybe?
so, with phone plugged in with "factory cable" here's what i get and when... the phone bootloops on the "bootloader unlocked" warning screen if i don't press anything. volume down gets me fastboot, volume up gets me recovery. phone shows up in both and takes commands... so is it possible i just need to restore a nandroid backup, or is the battery charge the better bet now? i would just try the nandroid for $h!ts and giggles, but the last one i have isn't as fresh as i'd like, but is certainly usable if i must.
slerros-1.0 said:
well, i'll take it regardless... i've acquired one of these mythical factory cables and it gets me into fastboot and recovery, so i'd wager, even though i haven't seen it, that it would boot all the way. so being that i don't have either the original charger (although have one that's motorola) or cable (samsung), my best bet is probably just find a store that has both an OEM motorola charger and cable even if they're not for the MB886? surely one for a moto x would work to charge battery, no?
Click to expand...
Click to collapse
Any generic USB charging cable SHOULD be good enough to charge and flash your phone, especially a Motorola cable. I'm currently using an old Blackberry cable for everything. They should be all the same. In rare instances, a cheap cable may give you issues (I think I had a cable from an old Samsung phone that I couldn't get to work right).
I guess just keep trying until you find one that works. Hate to tell you to go spend $20+ on an official Motorola charger...
Regarding your battery, yes you may be in a bit of a pickle. I've never had to do it, but I've read of users who had to short some leads in order to directly charge the battery. Trying searching through the forums, I'm sure the info is here.
---------- Post added at 02:59 PM ---------- Previous post was at 02:55 PM ----------
slerros-1.0 said:
or is this like a chicken and egg problem i now have? a catch 22? i can't charge the battery without a working phone, and i can't have a working phone without a charged battery? golly gee, anybody out there with an MB886 want to charge my battery for me? can i just hotwire the battery to a couple of leads from a charger and bypass using the phone as the charging device? at least to give the battery say 15%-20% to get something to happen... like get this rain cloud perpetually parked above me to blow over from above my head for a day or two maybe?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=892026
All hope is lost, I am now looking for a replacement.
Ok, so here's where I am at with this now... As we're basically talking about any regulated power supply that can put out an excess of (around) 3.8V and 800mA I've opted to use an old ATX computer power supply and wired the mini B USB end of a cable known to have in fact to have charged this very phone... nothing. I have also, for sake of hope, even tried using the wall wort from an iPad (which puts out a cool 5.1V and up to 2.1A). The green LED will shut off after a while of being plugged into said charger, but still no booty action.
As stated before, the phone still works with the factory cable.
So, I gather from this that...
A. some hardware component (i.e. resistor, etc...) on my phones board that is involved in the charging process has gone kaput.
or
B. There is some software flag flipped somewhere that could be unflipped with or without some trickery to what actually is VS what I want the phone to think it's seeing.
Anyone have any thoughts on this or something similar pertaining to B as a course of action?
*update to my update* ... umm, which should now be up to date??
I did a complete wipe of the phone (/system, /data, /data/media, /cache, and /dalvik-cache) and reinstalled the rom... and still nothing.
I know that it has been said that "if your touchpad completely dies, you must have the OEM charger to start it back up". At first this seems true. . .However! I would like to report that twice now, when it was completely dead and displaying the "plug in the original charger for reliable charging or die because im a juice nazi", I was able after about 4 hours of just leaving it alone plugged into a 1amp phone charger, to get it to charge up and boot. This may have already been discovered but I couldn't find mention of it. Just wanted to give hope to someone that might have given up on this.
einstein910 said:
I know that it has been said that "if your touchpad completely dies, you must have the OEM charger to start it back up". At first this seems true. . .However! I would like to report that twice now, when it was completely dead and displaying the "plug in the original charger for reliable charging or die because im a juice nazi", I was able after about 4 hours of just leaving it alone plugged into a 1amp phone charger, to get it to charge up and boot. This may have already been discovered but I couldn't find mention of it. Just wanted to give hope to someone that might have given up on this.
Click to expand...
Click to collapse
So when you connect 1 amp phone charger, does the TP says to connect the original charger? Even if it says to connect the original charger, and leaving it for 4 hours the TP charged is that right???
My problem is when I connect to cell phone charger, it says to connect original charger.
When I connect original charger, the TP stays at 0% even after connecting the charger overnight. I dont know what is the problem? is it charger, is it battery or is it TP..
atrix4nag said:
So when you connect 1 amp phone charger, does the TP says to connect the original charger? Even if it says to connect the original charger, and leaving it for 4 hours the TP charged is that right???
Click to expand...
Click to collapse
Yes.
atrix4nag said:
My problem is when I connect to cell phone charger, it says to connect original charger.
When I connect original charger, the TP stays at 0% even after connecting the charger overnight. I dont know what is the problem? is it charger, is it battery or is it TP..
Click to expand...
Click to collapse
The message will be displayed but it is gradually charging in the background. When it gets enough juice, it will start up and charge faster. In your case it sounds like either your port or battery are damaged somehow. Possibly the charging circuitry but that is unlikely. If you don't have an original charger or touchstone, then your options are limited. They aren't very expensive on ebay though. I would let it charge on a good 1 amp charger for a few days and see what happens then. Mine did the "soft brick" crap once where it was completely unresponsive and ran completely dead and i just charged it for 4 days and forgot about it and when i remembered it, it had powered on and booted. TPs are funny devices. Expect anything and report it if you don't mind. Maybe we can get this sorted out.
einstein910 said:
Yes.
The message will be displayed but it is gradually charging in the background. When it gets enough juice, it will start up and charge faster. In your case it sounds like either your port or battery are damaged somehow. Possibly the charging circuitry but that is unlikely. If you don't have an original charger or touchstone, then your options are limited. They aren't very expensive on ebay though. I would let it charge on a good 1 amp charger for a few days and see what happens then. Mine did the "soft brick" crap once where it was completely unresponsive and ran completely dead and i just charged it for 4 days and forgot about it and when i remembered it, it had powered on and booted. TPs are funny devices. Expect anything and report it if you don't mind. Maybe we can get this sorted out.
Click to expand...
Click to collapse
Thanks for prompt response..
I have original wall charger, and got a new cable from ebay. So I am hoping its equivalent to original charger. How can I debug if the port or battery is damaged.. any idea?
I left it on charge overnight yesterday. It was at 0, in the morning.. I left it on charge today before coming to office. i am expecting it to be at 0, when I go home.. When its connected to charger, its working normally (with 0 battery), but as soon as i remove from charger, it will shutdown..
Morning, when I was charging,
the battery monitor widget app showing Battery flow as "-600mA". I think this should be +ve while charging. the same app was showing status as "Charging AC plugged". I will try to charge my phone with the same cable and charger, if the phone shows +ve current flow, then, its deffinetly should be problem with the battery or touchpad right..
I wil test it in the evening.. and if its problem with battery or touchpad.. i will try to clean the TP and will try again.. Lets see how it goes
Ok so you have the original charger, great! And it boots into android/webos correct? It sounds like your A6 firmware might have crapped out or whatever it does to cause battery issues. Probably not bad battery if this happened rather suddenly, and its not a bad port if its booting and running while plugged, even if its not charging. . .so go here:
http://forum.xda-developers.com/showthread.php?t=2756314
and read it carefully! With this tool, you can do some really cool stuff including re-flashing the A6 battery monitor/control chip. It can (but might not) fix issues like this. Give it a try with a good cable and let me know what happens. Good luck!
einstein910 said:
Ok so you have the original charger, great! And it boots into android/webos correct? It sounds like your A6 firmware might have crapped out or whatever it does to cause battery issues. Probably not bad battery if this happened rather suddenly, and its not a bad port if its booting and running while plugged, even if its not charging. . .so go here:
http://forum.xda-developers.com/showthread.php?t=2756314
and read it carefully! With this tool, you can do some really cool stuff including re-flashing the A6 battery monitor/control chip. It can (but might not) fix issues like this. Give it a try with a good cable and let me know what happens. Good luck!
Click to expand...
Click to collapse
I rebooted to webOS, and TP charged normally.. now i updated to CM11, all good as of now.. Thanks for helping me..
only bad part is i disassembled, before booting to webOS
Aw dude....well hey it happens to the best of us lol. Now u know a lot more about ur tablet and i would still recommend reflashing the A6 and removing webos if u dont use it. Tptoolbox can also be "installed" by renaming the boot image .bin file to uImage.TPtoolbox and placing it in /boot on your android partition. This allows moboot to see it. Off topic i know but i thought you might be interested. Best of luck with the re-assembly!
einstein910 said:
Aw dude....well hey it happens to the best of us lol. Now u know a lot more about ur tablet and i would still recommend reflashing the A6 and removing webos if u dont use it. Tptoolbox can also be "installed" by renaming the boot image .bin file to uImage.TPtoolbox and placing it in /boot on your android partition. This allows moboot to see it. Off topic i know but i thought you might be interested. Best of luck with the re-assembly!
Click to expand...
Click to collapse
You can only install TPToolbox as described if you have removed WebOS.
shumash said:
You can only install TPToolbox as described if you have removed WebOS.
Click to expand...
Click to collapse
why is that?
einstein910 said:
why is that?
Click to expand...
Click to collapse
Because there's not enough room for both, and it's designed to run in the WebOS userspace. Don't even try it; I speak from experience.
einstein910 said:
why is that?
Click to expand...
Click to collapse
Because the boot folder is not big enough with the webOS uImage.
Fixed my Touchpad!
I had the same issue and just wanted to report what worked for me. My touchpad wasn't responding to any button pressing combos and even after sitting on the charger for two days, didn't want to turn on. After some google searching I found my Touchpad might be so dead that the charging circuity might not want to charge the battery and all the fixes were telling me to take apart the Touchpad and charge the battery directly. That's not something I really wanted to do. Then another person suggested to charge the Touchpad with a lower amp charger, so I plugged the Touchpad into an iPhone charger for about an hour. I came back, held the power button and home button - nothing. Tried power, volume up, and home - nothing. But then I held the power button and hit the home button ~10 times and then... the home button started blinking left and right. YES! I took the Touchpad and put it on the original charger, 15 minutes later it had the Low Battery Screen and another 15 minutes later, Cyanogenmod was booting.
I need help. When I try to transfer the Android files to the HP TouchPad using TPtoolbox, Windows says that there is an F drive that I have to format before I use it. In the tutorials, a drive labeled HP TOUCHPAD or something like that shows in Windows, and you can put the Android files inside of the ttinstall folder. Should I format the drive and if so, what format?
Oh sorry, I posted to the wrong thread.
I was searching around for anyone else with this issue and can't find anyone.
I shut down my N6 and place it on my LG wireless charger, then the phone boots up automatically.
I've also tried shutting it down while already on the wireless charger, and the phone still boots up.
I've been able to replicate this on the Nexus Charging Orb.
Does anyone know if there is a solution to allow the phone to remain off?
Thanks in advance!
bump for help
I am pretty sure that for qi to work it has to be powered on.
Sent from my SM-T320 using XDA Free mobile app
What you are experiencing is a Motorola thing. I believe the Droid Turbo does the same (my buddy had it and said it so don't quote me on it). It is not a feature of Qi as both my S4 and Note 3 will charge via Qi and not boot the phone. It actually even has a different graphic for charging even.
Sent from my SM-N900A using Tapatalk
jev3gs said:
What you are experiencing is a Motorola thing.
Click to expand...
Click to collapse
I hope they fix this with an future update. I don't see any benefit of having this occur
after researching this, the poster above is correct. this is a motorola feature/issue. my nexus 5 charges while off without a problem. NO idea who at moto thought this would be a good idea. it sucks actually. sadly, there is no solution that i've found
Robert_W said:
I was searching around for anyone else with this issue and can't find anyone.
I shut down my N6 and place it on my LG wireless charger, then the phone boots up automatically.
I've also tried shutting it down while already on the wireless charger, and the phone still boots up.
I've been able to replicate this on the Nexus Charging Orb.
Does anyone know if there is a solution to allow the phone to remain off?
Thanks in advance!
Click to expand...
Click to collapse
Ive
I've been having the same problem , I have the N4 (LG) orb and the nexus 6. tried all night to get it to charge while the power was off. I still haven't fond any solution to this hopefull thy fix with update because this is a stupid feature.
I can confirm the issue.
Since the battery life on this phone is pretty good I don't often use the wireless charger during the day anymore. However I prefer to use the USB port as little as possible so I'd like to charge up over night with the wireless charger. And since I prefer my phone off overnight this issue has really been deterring me from using the wireless chargers at all.
I also hope this will is software thing so that an update may fix it.
Robert_W said:
I hope they fix this with an future update. I don't see any benefit of having this occur
Click to expand...
Click to collapse
Unlikely. If the phone is off and connecting to Qi turns it on, it means it is managed by firmware, not android / recovery / bootloader etc.. Unlikely you'll see a hardware firmware update ever
rootSU said:
Unlikely. If the phone is off and connecting to Qi turns it on, it means it is managed by firmware, not android / recovery / bootloader etc.. Unlikely you'll see a hardware firmware update ever
Click to expand...
Click to collapse
That is not entirely correct. This is why;
ALL charging, whether it be a dumb power wire, qualcomm quick charge, regular old usb port, or Qi...... requires that the phone actually be ON to control the charging.
Usually, the mode that it is in *looks* like it is off. This is a special boot mode that is specific for charging. It brings the kernel up, and not a whole lot else. If you tap the power button, it'll show you a charging image and the percentage.
What this means is that when it gets to a Qi charger, it actually turns on with a normal boot (or at least *closer* to normal), rather than booting into charging mode.
Now in the kernel commandline, there are a few parameters that get passed in by the bootloader to indicate power up reasons and so forth, so if somebody wouldn't mind..... you can dump the kernel commandline by running 'cat /proc/cmdline' as root. I would like to see that line in all the different boot modes; normal boot, recovery boot, qi charging boot, quickcharge boot, normalcharge boot. You can, of course, edit out your serial numbers and mac addresses. I don't HAVE a qi charger, so I can't get that.
doitright said:
That is not entirely correct. This is why;
ALL charging, whether it be a dumb power wire, qualcomm quick charge, regular old usb port, or Qi...... requires that the phone actually be ON to control the charging.
Usually, the mode that it is in *looks* like it is off. This is a special boot mode that is specific for charging. It brings the kernel up, and not a whole lot else. If you tap the power button, it'll show you a charging image and the percentage.
What this means is that when it gets to a Qi charger, it actually turns on with a normal boot (or at least *closer* to normal), rather than booting into charging mode.
Now in the kernel commandline, there are a few parameters that get passed in by the bootloader to indicate power up reasons and so forth, so if somebody wouldn't mind..... you can dump the kernel commandline by running 'cat /proc/cmdline' as root. I would like to see that line in all the different boot modes; normal boot, recovery boot, qi charging boot, quickcharge boot, normalcharge boot. You can, of course, edit out your serial numbers and mac addresses. I don't HAVE a qi charger, so I can't get that.
Click to expand...
Click to collapse
This is different. When the phone is off and you plug a cable in, it boots to a charging mode, which sometimes uses a Micro kernel in the bootloader or sometimes the main android kernel - depending on the device. This is triggered by receiving current through the USB port. Obviously bootloader and kernel can be updated by ota.
However, the above is not what the OP is describing. He says the phone boots up. The Qi is triggering the phone to boot up and its not booting into this charging mode. What this says to me is that a hardware trigger based on qi connection is triggering firmware to force a boot, rather than the kernel
rootSU said:
This is different. When the phone is off and you plug a cable in, it boots to a charging mode, which sometimes uses a Micro kernel in the bootloader or sometimes the main android kernel - depending on the device.
Click to expand...
Click to collapse
QUALCOMM devices all boot the main kernel.
This is triggered by receiving current through the USB port. Obviously bootloader and kernel can be updated by ota.
Click to expand...
Click to collapse
Or, obviously, also through the Qi charging coil and/or magnetic switch.
However, the above is not what the OP is describing. He says the phone boots up.
Click to expand...
Click to collapse
RIGHT!!!
Which it ALSO does if you plug in the USB wire. It just boots to a different MODE.
The Qi is triggering the phone to boot up and its not booting into this charging mode. What this says to me is that a hardware trigger based on qi connection is triggering firmware to force a boot, rather than the kernel
Click to expand...
Click to collapse
You might want to re-read my last message in this thread involving things like the REASON for a boot up. The boot REASON is passed to the kernel by the bootloader on the kernel commandline. If the Qi is generating a special boot reason (like the USB does), then it is pretty simple to add a catch for that boot reason into the init and take it into CHARGING mode instead of a full Android boot. For example; find the line that effectively reads as "if (bootreason == usbcharge) start_chargemode();" and change it to "if (bootreason == usbcharge || bootreason == qicharge) start_chargemode();"
It is also possible that the boot reason for usb charge and qi charge are actually the same, but that the distinction is made DURING init. I.e., "if (bootreason == charge && charger != qi) start_chargemode()".
Starting to understand?
Thing is, you will likely not get a solution for the simple reason that it doesn't make sense to turn a device off for charging these days, may be your preference, but if you want something like this you will need to do it yourself, there's no real need for something like this for a regular dev to invest the time on it
doitright said:
Starting to understand?
Click to expand...
Click to collapse
Starting to realise how condescending you are. Not really interested in anything you have to say to be honest. Bye.
z0phi3l said:
Thing is, you will likely not get a solution for the simple reason that it doesn't make sense to turn a device off for charging these days, may be your preference, but if you want something like this you will need to do it yourself, there's no real need for something like this for a regular dev to invest the time on it
Click to expand...
Click to collapse
that's your opinion, and in my opinion it's wrong. there's no need to have my phone on when i sleep, and devices charge faster when off. also, my two other Qi devices, Nexus 5 and Nexus 7, charge wirelessly when off JUST FINE. so it's not unreasonable to expect N6 to behave the same way
rootSU said:
Starting to realise how condescending you are. Not really interested in anything you have to say to be honest. Bye.
Click to expand...
Click to collapse
How about this; next time you READ and TRY TO UNDERSTAND before just assuming that everybody besides you is an idiot, then maybe you won't be treated like YOU are the idiot.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
indianajonze said:
that's your opinion, and in my opinion it's wrong. there's no need to have my phone on when i sleep, and devices charge faster when off. also, my two other Qi devices, Nexus 5 and Nexus 7, charge wirelessly when off JUST FINE. so it's not unreasonable to expect N6 to behave the same way
Click to expand...
Click to collapse
Except that.... it is physically impossible for the device to charge when it is entirely off. The PMIC must be turned on, and for that to be on, the SoC must also, which means that the kernel must boot up. The only question is what mode it boots up into.
Fact is that if you boot into full android and turn on AIRPLANE MODE, it won't use any more power than it uses in CHARGER MODE, and it won't interrupt you -- it is *effectively* turned off.
And actually, here is an interesting piece of information for you to learn....
If you boot it to full Android, put the thing in airplane mode, unplug it, and turn the screen off... that will actually yield a lower power consumption from the device than what will happen when it is plugged in and booted to CHARGER mode. The reason is because in charger mode, it ALWAYS keeps one CPU core turned on! When it is unplugged, the charger's kernel wakelock is released, allowing ALL cores to shut down.
doitright said:
How about this; next time you READ and TRY TO UNDERSTAND before just assuming that everybody besides you is an idiot, then maybe you won't be treated like YOU are the idiot
Click to expand...
Click to collapse
Counter offer... Because I never assumed anyone was an idiot and actually since you haven't said anything I didn't know (you just assumed I didn't know anything.) Perhaps YOU should take your own advice before dishing out dumbed down and (although technically correct) incomplete "explanations" in a frankly condescending manor.
You didn't even try to get your head around what I was trying to say before going on the offensive.
I've been a desktop engineer for many years. I understand how hardware triggers the bootloader to hand over to the kernel. Now here I did make an assumption that firmware was involved. That's because I based it on something not dissimilar in my world. Wake on LAN. Now I fully admit that my understanding might be outmoded as its a different technology but you completely omit the fact that firmware layer says between the hardware and the bootloader or kernel. I have already said that I am not sure if the charging mode is a bootloader micro kernel or the android kernel. Different devices work differently here and I don't know which method it uses.
That said, my assumption is that like wake-on-LAN, the hardware firmware controls what is sent to the bootloader or kernel as an instruction. If that's true, no way would Google "fix" that with an OTA as why would they bother making it do that in the first place. Sure, that isn't to say it isn't doable and I never said it wasn't. Just that it would be unlikely to be "fixed"as it is by design.
doitright said:
How about this; next time you READ and TRY TO UNDERSTAND before just assuming that everybody besides you is an idiot, then maybe you won't be treated like YOU are the idiot.
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
Except that.... it is physically impossible for the device to charge when it is entirely off. The PMIC must be turned on, and for that to be on, the SoC must also, which means that the kernel must boot up. The only question is what mode it boots up into.
Fact is that if you boot into full android and turn on AIRPLANE MODE, it won't use any more power than it uses in CHARGER MODE, and it won't interrupt you -- it is *effectively* turned off.
And actually, here is an interesting piece of information for you to learn....
If you boot it to full Android, put the thing in airplane mode, unplug it, and turn the screen off... that will actually yield a lower power consumption from the device than what will happen when it is plugged in and booted to CHARGER mode. The reason is because in charger mode, it ALWAYS keeps one CPU core turned on! When it is unplugged, the charger's kernel wakelock is released, allowing ALL cores to shut down.
Click to expand...
Click to collapse
you're missing the point. there are ways around all of it, including airplane mode, dnd modes if you have lollipop or CM, but these are still more steps than simply turning the phone off. i just want it off. fewer steps = better, and when its off there is zero chance that i forget to turn on one of these modes and be awakened at 3am by some nonsense facebook post. as mentioned earlier, other devices will charge wirelessly while off, so the issue is clearly with the nexus 6.
not sure why you're trying to make excuses here. get a nexus 5 or 7 and then tell me N6 is operating correctly. Those devices will charge while off (however you choose to define that). Whether you approve or not of the way N6 does things is irrelevant to me, but for myself and many others it is a broken situation
rootSU said:
Counter offer... Because I never assumed anyone was an idiot and actually since you haven't said anything I didn't know (you just assumed I didn't know anything.) Perhaps YOU should take your own advice before dishing out dumbed down and (although technically correct) incomplete "explanations" in a frankly condescending manor.
You didn't even try to get your head around what I was trying to say before going on the offensive.
I've been a desktop engineer for many years. I understand how hardware triggers the bootloader to hand over to the kernel. Now here I did make an assumption that firmware was involved. That's because I based it on something not dissimilar in my world. Wake on LAN. Now I fully admit that my understanding might be outmoded as its a different technology but you completely omit the fact that firmware layer says between the hardware and the bootloader or kernel. I have already said that I am not sure if the charging mode is a bootloader micro kernel or the android kernel. Different devices work differently here and I don't know which method it uses.
That said, my assumption is that like wake-on-LAN, the hardware firmware controls what is sent to the bootloader or kernel as an instruction. If that's true, no way would Google "fix" that with an OTA as why would they bother making it do that in the first place. Sure, that isn't to say it isn't doable and I never said it wasn't. Just that it would be unlikely to be "fixed"as it is by design.
Click to expand...
Click to collapse
Lets start over. Ok?
Everything involving the device turning on involves hardware and firmware. You are not being unreasonable in assuming some similarity to WOL. The main difference here is that we actually have more information available regarding the CAUSE of the wake-up. Where the WOL packet gets sent once and its over, a Qi charger *continues* to be connected and supplying power. In addition, the bootloaders on the phone actually provide more information to the kernel than you can get on a desktop/server machine.
At the most basic level, something physical happens that triggers a power up, whether that be a magnetic field received through the Qi coil, a DC current applied to the USB port, or the power button being pressed and sending a current through the 'on' pin of the PMIC.
From there, it begins executing bootloaders in the order PBL --> SBL1 --> SBL2 --> TZ --> back to SBL2 --> SBL3 --> ABOOT.
ABOOT, which carries a LittleKernel "LK" payload, is a multi-bootloader with THREE boot modes; fastboot (part of LK) selected if LK detects VOL- being pressed, boot (standard boot, linux kernel from boot partition) selected if LK detects NO Vol button being pressed, recovery (linux kernel from recovery partition) selected if LK detects VOL+ being pressed. In addition to loading and starting the linux kernel on recovery or boot partition, it sets a number of kernel parameters, indicating various other details, such as, like we've talked about, a charging reason flag.
What I *do not* know, is what the different sets of parameters look like comparing USB charging, Qi charging, and Power button.
Not that we really even NEED to know, since there are other hacks we can use to choose a boot mode.
I.e., the kernel knows when the Qi charger is connected. If there is no difference at all between the flags set by a power-button startup and a Qi charger startup, then we need only check if (a) there is a Qi charger connected during the init, and (b) that the boot reason is NOT "reboot", and use that information to decide to boot into charging mode. Let me explain the not-reboot part: If the phone is placed on the Qi pad from a power off state, it will power on right away with a reason that is not reboot. The user would not even have a chance to press the power button to turn it on, which means that the combination of "normal" boot with the presence of a Qi charger, means that it MUST be a qi-boot. If they then press the power button from charging mode to "turn it on", it will actually BE a reboot, so we can take that to mean to go into a normal boot.
I do agree, fully, that Google/Moto will NOT be changing this behavior in an OTA, since it is clearly "working as intended".... HOWEVER, this *is* a Nexus, and the best part about having a Nexus is that you can hack it to suit yourself. As a result, the discussion on how to change this behavior is still quite valid.
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
DroidGuy321 said:
My phone had been working perfectly fine, as well as charging perfectly fine. Recently, I accidentally let it drop to 0%, which I don't usually do. I went to plug it into the same wall outlet as always, but instead of the usual charge process, the battery icon with the lightning bolt in the middle simply flashes on the screen and then turns off, which happens over and over again.
It should be noted as well that about 3 weeks ago my phone get fairly wet. After that incident, I turned it off till it dried, powered it up, and everything appeared to be totally ok.
Other facts:
-I can safely get into the recovery menu (power + vol down), which is stable, but any menu selections result in the Motorola splash screen for a quick second and then the phone powering down.
-The computer will recognize the connection to the phone.
Attempts to resolve:
-New cable, new usb hub, new wall outlet
-Trickle charge from the computer (same flashing)
-Phone in rice to remove moisture
-Toothbrush cleaning of Micro-usb port (suggestion from another thread)
I'm pulling my hair out, and I am considering prying off the back and replacing the battery. I have searched other threads, but have seen various solutions none of which worked for me. If anybody has any idea how I can fix this please help!!! Thanks in advance.
Click to expand...
Click to collapse
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally: https://www.amazon.com/gp/product/B00S7IBDGW/ref=oh_aui_search_detailpage?ie=UTF8&psc=1.
Also, are you unlocked? If so, what battery percentage does TWRP say?
TheSt33v said:
Either there is something wrong with your battery, or there is something wrong with the USB port. If the USB port is the problem, you can use wireless charging instead. I'm a fan of this one, personally:
Also, are you unlocked? If so, what battery percentage does TWRP say?
Click to expand...
Click to collapse
Thanks for the quick reply. It does seem like a battery problem, however it is just so coincidental that it stopped working after I let the battery drain to 0%, when only hours previously it was in use and charging without any issue at all.
Also, if there was a problem with the micro-usb port, I would think that a computer wouldnt be able to read the phone, but when I plug it in it is recognized as an ADB device.
I have another turbo with a cracked screen, I'm thinking about dissecting both and putting that battery in this phone as a replacement.
And unfortunately I am not unlocked :/.
Update
Well, after some further experimentation, I've gotten it working again. The solution was to charge it for like 5 hours, then let it sit off charge for an hour, and then it would boot... bizarre combination of actions. It has since dies twice and I've had to use this method.
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
DroidGuy321 said:
It is working for now if I don't let the battery drop below like 15%. Seems more like a software or hardware issue to me, and i'm still trying to resolve it, so if anybody has any suggestions please let me know.
Also, what is the best way to re-calibrate the battery, maybe that could help?
Click to expand...
Click to collapse
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
mrkhigh said:
If you note when your battery dies abruptly and you immediately reboot the back light is very poor. Almost flickering.
I think this is a battery issue of not being able to feed enough amperage.
...however. My phone was doing this and after a full clean reflash it has stopped. I question if this is because I am running less apps now. Or if perhaps somehow the battery managed to lose its memory. (Li ion is an odd duck..)
Click to expand...
Click to collapse
Septfox said:
If you can't let the battery go below a certain percentage, it might be an early sign of failure. The voltage might drop suddenly and unexpectedly towards the end of discharge, prompting the phone to emergency-shutdown.
As for calibrating the battery...it depends on who you ask. I would say that running it to shutdown (even if shutdown is "15%") and then charging it to 100% should do it, since that gives the controller a full set of data with which to extrapolate a discharge curve. Clear your cache in recovery, so hopefully the OS will pick up on this to accurately track the battery's actual state.
Get Kernel Adiutor or something similar to check your battery's health, too. If there's something obviously badly wrong, it should report something other than "Good".
Click to expand...
Click to collapse
Thanks for the pointers. So strange, first it died at 40%, then 30% then 15%. Now, it is still dying early but I am no longer facing the issue I originally had, it will show normal charging when off, and boots up right away. Sure hope its not some ticking battery time bomb, its still a relatively new refurb.
I attempted the charge calibration so we shall see if it helps. I also did a factory reset for the hell of it, since I am on stock and can't reflash. Perhaps I'm in the clear, that would be awesome. Still no idea what the issue was in the first place though, which will annoy me to no end.