Database Users

[Q] softbricked with no info

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.

[Q] Not recognized by computer, Red dot of death

Ok so:
Had CM 10.2 nothing else crazy (unlocked/rooted)
One day wifi started acting up (kept dropping) and USB started not being recognized.
Decided that maybe software might be acting up, switched to PA 3.99RC2: FUll Wipe, reinstall
Next day riding out to a meeting phone starts rebooting randomly while running Google maps and music
Keeps locking up and rebooting
Getting really hot
Turn phone off, go to meeting
Phone will not turn back on (solid red dot by usb)
Go home
Recovery no go, phone will not charge on wall or USB charging at all.
Red dot comes on when plugged into wall then turns off after about 30min, plugging/unplugging turns the solid red dot on again.
Put on wireless charger, for an hour
Phone boots up, at 60% charge
USB only charges phone does not send any kind of signal that it is there, no windows sound, nothing in device manager
No charging light at all, but the icon shows as charging.
Have airdroid installed, might try stock google, but it looks like something hardware related.
Has anyone experienced something similar?
Since I don't have ADB working how do I return to stock? (I presume unpackage the distro, airdroid them over, and then install individually?)
I called Google and they say that if they deem that the phone works, not only will they keep the phone I sent them, but they will also charge me for another nexus 4, this is kinda BS and wiht the Nexus 5 around the corner it seems even more BS.
Not sure what to do, as I have about another 1.5 weeks of warranty left. The USB seems jacked up but I am not sure if there are other diagnostics to confirm.

Slappy00 said:
Ok so:
Had CM 10.2 nothing else crazy (unlocked/rooted)
One day wifi started acting up (kept dropping) and USB started not being recognized.
Decided that maybe software might be acting up, switched to PA 3.99RC2: FUll Wipe, reinstall
Next day riding out to a meeting phone starts rebooting randomly while running Google maps and music
Keeps locking up and rebooting
Getting really hot
Turn phone off, go to meeting
Phone will not turn back on (solid red dot by usb)
Go home
Recovery no go, phone will not charge on wall or USB charging at all.
Red dot comes on when plugged into wall then turns off after about 30min, plugging/unplugging turns the solid red dot on again.
Put on wireless charger, for an hour
Phone boots up, at 60% charge
USB only charges phone does not send any kind of signal that it is there, no windows sound, nothing in device manager
No charging light at all, but the icon shows as charging.
Have airdroid installed, might try stock google, but it looks like something hardware related.
Has anyone experienced something similar?
Since I don't have ADB working how do I return to stock? (I presume unpackage the distro, airdroid them over, and then install individually?)
I called Google and they say that if they deem that the phone works, not only will they keep the phone I sent them, but they will also charge me for another nexus 4, this is kinda BS and wiht the Nexus 5 around the corner it seems even more BS.
Not sure what to do, as I have about another 1.5 weeks of warranty left. The USB seems jacked up but I am not sure if there are other diagnostics to confirm.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post...I'd return it all to stock and RMA it.

mrhiab said:
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post...I'd return it all to stock and RMA it.
Click to expand...
Click to collapse
Thanks for the tip, I was just wondering how this sort of malfunction happens. I never really used the USB port after I got wireless charging, so maybe some light dropping? I dunno

[Q] N7 Failure

Had my N7 for well over a year, rooted, unlocked bootloader, all of a sudden it wont turn on... If I plug it in I get a blue screen, unplugged nothing..
Any Idea's out there?

mojimmy said:
Had my N7 for well over a year, rooted, unlocked bootloader, all of a sudden it wont turn on... If I plug it in I get a blue screen, unplugged nothing..
Any Idea's out there?
Click to expand...
Click to collapse
Try opening the back panel of your nexus and unplug and replug the battery.

Leonhan said:
Try opening the back panel of your nexus and unplug and replug the battery.
Click to expand...
Click to collapse
That did it...I usually just thump it on the side and it works...N7 flaw, thanks for your help..

