Related
my battery charge icon was replaced by ClockworkMod and now i can't charge my phone when it is turned off. any solution for this problem? thanks.
I think what you mean is when you shut down it reboots into clockwork? Ive had that happen. If thats the case just select reboot and it turns back on / charges
you can't charge it when it's turned off
Sent from my Liberty using XDA App
xpedro said:
my battery charge icon was replaced by ClockworkMod and now i can't charge my phone when it is turned off. any solution for this problem? thanks.
Click to expand...
Click to collapse
That is how clockwork works but it should not be a problem as your phone is still charging regardless if it's sitting in clockwork or on in Adroid.
sd73ta said:
I think what you mean is when you shut down it reboots into clockwork? Ive had that happen. If thats the case just select reboot and it turns back on / charges
Click to expand...
Click to collapse
it reboots in clockwork only when the usb cable is plugged in ac.
i turn off my phone at night and charge it. that's why it bothers me.
but it seems there's no solution for that. i'd would have to uninstall clockwork, then?
Why don't you just leave your phone on?
or just put it on silent.
ok. i was just wondering if that could be fixed. thanks.
Just unplug the cable before shutting it down, then plug it back in after it is fully shutdown.
phone died
ya my phone died completely in my pocket and didnt have enough power to boot,
but i had the same problem with my old htc 8125 and had a solution ready
some htc phones, (2 that i have) htc aria and htc 8125 cant run without battery because there isnt a direct connection from the usb port to the battery.
the phones OS charges the battery once its booted, so with a dead battery you cant do jack. this just happened to me with aria. before i would just plug it in and the battery icon would pop up. but now its clockworks recovery. left phone plugged in for hours and still nothing. i had a usb cable cut up from when my 8125 did this and it worked for the aria too. so if your aria dies, google how to fix 8125 dead battery problem. basicly you take a usb cable and cut it expose the + and - power cables and touch them direct to the battery + and - for about 5-10 mins to give it a boost of power then boot it up. once booted the issue is gone, till your battery dies again. Im assuming the aria fixed the old problem with the recovery where recovery can run with direct power cause i could get to clockwork all day long with dead battery, but could not get it to boot till i jump started the battery.
that means i won't be able to charge my phone if the battery dies?
(unless i "jump start" the battery?)
magicbyrdman said:
ya my phone died completely in my pocket and didnt have enough power to boot,
but i had the same problem with my old htc 8125 and had a solution ready
some htc phones, (2 that i have) htc aria and htc 8125 cant run without battery because there isnt a direct connection from the usb port to the battery.
the phones OS charges the battery once its booted, so with a dead battery you cant do jack. this just happened to me with aria. before i would just plug it in and the battery icon would pop up. but now its clockworks recovery. left phone plugged in for hours and still nothing. i had a usb cable cut up from when my 8125 did this and it worked for the aria too. so if your aria dies, google how to fix 8125 dead battery problem. basicly you take a usb cable and cut it expose the + and - power cables and touch them direct to the battery + and - for about 5-10 mins to give it a boost of power then boot it up. once booted the issue is gone, till your battery dies again. Im assuming the aria fixed the old problem with the recovery where recovery can run with direct power cause i could get to clockwork all day long with dead battery, but could not get it to boot till i jump started the battery.
Click to expand...
Click to collapse
xpedro said:
that means i won't be able to charge my phone if the battery dies?
(unless i "jump start" the battery?)
Click to expand...
Click to collapse
I'm pretty sure the wall-charge adapter will always charge the phone. It always has full juice to the USB pins whereas a USB host only supplies a minimal current to the device then the device must request more from the host once communications are established (part of the USB specifications).
Attn1 has a procedure of flashing ROMs without flashing CMmod, i did that. Now i have liberated aria rom with stock recovery. It works correct.
Sent from my HTC Liberty using XDA App
i think i'll just wait my battery die and see if i can charge it then.
i hope i won't lose my phone forever. hehe.
I think it should be considered as bug then?
tleung11 said:
I think it should be considered as bug then?
Click to expand...
Click to collapse
No, because even before you flashed clockwork, the phone is never off during charge. If you shut down and plug in, it would boot that big green battery (which was part of the old recovery) and eventually sleep. But it was not off. No Clockwork bug - just a crappy HTC design.
Uninstalling clockwork or patching the phone?
attn1 said:
No, because even before you flashed clockwork, the phone is never off during charge. If you shut down and plug in, it would boot that big green battery (which was part of the old recovery) and eventually sleep. But it was not off. No Clockwork bug - just a crappy HTC design.
Click to expand...
Click to collapse
Sorry, I didn´t see this thread before, and I asked about this issue in others.
Isn´t it possible to run an update using clockwork to change it to work in the normal way, at least just with a black screen, not starting the clockwork recovery... Its just to minimize the probability to make mistakes, the clockwork interface could be dangerous if you don´t know what you are doing...
I´ve seen a "patch" to run live wall papers on Aria: http://forum.xda-developers.com/showthread.php?p=6953168#post6953168
It would be possible to make a similar patch for this case? I´m just wondering...
What if I uninstall the clockwork recovery replacing it with the original?, is it possible?
Is there anyway to change it back to the battery, but leave clockwork on? My mom just got the aria, and I rooted it to flash the sense ROM here. Is there anyway to take off clockworks, or return the battery charge animation on the phone?
The battery charge screen is part of the original recovery and there is no way that I know of to have two recoveries on the same recovery partition, so I'd have to say "no".
This will bring back the battery charging animation instead of clockwork
Attn1 pointed me the way in irc.
Basically, you flash back the stock recovery using unrevoked. Then when you want to use clockwork, you flash it with unrevoked.
http://www.mediafire.com/file/awlgonzr74w711l/recovery.img
Remember, if its stuck at looking for root, press the power button, and let it continue. For me, it would get stuck there, and I didn't realize thats all that was needed for it to be successful.
I tried to load up the new gingerbread roms from my current one. I downloaded its content and tried to install it via clockwork.
I first deleted system, logo, and cache followed up by a restore format. When trying to download the new rom, I was getting a weird error that was stopping me from completing the full installation. So basically was in a chokehold because I didn't have any backup files or another working rom in the sd at that time. I just restarted the phone and it for a few times was stuck on the M screen, but now its just green led when I plug it into the computer usb. When plugging it into the outlet, it imediately turns on stuck on the M screen and shuts off when unplugging as if the battery isnt charging at all.
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
bigshotrob22 said:
Sounds like ur going to have to sbf.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
thats the problem.. i got the X.340 sbf and the program aswell but I cant get into bootloader mode. is there an alternative way to sbf?
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Could be your battery same thing happened to me try using a friends battery your battery could be dead and it no longer charges
Sent from my DROIDX using XDA App
bigshotrob22 said:
Did u pull the battery for 30 seconds and then hold the volume buttons + power to put it n bootloader
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
bootloader is such a rare occurance for me, i just had it come out but it was flashing low battery. the thing is, im not quite sure if its charging if i have it plugged into the computer. when i have it plugged into an outlet, the M splash screen comes up so i'm worried that draining the power..
edit: now it flickers for a split second, am i supposed to hold on to it til something shows up? been like 1 minute
i dont think bricking phone blows your battery. at least i hope it doesnt, was working fine before.
Plug it in without the battery if a question mark comes up you ned to use another battery cuz it won't charge in boot loader and the boot loader should pop up right away hold power volume down and camera button it takes about three seconds
swyped from my DROIDX using XDA App
well its basically the same thing. when plug into the outlet it shows the m splash screen with or without the battery.
when its plugged into the compuiter however, its just flickers once. when it is done with the battery in, the led is on forever
EDIT: OBSERVATION
when on the wall, it is actually charging, but REALLY slowly because of the fact that the splash screen stays on. found this out because i had it in for30 min and then tried to connect mit to my comp with bootload and it loaded for a few minutes with the low battery flashing.
is version 320 the latest?
Okay. so it isnt charging as I though because its not working at all... problem is, I dont know if it truly is a battery defect. If I were to Buy a new battery, how would i know if it is charging if it doesnt boot and just stays stuck on the M logo screen?
perhaps I should by a battery charger where i take the battery out and charge it through there? because my bootloader always gives me the same low battery.
Do you have any friends with the same phone? There is also a macgyver (spelling?) Method of doing this by cutting the USB cable open and attaching the cable ends to the battery. However I would only do this if you're really desperate
i just really need make complete sure that this phone is INFACT dead battery
when not plug, it doesnt turn on what so ever with a white spark on the led.
when plugged nto outlet the logo shows but i isnt charging because it isnt booting
when plugged into the computer it is a solid green which i think represent a dead or a low battery state(can someone back thisup?)
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
raziel36 said:
Your battery is dead, as in drained, but should work fine once you get your phone to a bootable state again. The problem is that, in the state your phone is in, there's no charging capabilities. Bootloader won't do it, neither will sitting at the M logo. So, you just need to find someone with a compatible battery to let you use it to SBF your phone. Then, boot the phone up completely, and let your battery charge to at least 50-60% before trying to install a ROM. Preferably, I'd go with a full charge, just in case you end up in a similar situation again.
This is nothing to freak out over, you'll be fine.. the only problem you have is that your battery has no juice, as confirmed by the low battery warning in the bootloader, when you successfully got it to load.
Click to expand...
Click to collapse
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
There's a usb trick u can try. Google it.
Sent from my DROIDX using XDA App
jinho11050 said:
thanks for the reassuring comment, however, i think i need to bootload.
i accidently did the partition hat formats everything.. cant recall if it was under clockwork because it didnt have the same interface, i was all light blue text with an ok button on the left corner. Anyway, i've completely destroyed the phone as in no roms no factory.
can I possibly get a dock to charge this battery and then get into bootloader for an sbf session
? Even if I did have battery, im pretty sure i just hover at the logo screen
Click to expand...
Click to collapse
You definitely need to use the bootloader, and I was implying that in the first reply(SBF'ing requires going into the bootloader). If you had a stand-alone battery charging cradle/dock, that should do the trick. Just make sure to let the battery charge sufficiently. I've successfully gotten an SBF completed, starting with only 30% battery. SBF takes about 7 minutes on my laptop(not that I've timed it, but I usually light up a smoke when I start the process lol). So, as long as the battery is charged enough to no longer give the "Low Battery" warning in the bootloader, you should be fine.
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
froyli said:
You got your usb cable and put the ends where the battery goes that's how I got mine working try it
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
al the tips or just red for pos and black for neg
Positive and negative google it before you do it
Sent from my DROIDX using XDA App
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
jinho11050 said:
okay im having another issue with bootloader.. the program detecs it but i canot start the process.. am i missing something?
EDIT: finally got sbf working after renaming it.
All my threads have been in a form of technique difficulty question and the answer I get from the community were VERY helpful. thank you everyone
Click to expand...
Click to collapse
Glad you got it working! Nearly everyone on here has needed help, at one point or another, and that's what makes Android so great... the community.
Sent from my DROIDX using XDA App
Ok here's what happened:
1.) Rooted using z4
2.) koush bootstrapped
3.) CWM recovery installed using rom manager
4.) wiped data through cwm and koush
5.) wiped system
6.) installed liberty 1.5
7.) rebooted. Let liberty boot up.
Problem is, she had about 15% battery left upon the start of all this. When i got back into liberty it almost immediately rebooted, and shut off. When i plugged in charging cord connected to computer, green LED came on, which shows me that maybe the battery is charging. Couldnt get power to come back on phone. Wondering if the phone was just too dead to come on or if i've bricked it by not having enough charge?
The woman who owns the phone had to leave suddenly with the phone , so I cant really find out till later tonight if she got it to turn on or not.
One word of advice and then I will help you:
always always always charge your phone before flashing anything.
Now to help you:
There is a way to charge your battery without it being in your phone. Actually there are two; one costs money, and one is fun
Money method: Buy a dock for the battery. It will charge it and youre all set.
Fun free method: this is also referenced as the "macgyver" method. It involves splicing a USB cable and putting the cable ends on your battery. It is not hard but could possibly be dangerous if you can't read instructions. Google it as I don't know the exact wording and I do not want to lead you in the wrong path
I thought I'd clean up the OP for folks who got here with similar issues as me since it seems more common than we'd like.
Scenario:
Phone does not turn on without the charger or USB plugged in.
When plugged in, it boot loops at the Google logo (i.e. turns off at the logo, and reboots) and gives what is beginning to be referred to as the the 'red LED of death'--where the LED just blinks read.
The bootloader is accessible when plugged in. But trying to boot into recovery causes a loop. If you try to enter recovery, the phone has to turn off then boot back into recovery. But turning off means that when it turns on it will loop at the Google logo. So, booting into recovery is NOT an option.
Download mode is also accessible when plugged in.
Since the bootloader is accessible, it is possible to flash the factory image to the phone, however, doing so does not resolve the boot loop, nor does it allow the phone to turn on without being plugged in.
Fixes which have worked for some people
Instructions in this post worked for a couple people. NOTE: you have to be able to get into the bootloader for this to work.
One person who left it in download mode plugged into the PC (which was off) overnight, and somehow the problem was resolved. Thread here.
Here's a post in this thread from a user who was able to get it booting up again by leaving it on the charger for a bit.
You fool.
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: http://forum.xda-developers.com/showthread.php?t=2010312
overhauling said:
Your computer only detects it briefly? perhaps it'll detect it if you boot into Bootloader mode (not sure if you were able to from reading the OP)
Press and hold volume down, volume up, and power until the device boots. If you successfully enter Bootloader mode you can find steps on how to return to stock here: [/QUOTE]
Yeah, it would be nice if...en if I get into the bootloader for a second.
Click to expand...
Click to collapse
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
ntt1409 said:
i am on the same boat. i already contacted CSR anh they will send me a new one. after flash new kernel and start antutu, the n4 crashed and completely dead.
Click to expand...
Click to collapse
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Ulver said:
I'm pretty sure the battery with the lightning bolt means its charging.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, but it's already full charged. Even if I leave it on the charger for a while, it still doesn't start up
KonstantinKeller said:
Tape the power button down so it goes into a power cycle. Leave it until the battery is totally dead. Then plug it into the wall outlet, let it fully charge. Then try turning it on.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would say try this to drain the battery. Then charge it and see what happens.
So how exactly did the phone brick? Just so everyone here knows what not to do. Is it the kernel that caused it since its still in experimental stages?
Sent from my Nexus 4 using xda premium
abnormalreply said:
In sum: I started using the Faux kernel with AOKP. OC'd to 1.6Ghz and started Antutu. Phone crashed and now it doesn't boot. When I plug in the charger, there's the battery icon with the lighting bolt which I think indicates that the battery is dead. But it's not dead, it was around 95% when I started Antutu. So, it's constantly turning on and off showing that battery icon while plugged in, but doesn't start up. Anything I can do about this?
Also, the computer only detects it briefly, before the phone turns off again, so ADB/fastboot/toolkit seems out of the question, because it doesn't stay detected long enough to do anything.
Click to expand...
Click to collapse
Have you tried reflashibg or using your nan droid back up from the recovery console?
Just because our won't not does not mean it is bricked.
It is really ticking me of that many people do not even have our phones and you are exchanging because of ignorance. Surely all these exchanges must impact stock. I know they keep extras but how many?
Stop messing with things you know nothing about until you at least learn..
sent via xda premium with nexus 7
abnormalreply said:
Yeah, it would be nice if I could get into the bootloader :/
But as I mentioned, it 'thinks' the battery is dead so it just keeps turning on and off even if I get into the bootloader for a second.
Click to expand...
Click to collapse
That's the point. It'll turn on and off until the battery is ACTUALLY dead. Then, charge it fully, and try to start it.
Dude this happened to me last night! Same ROM kernel combo! And fired up an tutu after ocing point is this should not be happening just made a thread and seen this here! Freaky! I'm telling u people beware something is up for sure been doing this a long time never seen this before
First if you have an unlocked bootloader, your replacement won't be free. As soon as Google gets it and realizes it's unlocked they will charge you full price for your replacement.
Second, Nexus devices are next to impossible to brick. There is probably a way to reset the device. I would try first unplug the device from your computer or charger and try holding the power button for a full 15-20 seconds. Then try booting into bootloader or recovery. If that doesn't work, try holding volume up and power for 15-20 seconds. If that doesn't work, try volume down and power for 15-20 seconds. And if that one doesn't work try holding all 3 down for 15-20 seconds. This sounds like a problem that would more than likely be fixed by removing the battery and rebooting. Since this doesn't have a removable battery there has to be a built in 'hard reset' that will power cycle the phone.
I am willing to bet there is a way to get this working. I guarantee if I had it here in front of me I could.
Also, like someone else has said before, if you are a not good at diagnosing problems, troubleshooting problems, fixing this kind of stuff on your own and adb/fastboot, it makes no sense to be using experimental software on your device. Especially if you plan on pushing its boundaries by overclocking and running benchmark software. If I were you, after you get this straightened out, wait a while until stuff is more ppolished and tested better.
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Yo hold power down then plug USB in then right after hold all three button .like after u plus in USB while holding power button then at same time hold volume buttons also this is how I got into download mode.....but.....phone was not detected and comp SD there was a driver failure. But yes dude phone was charged. And I had same exact combo as u I mean same exact. This is why it is freaky. Aokp was fine all day then when I flashed faux test kernel and fired up antutu I just had a flash then nothing. Not blaming anyone of course it was me who chose to flash after all this is custom software and I love these guys work just wish I knew what did it ....like what actually did it
Richieboy67 said:
Omg.. you don't need a replacement. Stop trying to load roms and kernals if you do not know how.
sent via xda premium with nexus 7
Click to expand...
Click to collapse
Seriously... thousands of people waiting for the phone to become available, and people who deserve to have their phone bricked are getting 2nds for free.
abnormalreply said:
So, by sheer luck, I was able to get into the bootloader and have it stay on. I was then able to use the toolkit (option 9) to flash the google factory stock image. This completed successfully, and I was also able to re-lock the bootloader, but I still have the same problem as I did before: battery charging icon and constant reboot. So, it's completely stock now and the issue is still there. Would it be reasonable to assume that the issue isn't software and I somehow got a hardware failure?
Click to expand...
Click to collapse
I was able to do the same thing but it would vibrate then see Google for a sec then nothing and back to a blinking red light....dude this is crazy I can't. Believe this happened to another person the same exact way
dammit. And I was just going to try this combo. Guess that's gonna be a no go.
Last ditch effort is to unscrew the two t5 screws at the bottom and do a real battery pull. Probably wont work, but what do you have to lose?
Like the topic says, RSD Lite isn't detecting my Mini. It is detected and drivers installed in Windows 8.1. Difficult to get phone in fastboot mode, but eventually gets there. Any ideas?
Tried a script a found instead, received a bunch of low battery fails. Can't seem to get the phone to charge, not sure how to proceed.
zefyx said:
Tried a script a found instead, received a bunch of low battery fails. Can't seem to get the phone to charge, not sure how to proceed.
Click to expand...
Click to collapse
The best answer for low battery flashing is using a Moto Factory cable...
What difference would that make, the battery would still be drained? It's making it almost impossible to even get into fastboot mode.
zefyx said:
Tried a script a found instead, received a bunch of low battery fails. Can't seem to get the phone to charge, not sure how to proceed.
Click to expand...
Click to collapse
Will it boot to recovery? Also do you have moto device manager installed? If not, install it.
Also try a different usb port
When you plug it into power what does it do?
Topsnake said:
Will it boot to recovery? Also do you have moto device manager installed? If not, install it.
Also try a different usb port
When you plug it into power what does it do?
Click to expand...
Click to collapse
If I don't attempt to boot to recovery but maybe once a day, it will; one time. Device Manager is installed and I've tried all three available USB ports. When I plug it in, nothing happens. The screen stays dark. The only guaranteed way to get the phone up is to hold power and volume up. When these issues first appeared, it would charge while powered off.. sometimes. I baby the phone, definite A-stock. No idea what could have caused it. Rebooted one day and it never progressed further than the Motorola vibration.
Do you have xposed installed? Do you have a custom recovery?
IF so, try flashing something called xposeddisabler.zip from your SD card, then try to boot normally and see if that gets you past the M logo.
Xposed is installed, but I have no custom recovery. I uninstalled Safestrap awhile back to prepare for SunShine and such. That's the most bummer thing about all of this, $25 burning a hole in my pocket to unlock my phone -- something I've waited for since buying my Mini at launch.
I guess the biggest problem I'm facing now is that the device refuses to charge. I can no longer get into recovery. It will however bootup with the power button and using the power+volup. I'm out of ideas. I've found others with this issue, but no one seems to have an answer. I'd really appreciate any helpful feedback.
zefyx said:
Xposed is installed, but I have no custom recovery. I uninstalled Safestrap awhile back to prepare for SunShine and such. That's the most bummer thing about all of this, $25 burning a hole in my pocket to unlock my phone -- something I've waited for since buying my Mini at launch.
I guess the biggest problem I'm facing now is that the device refuses to charge. I can no longer get into recovery. It will however bootup with the power button and using the power+volup. I'm out of ideas. I've found others with this issue, but no one seems to have an answer. I'd really appreciate any helpful feedback.
Click to expand...
Click to collapse
RSD light has known issues on 8.1. You will have to get it into bootloader mode and manually flash it via adb.
zefyx said:
What difference would that make, the battery would still be drained? It's making it almost impossible to even get into fastboot mode.
Click to expand...
Click to collapse
"factory" cable is not the cable that comes with the phone it is a special cable that allows the phone to charge in situations such as yours where the phone will not boot to any stage of the OS.
BladeRunner said:
"factory" cable is not the cable that comes with the phone it is a special cable that allows the phone to charge in situations such as yours where the phone will not boot to any stage of the OS.
Click to expand...
Click to collapse
I dont think the factory cable charges the phone, I believe it bypasses the battery allowing for the phone to powerup straight from the wall/usb power, or flashing when the battery is too low.
there are a couple tutorials on youtube on how to make one using a spare micro usb you have laying around
asuhoops8628 said:
I dont think the factory cable charges the phone, I believe it bypasses the battery allowing for the phone to powerup straight from the wall/usb power, or flashing when the battery is too low.
there are a couple tutorials on youtube on how to make one using a spare micro usb you have laying around
Click to expand...
Click to collapse
you're probably right, but either way it gets you by the "low battery" warnings
Finally got my factory cable. How can I get the phone into fastboot mode with it? It instantly turns on and hangs at the same Moto logo trying to boot into Android whenever connected to the PC.
Got it into fastboot mode once, with the factory cable and went into BP Tools. Was able to charge the phone to 19%, but now I can't get back into fastboot.
Nothing happens when plugging USB into wall or PC with factory cable or normal now either >:|
EDIT: let the phone die, and all is well. Booted into fast boot after letting charge 100% and now I'm just looking for restoration files as sbf is down.
zefyx said:
Nothing happens when plugging USB into wall or PC with factory cable or normal now either >:|
EDIT: let the phone die, and all is well. Booted into fast boot after letting charge 100% and now I'm just looking for restoration files as sbf is down.
Click to expand...
Click to collapse
What FXZ you need, I have a couple of them stored locally... could throw in dropbox if its the correct one.