Ok my buddy has an atrix 4g for ATT. he 'said' he was in cwm and loading a rom and now its softbricked. though i am familiar with droid, after reading recovery threads and everything, im still unsure of my resolution. most threads tell me i need an unlocked bootloader, others say not to flash if you were on this version. Honestly i have no idea if the BL is locked, what version or update he was on. at the moment it says failed to boot, starting RSD mode, battery is too low to flash.
A. will it charge while it says that or how should i charge it in this state?
B. after it does charge, what should i flash to it?
I apologize that i dont have much information. you have no idea how long it took me to find the power button lol. I appreciate any and all suggestions. Thanks
You definitely need to get more information from him before you can do anything. If his bootloader wasn't unlocked, then he was likely trying to flash one of the P-Roms like Greyblur or Gingerblur, in which case your solution will be a lot messier since the only way I remember accessing recovery back then was by using Tenfar's CWM app that reset it to recovery w/ a wall charger.
As for charging the phone, I don't recommend keeping it on and plugged in, in the chance that it doesn't charge and you are left with a dead battery. When the phone is completely off and you plug the charger in, do you see the charging battery?
When the phone is plugged into the wall charger it boots up automatically and says failed to boot 1, starting rsd, battery too low to flash. If I plug it into my pc the green power light turns on but nothing else happens. I never get any pictures on screen. No battery and no motorola logo. He was on 2.3.4 but he took his sd so I couldn't see what he was trying to flash. I will try to get more info
Sent from my DROID3 using XDA App
Same thing happened to me, and I can assure you it doesn't charge in that state. I have to find a way to charge the battery now... It is 0% dead. I hope I can use RSD Lite to fix it when it is charged.
alright, what happened was his battery was too low to finish the flash. it died halfway through, and now the phone is in some sort of limbo state that is just completely unusable.
but, if you have a spare USB cable you can fix this.
http://www.youtube.com/watch?v=EQ6JNCvIe8k
just watch that video, and let your phone charge for about half an hour to 45 minutes. after that, reflash the pudding .sbf with rsdlite (unless you can boot into recovery, then you can just reflash any ROM)
If you can boot the phone into recovery by holding the volume down key when powering on, then simply find the alien rom, save onto your SD card from the PC, then install in recovery...then you should be able to reboot into a working phone and charge. If you can't boot into recovery, and the phone is stuck on the "starting rsd protocol" screen, than...I think its a paper weight, but I could be wrong.
Although this problem could probably be fixed by an earlier post, I'm curious....
what would happen if you plugged it into the wall charger, let it boot up into the boot loop, then pulled the battery, left it out for 30 seconds, then put it back in. (this is without unplugging it from the wall charger). Does it allow the phone to stay off and charge, or does it still automatically boot up? Just curious.
im gonna look at the youtube video. ive got a D3 and i saw where a kid had cut a usb cable and made something work for 30 minutes and was able to flash again, but i was def trying to avoid that lol. also, there is no loop really. it doesnt restart, it just sits there. when the battery is pulled, it still stays on the same screen and never powers off until the charger is removed. i may see if i can get a new battery. i really apprecaite the feedback
Phalanx7621 said:
Although this problem could probably be fixed by an earlier post, I'm curious....
what would happen if you plugged it into the wall charger, let it boot up into the boot loop, then pulled the battery, left it out for 30 seconds, then put it back in. (this is without unplugging it from the wall charger). Does it allow the phone to stay off and charge, or does it still automatically boot up? Just curious.
Click to expand...
Click to collapse
It will not charge in this state
well my only option at this moment is to try the usb trick. im trying to strip the wire and hook it to the connector on the phone and then just smash teh battery on top of it, but i have no idicator light, so i dont know if its charging. would it charge if i tape/rig/solder it to the battery itself and not have it in the phone? i really dont wanna try a wall outlet charger
I am going to splice a cable and report back with results. My only other option is to charge the battery in my friend's Droid X
If that fails, to AT&T I go.
i havent been able to get it to charge through the usb using the red and black wires. i was very careful and have a decent set of tools to work with. he can buy the external battery charger for $30 if he'd like. im not really sure what else to do at this point.
Related
Let me give you the run down. I recently bricked my phone trying a 2.3.320 SBF update which got stuck on the M logo. I followed steps as on rootzwiki and got my phone working again, with the new 2.3.320 update. I backed up my cricket APN so the reflash wasn't to bad. I use Droid Overclock at low volts running 1.2Ghz. I have done so for months...never had an issue....ran smooth and fast.
After the new SBF update and re-rooting and running my usual overclock settings, my phone got a lil warmer then usual. I was removing bloat at this point, nothing else. I could not get it to boot into the homescreen...I thought this was unusual as I did not delete any important files ( just bloat ). So, I restarted it, so I thought.
I can not even get it to turn on and after several hours on the charger, It will not turn on! I can get into bootloader but all it states is
Batter Low
Cannot Program
When it's plugged into the USB on my computer, the LED light turns solid green and stays green unless I unplug it. I can not turn it on nor boot into recovery. Only thing I can do is load bootloader and get that exact same message everytime.
My phone is in mint condition. Nothing less then perfect....until today, until I loaded the new 2.3.320 using RSD Lite. Whats going on with my phone? Is it a goner? I will be heading to the VZW store for a brand new battery but I don't think it is the case.
Ideas? Anyone? Sad, sad day for my X...
I think the problem may be that you accidently removed the files necessary for it to charge. If you knew someone else that had the same phone, you could try charging your battery in his phone. That could possibly work.
It had 70% charge when I turned it off to reboot it the first time.
Wierdest thing, as I was reading your post...CWM just started up out of no where and out of excitment, I grabbed my phone and hit the camera button on accident and it rebooted, past the M logo but got stuck on the Droid animation! I had my chance to flash it back to a working nandroid and missed it.
Something wierd is going on here...
If you pull the battery, put it in, then plug it in you should go right to CWM. Keep playing with it until you make it in. I know my phone won't boot up (dead battery), but still gets to CWM.
Might have to jump start it
If the battery is too dead you'll either have to borrow a battery or cut a USB cable to 'jump start' it. I found a post with pictures on how to do it for mine, or look for one of my old posts where I describe it a little.
Use the wall charger. I have the same problem except when my phones dead it wont charge over a computer USB cause its not getting the correct voltage for it to charge. Try that if that's not the case then use another battery and sbf.
Sent from my DROIDX using XDA App
i have unlocked my atrix fine, then failed to flash gingerbread, and so tried to flash back to the original tmobile 2.2.2, but during the sbf flash through terminal, it just stopped dead, then after a while rebooted the phone, and now it does nothing. except the green charge light comes on when plugged in via usb. the power button appears to do nothing, so i cant boot back into fastboot or RSD. help pleeease XD
*EDIT* i have just rebooted with fastboot after many tries to boot failed 4, which is ok i can deal with that, but also "battery to low to flash"
is the phone charging when the green light is on, even when it cant boot? if so thats fine and i'll delete the thread. many thanks
ishamm said:
i have unlocked my atrix fine, then failed to flash gingerbread, and so tried to flash back to the original tmobile 2.2.2, but during the sbf flash through terminal, it just stopped dead, then after a while rebooted the phone, and now it does nothing. except the green charge light comes on when plugged in via usb. the power button appears to do nothing, so i cant boot back into fastboot or RSD. help pleeease XD
*EDIT* i have just rebooted with fastboot after many tries to boot failed 4, which is ok i can deal with that, but also "battery to low to flash"
is the phone charging when the green light is on, even when it cant boot? if so thats fine and i'll delete the thread. many thanks
Click to expand...
Click to collapse
First Rule, always charge your battery to the full before flashing.
Second Rule, always read the instructions carefully beforehand. Most importantly the warnings.
Third Rule, always follow the steps exactly as described.
Fourth Rule, if u face any hiccups or problems please describe in detail. Which version of Atrix, which country, how were u flashing, how did u unlock, what steps did u follow.
tbh i didnt realise that the phone couldnt charge while in fast boot, never even crossed my mind to check. im ok getting the phone out of RSD etc, and am aware of all the warnings, i suppose the real issue here is that when i plug the phone in, it boots up to the fail to boot/RSD screen, and wont charge. is there any way i can force it not to try to boot? thanks
Unfortunately, this sounds like the classic bricking situation. However, more details are required to be sure. To start:
What GB file did you use to upgrade from froyo?
What exactly is your error message?
Sent from my MB860 using XDA App
Buy an external battery charger so you can charge your battery. You can still flash ROMs when you have a fully charge battery using RSD Lite.
i tried to upgrade to GB with an orange sbf, since it seems from other forums tmobile people had had success with it. for whatever reason mine failed at the end, leaving me with RSD mode, then when i tried to flash back to the tmobile sbf from the Original sbf thread, the process just stopped part way through (it had worked fine before, with the same method) and again left me with RSD, but with low charge this time. is there no way around this without buying a charging station? i'd like to save money if possible, and with shipping the phone would be out of action for days, not ideal, though of course if its between that and an argument with tmobile about unlocking/waranty, i'll spend the £20 XD thanks
ishamm said:
i tried to upgrade to GB with an orange sbf, since it seems from other forums tmobile people had had success with it. for whatever reason mine failed at the end, leaving me with RSD mode, then when i tried to flash back to the tmobile sbf from the Original sbf thread, the process just stopped part way through (it had worked fine before, with the same method) and again left me with RSD, but with low charge this time. is there no way around this without buying a charging station? i'd like to save money if possible, and with shipping the phone would be out of action for days, not ideal, though of course if its between that and an argument with tmobile about unlocking/waranty, i'll spend the £20 XD thanks
Click to expand...
Click to collapse
If you have a spare USB cable you can use it to charge the battery. Search on YouTube for how to charge any phone without a charger
Sent from my MB860 using xda premium
do you mean charging with a stripped down usb cable? would that not cause the phone to still boot up? the videos i have seen before clamp the wires between the battery and phone terminals, i would of thought this would make the phone boot as it is, without charging since i only have RSD mode? if im wrong, thatd be great, but if not ive found a battery only charger for £0.99 XD
ishamm said:
do you mean charging with a stripped down usb cable? would that not cause the phone to still boot up? the videos i have seen before clamp the wires between the battery and phone terminals, i would of thought this would make the phone boot as it is, without charging since i only have RSD mode? if im wrong, thatd be great, but if not ive found a battery only charger for £0.99 XD
Click to expand...
Click to collapse
from what i remember someone posting who was in your situation, they did this and it gave their battery a charge. it's worth a try right?
Used my device last night to do some reading and the battery was about half full.
Went to use it tonight, won't turn on. Thought something killed the battery, so charged it for an hour.
Held power button, nothing. Tried volume up then power, nothing. Finally got it to do something by pressing volume down and power. It comes up to the Odin screen.
I've never rooted/loaded any roms or anything, so anybody have any idea what the heck happened or how to get my device back to normal?
Thanks for any help.
Have you used the stock AC wall-charger to charge it up?
Yes, it's charging now while I am reading all about using Odin and downloading a stock firmware...
Not that I know what I'm doing <grin> I'm hoping it powers up after I charge it some more before I go mucking with it...
Thanks, Samsung! I'd much rather be having this fun instead of reading a book. Where is the damn ICS update? Honeycomb sucks.
I would let the battery go flat which is the same as removing the battery on a phone and hope that allows you to re-boot normally after charging then I would try a factory reset to clear any problems before going down the re-flashing road.
Well, looks like letting the battery go flat is my only option because after charging all night it now won't even go into Odin Mode.
Do you have a general idea how long it will take for the battery to die since there are no indicators? Should I expect days/weeks?
Sure wish I could pull the battery or use the paperclip trick like on other devices. This thing is a very expensive (imported) paperweight right now.
EDIT: Any idea why I couldn't get to the boot loader (volume up + power) to reset the device but the Odin mode worked?? I don't think it's the button, this device has been coddled. Just sits on my nightstand until I read a little at night and put it back.
Uh 九千., I'd thank you twice if I could.
So I go to pull the usb cable and wall charger behind my nightstand to bring to work and it's NOT the original charger. I forgot it came with the European power adapter so I had to use a generic USB charger.
I grabbed the Samsung wall plug from my 8.9 and now it shows the battery with a yellow exclamation mark. I'll try charging it and go from there.
Very strange, considering I've been using the other usb wall charger since I bought the device maybe six months ago...
I'm hoping for the best!
EDIT: IT BOOTED and it's charging... What a relief. Thanks for the help guys.
EDIT 2: So before, it was NOT charging... It got so low that only the Samsung wall charger could get it going??? Very strange.
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
CallMeAria said:
Trying to fix a family members xt907 so here's the situation which has been nothing but headaches for me:
1. The Phone is only 7 months old and the bootloader is unlocked so warranty exchange is out of the question. She let the battery run down until the phone died. Then without charging the phone she turned it back on and it died again. From that point she couldn't get it to charge or turn back on while plugged in. At this point she brought it to me.
2. I got the phone and did a soft reset which finally got the charging screen to come up (showed the actual charging icon and the fill meter would flash up and then back down periodically). Problem is it never went past 0% after charging all night. I went ahead and tried to power it up thinking maybe it was just a glitch with the charging screen. Phone wouldnt boot. Just stuck at the Motorola logo. Another soft reset and the phone finally boots but now the battery icon showed a '?' and status showed '5% - Unknown'.
3. Performed a factory reset. No change. So I used RSD to flash the stock 4.1.2 firmware/kernel/modem, etc... What I found strange here is that despite the low battery Fastboot AP showed battery as OK, not low and let me flash (bootloader is unlocked, not sure if that affects low battery flashing or if that safeguard just wasnt built into the M).
4. So phone boots back up and shows 7% battery. Plugging in the charger at first notice has no affect. Battery stats shows '7% - Not Charging'. So I unplug the charger and the low battery warning pops up. Plug it back in and phone still doesnt register as charging, but says 'Not Charging'. Then I notice that the lockscreen shows '7% Charging'. Weird. Regardless of all that, the battery was not charging. The percentage never goes up and after reboots the percentage will remain the same. The battery does slowly discharge on the charger if I have it powered on.
5. I tried flashing a couple different roms before flashing back to stock and all had the same problem. I've formated /system hoping it was a problem with the OS but it didnt help. All of these charging tests were performed with the stock Motorola usb cable plugged into the wall charger. I tested the Motorola charger against my S4 to verify it works and also tried my Samsung charger on the Razr and it made no difference. However, booting the Razr M up with the Samsung charger resulted in the '?' in the battery icon and a notification in the status bar saying something about a CommServer starting. This notification was persistant and could not be dismissed. If I reboot the phone with the Motorola charger or no charger then that notification and the '?' dont appear.
6. I should also point out that I opened the phone up and disconnected the battery from the board and discharged the board. As a last resort I completely removed the battery and peeled back the tape on the bottom of the battery to expose the + and - terminals on the battery and wired it up to a stripped down charger and left it for a bit. Upon putting the battery back in the phone it showed a charge of 30% but still had all the same problems otherwise. So the battery is capable of taking a charge, it just wont take it through the phone, whether powered on or off. Thats what leads me to believe the battery itself is not bad. Its not practical for her to pull the battery to charge it, obviously. The phone detects the cable being plugged in and I can transfer files via usb cable to/from the computer no problem, so I'm fairly sure the Micro usb port is ok. Just refuses to charge.
A little lengthy but I'm at my wits end on this and really dont want to have her buy a $50 battery and then its a problem with the phone. I dont usually get stumped when it comes to fixing something but this one really has me. So if anybody can shed some light on this situation it would be greatly appreciated.
Click to expand...
Click to collapse
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
jco23 said:
I presumed you tried to wipe the battery stats via the battery calibration app? not that I think it would make a difference. another option is enable/disable USB debugging. you could also try charging into a PC or a different outlet (perhaps that outlet does not provide a good current)?
not really sure, just tossing out some ideas...
Click to expand...
Click to collapse
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Doubt it. However, the issue seems to be with the hardware, and since it is not a software issue, Motorola could honor the warranty. Last resort would be to unroot and see if you can get an exchange.
Sent from my XT907 using xda app-developers app
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
CallMeAria said:
I actually installed cwm recovery just to wipe battery stats. Im assuming it works the same way but I'll give the app a try. I'll try anything at this point. Tried your other ideas already though and didnt make any difference.
I appreciate the input. I'll give that app a try and see if it does something different from wiping battery stats in recovery.
Click to expand...
Click to collapse
Did you ever find a solution? I am having the same issues with my xt907.
What did you have it plugged in to? The fact that it said it was not charging indicates maybe you didn't have enough power coming through the charging port...
Sent from my XT907 using Tapatalk 4 Beta
uthkuknwme said:
have you tried a non moto cable? the one that came with my fone was total crap, would continuously connect and disconnect when i hooked it up to my comp or try to charge it, so i tried my old samsung cable and i didnt have any disconnect problems at all. just a suggestion
Click to expand...
Click to collapse
yeah I tried my Samsung cable as well.
jgramkow said:
Did you ever find a solution? I am having the same issues with my xt907.
Click to expand...
Click to collapse
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
CallMeAria said:
yeah I tried my Samsung cable as well.
No. Verizon finally sent her a refurb replacement. I got the battery to charge up by taking it out and rigging a charger to it. But the phone still wouldnt accept a charge with the battery back in and it lost the charge it did have 2-3 times faster than normal. Battery Stats also showed the battery was showing a pretty decent voltage so unless the battery itself has a low charge circuit that gets tripped I'd be hesitant to point to the battery itself. And the charger port transfered files just fine and the phone recognized when the charger was plugged in (would go from 'discharging' to 'not charging'. So yeah, I was left stumped. Hopefully somebody else can get this solved for you.
Click to expand...
Click to collapse
Just an update: I ended up buying a replacement battery and it fixed the charging issue. I rsd back to stock. Then, playing around with it, I booted to bootloader and selected "Factory" and it immediately booted back to stock, but, the battery had a "?" again. Ready to throw the damn phone against the wall, I rebooted it. The "?" is mysteriously gone. What is the "Factory" setting? I think I tried it before, but had CM10.1 installed. My theory is that this "factory" boot from bootloader actually soft bricked the phone. Either that or the issue was truly the battery and simply replacing it fixed things. I am up and running now, cm10.1 is flawless, imho. Thanks for the quick reply and I hope this helps anyone with similar issues.
Beware of the "Factory" bootloader option...........
Here we go again. Upon a reboot into recovery. Recovery is twrp 2.5. What I notice is the motorola boot img takes an extremely long time (2 minutes) to turn off and cyanogenmod to begin. Could there be something corrupt in the bootloader? Is there any way to reload the bootloader on this device? Anyone have any ideas? Could it be Recovery?
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.