I was reimaging my device from 4.4 back to 4.3 (since Kit Kit broke flash videos). Stupid me, I told it NOT to wipe my user data (even though I backed everything up, including the internal storage device). When it rebooted, the X logo was there, but it never would boot up. I'm assuming because it was because I should have wiped data. Oh, and it was fully charged before I did the reimage to 4.3.
Well, I tried to reboot it (did the reset) to try and get into the bootloader which I did. I wipe the cache only and then rebooted and that was it. Blank screen and nothing else. I can't tell if it's turned on or off. Plugging the charger into the wall outlet doesn't elicit any type of response on the screen. Usually, the screen turns on if it's already on or else, if it's off, you get the battery icon. Neither one happens.
The screen is blank (even when I press and hold power+vol up+vol down. I've hooked it up to the PC to see if I could hear at least the sound when it powers down on the reset and it does indeed do that. Then, it connects and then I get a different sound and the PC says it cannot identify the USB device connected when before all of this happened, it was working just fine (had to since I JUST used the N7 tools to flash back to 4.3).
I've also left it hooked up to the original wall charger for over an hour and nothing. Screen is still blank and never comes on no matter what I do.
I've also opened the back up (hopefully they can't tell if I've done this or not) and unplugged the batter, waited and plugged it back in. Still nothing.
I've uninstalled all the drivers, rebooted and tried it again. After it installed the drivers, still the same issue. It worked for almost a year. Luckily, I purchased the N7 on January of 2013, so I'm still under warranty.
Here's the problem: I unlocked the bootloader. Will this void the warranty? Am I hosed if I try to RMA it? I cannot get connected back to to an fastboot oem lock on it. N7 toolkit is useless (well, NOW it is since I have a non-functioning device), so I cannot do anything there.
I'm just trying to see if there is anything else I can do or is the N7 fubar'd? If so, does this mean they won't be able to keep my data (which is fine by me)? I would hate for them to boot it up and see the unlocked icon on the screen and then come back at me for money.

Was the problem hardware or software?

Okay so here's the story.
I was running pacman 4.3 nightly roms on my tablet.
At some points id have this weird issue where out of nowhere I would start bootlooping (and bc of some weird issue i couldnt boot into recovery from the bootloader unless i was plugged in to a pc. idk it was weird. the bootloader was like 3.13 or whatever)
anyway, yesterday my battery drained completetly and I would do what I would normally do, plug in to my pc, boot into the bootloader, boot into recovery and let it charge a little bit, then i would reboot into the system. but this time it would die during the splashscreen, so that was weird. Anyway, I eventually got it past the splashcreen onto my homescreen and my battery was apparently at 0 percent and then it would just die even tho I was plugged in.
i could leave my tablet in recovery for a while without being plugged in which was weird.
Anyway I tried flashing a newbootloader. 4.23 or something and it successfully flashed, now it wont boot up. fancy paperweight in my hands lol
lsusb command on my linuxbox gives me nothing. RIP nexus7, its been real.

oh and i did everything through adb
and before it died, whenever i plugged it in to usb or my power adapter, some strange sounds came from inside the tablet, like static lol
update, i had it plugged in and not even the charging screen was coming up so i was just there holding the power and volume buttons then the charging screen came up and went away. hmmmmm
The usb cable works fine for file transfers/being detected on my linuxbox on my s3 and evo so its not the port or cable
another update.
charging screen now comes up and stays on for a while. guess its an issue with a port on the tablet, but whenever i power it on or try to get to the bootloader the screen goes black for a second then back to the charging screen. so Im guessing this tablet is done for and shouldnt bother trying to fix the port?

deleted.

Is it still under warranty (less than a year old from when you purchased it)? If so, RMA the sucker. That's what I did and they replaced the motherboard for me.

RSD Lite not detecting Mini

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.