I am trying to repair my Motorola Atrix HD that is stuck on the AT&T logo and thinking it is a soft brick. I tried to restore everything to factory through the boot menu and safe mode. I tried to connect my Atrix for RSD Lite to flash it but could not pick up my Atrix. Anything suggestions welcome.
What ROM was on the phone before it soft bricked? Is your bootloader unlocked? You have a custom recovery installed?
audit13 said:
What ROM was on the phone before it soft bricked? Is your bootloader unlocked? You have a custom recovery installed?
Click to expand...
Click to collapse
It was on Android 4.1. The bootloader is locked and there is no custom recovery installed. Pretty much everything is stock and never been rooted.
Did you take the 4.1.1 OTA update from ATT? Did you try both 4.1.1 ROMs from here: http://sbf.droid-developers.org/phone.php?device=7?
audit13 said:
Did you take the 4.1.1 OTA update from ATT? Did you try both 4.1.1 ROMs from here: http://sbf.droid-developers.org/phone.php?device=7?
Click to expand...
Click to collapse
I took the OTA. I flashed both 4.1.1 roms from that website and now I tried using RSD and Myth Tools yet nothing. I keep getting stuck at the AT&T logo. I factory reset from recovery as well since I can not get into Android. RSD won't recognize the phone in fastboot and Myth Tools won't flash the phone. I need to add as well that I keep getting:
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
when I use Myth Tools or any other tools. Sometimes the phone would just turn off on it own after leaving the phone on with the AT&T phone.
So your phone is not recognized in fastboot mode at all on your computer? Have you tried another computer?
Have you tried flashing stock with Linux? I'm not sure where a tutorial is but I've used Linux in the past to flash with no issue on other Motorola phones. Sometimes the drivers don't work on windows.
audit13 said:
So your phone is not recognized in fastboot mode at all on your computer? Have you tried another computer?
Click to expand...
Click to collapse
I guess my computer is not recognizing the connection my phone either on normal boot or fastboot. I have not tried it on another computer.
Dr. Orange said:
Have you tried flashing stock with Linux? I'm not sure where a tutorial is but I've used Linux in the past to flash with no issue on other Motorola phones. Sometimes the drivers don't work on windows.
Click to expand...
Click to collapse
I haven't tried flashing stock with Linux. I am not good at flashing stock with Linux that is why I haven't tried.
KieKazami said:
I haven't tried flashing stock with Linux. I am not good at flashing stock with Linux that is why I haven't tried.
Click to expand...
Click to collapse
I found it! If you have Linux, you can use a tool called sbf_flash to flash the .sbf to your atrix HD. There are numerous tutorials about using sbf_flash with Motorola phones.
Your first option should be RSD lite since it's more popular and more easier, but when that doesn't work, use Linux.
KieKazami said:
I guess my computer is not recognizing the connection my phone either on normal boot or fastboot. I have not tried it on another computer.
Click to expand...
Click to collapse
This is on Windows, right? Could always be a driver problem. If so, try uninstalling anything Motorola related from the computer. Maybe even try deleting any "phantom" USB devices from your Device Manager. Reboot.
Then re-install the latest USB drivers from Motorola.
That's all I got
Related
So I got carried away with trying to get rid of that three dot menu button at the bottom of the screen and I've slowly managed to work myself into a really bad problem. I'm not necessarily new to this, I've rooted my Droid 2, Droid 3, and GS3, but this has been more complicated for me.
Anyways, my problem is, I was trying to wipe my phone so that I could flash a ROM. This is because I couldn't access my settings (I overwrote the original in an attempt to get rid of the multitask button). But while I was in CWM I factory reset it but I also accidentally deleted the system. My bootloader is unlocked, but now my phone is on and I can't get into recovery, and I'm assuming it's because the whole system is gone so there's nothing to boot.
Another problem I had (while my phone was able to boot up completely), Android File Transfer wouldn't work, I downloaded a rom for the settings.apk but it wouldn't let me transfer files between my computer and phone. I emailed the .apk to myself but since I couldn't access settings I wasn't able to pick my usual email (although now I'm thinking I should have just used the email I first signed in with). Not as much of a concern but input is still welcome.
I've looked up RUU but it looks like it's not available yet for Verizon. Any possible solutions would be MUCH appreciated.
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I'm stuck on the green HTC logo screen and the red warning about the bootloader. I can't boot into recovery anymore. By the way I'm using a Mac but I do have a PC running Windows 8 if there's solutions I could try
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
xerhoffx said:
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
Click to expand...
Click to collapse
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
n1234d said:
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Click to expand...
Click to collapse
I only have Windows 8 I believe...
xerhoffx said:
I only have Windows 8 I believe...
Click to expand...
Click to collapse
Try a different PC, worked for another guy whose pc wouldn't detect his phone. See if a pc with XP works..
ndulian increase
jingles98 said:
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
Click to expand...
Click to collapse
Where could I find a nandroid for Verizon? I feel like Verizon is the most difficult to find.
FIXED
I was finally able to boot into recovery and thank goodness had a CWM backup. Thanks for your input guys.
Hi:
Just switching from Nexus 5 to Moto X XT 1097 so I´m a little unfamiliar with RSD.
The thing is I´ve tried phone detection in RSD Lite in both windows 8.1 and windows 7 with no luck.
I´ve downloaded drivers, treid different versions of RSD Lite, different ports, different USB cables, done a lot of reading and nothing...so as you can see I´m very frustrated ....
Any help please getting RSD Lite working?
Thanks!
Looking for an answer to this also
You need rsd lite 6.2.4 and moto drivers 6.4.0 . im assumming you have adb all set up on your pc. You will also need mfastboot
shane1 said:
You need rsd lite 6.2.4 and moto drivers 6.4.0 . im assumming you have adb all set up on your pc. You will also need mfastboot
Click to expand...
Click to collapse
No 6.2.4 here...http://rsdlite.com/rsd-lite-download/
Do you have a link & to those drivers, I have the latest installed on Win 8.1
What do i do with mfastboot? I have downloaded it.
I thought you just launched RSD found firmware to flash, plugged in phone, adb mode & flashed?
What is the procedure?
Thanks
http://www.droidrzr.com/index.php/topic/57858-motorola-tools-rsd-lite-usb-driver/
Once they are installed you have to put your phone into fastboot mode for rsd to flash. To make sure your pc sees your phone when in fastboot mode and connected to your pc open cp and type fastboot devices your device should come up. If it sees it then run rsd
shane1 said:
http://www.droidrzr.com/index.php/topic/57858-motorola-tools-rsd-lite-usb-driver/
Once they are installed you have to put your phone into fastboot mode for rsd to flash. To make sure your pc sees your phone when in fastboot mode and connected to your pc open cp and type fastboot devices your device should come up. If it sees it then run rsd
Click to expand...
Click to collapse
Many many thanks sir. That all worked a treat.
I still have one problem that started all this, maybe you can help.....
When I try to get in to stock recovery, i get to the andriod guy laid down & press up/down buttons together for 5/10 sec & then press power button....Nothing happens.
I think my stock recovery is screwed, do you have any ideas how to get it back? Flashing etc?
Thanks Again
I sure your recovery is still there. I have problems getting into it most of the time as well. When andy shows on the screen i think its volume up then power. The timing has to be just right but i can never remember exactly.
shane1 said:
I sure your recovery is still there. I have problems getting into it most of the time as well. When andy shows on the screen i think its volume up then power. The timing has to be just right but i can never remember exactly.
Click to expand...
Click to collapse
Hold power button & press Vol UP, gets in to recovery. Yay It's still there.
Accessing it is different in Lollipop, got that from Moto website.
Thanks again for your help.
Merry Christmas to you
Was running stock 5.0.1 with a decrypted boot.img. Rooted, unlocked, modified build.prop, TWRP, Franco kernel. Lost ability to connect to a PC, so I can't update manually (that's for another conversation). So I need the 5.1 OTA. I unrooted through SuperSu, flashed stock recovery and stock kernel. Did a factory reset. For some reason, my build.prop stayed modified.
The OTA will download, but fails to install...simply saying "error." Any advice on what could be preventing the OTA from installing?? I was hoping this update would fix my device-to-PC connection.
Thanks
ryan4a said:
Was running stock 5.0.1 with a decrypted system.img. Rooted, unlocked, modified build.prop, TWRP, Franco kernel. Lost ability to connect to a PC, so I can't update manually (that's for another conversation). So I need the 5.1 OTA. I unrooted through SuperSu, flashed stock recovery and stock kernel. Did a factory reset. For some reason, my build.prop stayed modified.
The OTA will download, but fails to install...simply saying "error." Any advice on what could be preventing the OTA from installing?? I was hoping this update would fix my device-to-PC connection.
Thanks
Click to expand...
Click to collapse
Flash system.img and userdata.img and reboot.
gee2012 said:
Flash system.img and userdata.img and reboot.
Click to expand...
Click to collapse
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images without a PC or root access? Through stock recovery? Where do I find those files?
ryan4a said:
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images with a PC or root access? Through stock recovery? Where do I find those files?
Click to expand...
Click to collapse
Extract the Google factory image and flash both img`s in fastboot/bootloader, here is a guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
ryan4a said:
I'm probably more of a noob than I should be and may be in over my head. But how exactly would I flash those images with a PC or root access? Through stock recovery? Where do I find those files?
Click to expand...
Click to collapse
You can't. You're pretty screwed to be honest, you'll need to have that other conversation about your USB connection now.
gee2012 said:
Extract the Google factory image and flash both img`s in fastboot/bootloader, here is a guide http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008.
Click to expand...
Click to collapse
Thanks again. But this tutorial says
"Boot it in fastboot(bootloader mode) by pressing and holding Power Button + Volume Down at the same time.
Connect your phone to your PC through your USB cable."
Again, my device is not recognized by any computer, even in fastboot mode. Anyway to do this without a PC?
ryan4a said:
Thanks again. But this tutorial says
"Boot it in fastboot(bootloader mode) by pressing and holding Power Button + Volume Down at the same time.
Connect your phone to your PC through your USB cable."
Again, my device is not recognized by any computer, even in fastboot mode. Anyway to do this without a PC?
Click to expand...
Click to collapse
No, not possible without a pc i`am afraid.
gee2012 said:
No, not possible without a pc i`am afraid.
Click to expand...
Click to collapse
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
ryan4a said:
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
Click to expand...
Click to collapse
Does the phone boot-up? If yes enable usb debugging and you should get connected and the phone is recognised.. Test if the device is recognised in adb with cmd terminal: adb devices and in fastboot/bootloader: fastboot devices.
Try downloading the latest fastboot drivers, I had the same issue and until i installed the latest ones, it wasnt being detected.
ryan4a said:
Thanks for your help. So if I have stock rom, stock recovery, and stock kernel, why would the OTA fail? I thought unrooting and factory reset would have and put everything back to original. I’m just trying to get the update. Do I need to clean up any other system files? Without root access, I can’t change my build.prop back to original, but I wouldn’t think that would have any effect.
I'm on a Nexus 6 by the way.
Click to expand...
Click to collapse
Root modified system in a way that only reflashing the system image will fix. This was changed when lollipop launched.
---------- Post added at 04:34 PM ---------- Previous post was at 04:31 PM ----------
Oh and if you decrypted, you'll have to flash boot img too.
gee2012 said:
Does the phone boot-up? If yes enable usb debugging and you should get connected and the phone is recognised.. Test if the device is recognised in adb with cmd terminal: adb devices and in fastboot/bootloader: fastboot devices.
Click to expand...
Click to collapse
Yes, phone boots up and runs fine. USB debugging is enabled, but still not recognized. At best, I'll get an "unknown device" in device manager. I can't get the Nexus Root Toolkit to recognize it either, even after using the USBDeview.
fkofilee said:
Try downloading the latest fastboot drivers, I had the same issue and until i installed the latest ones, it wasnt being detected.
Click to expand...
Click to collapse
Where would I get the latest fastboot drivers?
ryan4a said:
Yes, phone boots up and runs fine. USB debugging is enabled, but still not recognized. At best, I'll get an "unknown device" in device manager. I can't get the Nexus Root Toolkit to recognize it either, even after using the USBDeview.
Where would I get the latest fastboot drivers?
Click to expand...
Click to collapse
I use the Google usb drivers, they are in the /android-sdk/ Extras/Google/usb_drivers/ folder
Or, try this:
http://forum.xda-developers.com/showthread.php?t=2588979
gee2012 said:
I use the Google usb drivers, they are in the /android-sdk/ Extras/Google/usb_drivers/ folder
Click to expand...
Click to collapse
Thanks. That was one of the first things I tried. I downloaded the updated drives, but not sure I "installed" them. Still not recognizing my device on any PC or Mac. I'm hoping it's not hardware, because it charges fine when connected to a PC.
ryan4a said:
Thanks. That was one of the first things I tried. I downloaded the updated drives, but not sure I "installed" them. Still not recognizing my device on any PC or Mac. I'm hoping it's not hardware, because it charges fine when connected to a PC.
Click to expand...
Click to collapse
Try a different USB cable
cam30era said:
Try a different USB cable
Click to expand...
Click to collapse
That was one of the other things I first tried.
ryan4a said:
That was one of the other things I first tried.
Click to expand...
Click to collapse
Connect the device to the pc, if the phone shows up in device manager uninstall the device, disconnect and the reconnect the phone and choose manual usb driver install and choose the Google usb drivers and all should be ok.
ryan4a said:
I'm hoping it's not hardware, because it charges fine when connected to a PC.
Click to expand...
Click to collapse
Doesnt indicate anything. Data connection uses more USB pins than charging.. Double check your USB port to check for obstruction or pin damage.
Thanks everyone. I've tried multiple cables and multiple computers. Still nothing. At best, I can only get my phone to show up as an "unknown device" in device manager. Then when I manually install the Google drivers, it says "drivers already installed." Or it will install the drivers in like 1 second and finish. But still no connection. I'll keep trying. Otherwise, I'm screwed and will need to keep my non-rooted device on 5.0.1.
When I plug my phone into my computer and run RSD Lite, no phone appears. The operating system of the phone is completely shot, so I need to flash an image of a fresh operating system. I can't do this without being able to use RSD Lite. Motorola Device Manager doesn't seem to be recognizing any available drivers for the device. I really need this phone unbricked. Any answer would be great.
I guess you should leave your phone in bootloader mode.
In order for RSD lite to work, you have to put your device into bootloader mode by holding vol down while you power on. Also, you need to make sure that you have a version of RSD lite that supports it. I've used 6.2.4 successfully.
TheSt33v said:
In order for RSD lite to work, you have to put your device into bootloader mode by holding vol down while you power on. Also, you need to make sure that you have a version of RSD lite that supports it. I've used 6.2.4 successfully.
Click to expand...
Click to collapse
The phone is in bootloader mode and I'm using version 6.2.4.
roll11tide said:
The phone is in bootloader mode and I'm using version 6.2.4.
Click to expand...
Click to collapse
If that's the case, and your phone is still not recognized, there is either a driver problem or a physical connection problem. Assuming you're on Windows, open the device manager. When you plug in the phone, does a new device appear? If so, your problem is likely driver related. If not, there is a problem with the physical connection, which you can troubleshoot by using a different USB port and/or USB cable.
TheSt33v said:
If that's the case, and your phone is still not recognized, there is either a driver problem or a physical connection problem. Assuming you're on Windows, open the device manager. When you plug in the phone, does a new device appear? If so, your problem is likely driver related. If not, there is a problem with the physical connection, which you can troubleshoot by using a different USB port and/or USB cable.
Click to expand...
Click to collapse
I've ttried using different USB ports and cords. Yes, I tried the cord that came with the phone.
roll11tide said:
I've ttried using different USB ports and cords. Yes, I tried the cord that came with the phone.
Click to expand...
Click to collapse
Okay. So if it's in bootloader mode, and absolutely nothing happens in the windows device manager when you plug in the phone (no connected device sound, no unknown device, no known device, no nothing), and you're positive that that USB cable/ports on your PC are working, then it sounds like the USB port on your phone has stopped working, in which case there isn't much you can do. If there is no obvious physical damage, and the phone was never exposed to water, I would try getting Motorola (not Verizon) to replace it. It's free.
TheSt33v said:
Okay. So if it's in bootloader mode, and absolutely nothing happens in the windows device manager when you plug in the phone (no connected device sound, no unknown device, no known device, no nothing), and you're positive that that USB cable/ports on your PC are working, then it sounds like the USB port on your phone has stopped working, in which case there isn't much you can do. If there is no obvious physical damage, and the phone was never exposed to water, I would try getting Motorola (not Verizon) to replace it. It's free.
Click to expand...
Click to collapse
Something happens, it is just recognized as a Fastboot Quark S.
roll11tide said:
Something happens, it is just recognized as a Fastboot Quark S.
Click to expand...
Click to collapse
Hmm. Well then it is set up correctly. If you can't get RSDlite to work, you could always flash your images manually, since basically all RSDlite does is automate the Fastboot commands that are necessary to do this.
1. Install Minimal ADB and Fastboot (or get Fastboot set up in the way of your choice).
2. Unzip the contents of the firmware that you're trying to flash to the same directory as Fastboot.exe.
3. Look for the .bat file that came in the firmware zip and edit it. You should see all of the fastboot commands necessary to flash the firmware.
4. Start fastboot and perform those commands (in the order that they appear) while the phone is in bootloader mode and plugged into the computer.
TheSt33v said:
Hmm. Well then it is set up correctly. If you can't get RSDlite to work, you could always flash your images manually, since basically all RSDlite does is automate the Fastboot commands that are necessary to do this.
1. Install Minimal ADB and Fastboot (or get Fastboot set up in the way of your choice).
2. Unzip the contents of the firmware that you're trying to flash to the same directory as Fastboot.exe.
3. Look for the .bat file that came in the firmware zip and edit it. You should see all of the fastboot commands necessary to flash the firmware.
4. Start fastboot and perform those commands (in the order that they appear) while the phone is in bootloader mode and plugged into the computer.
Click to expand...
Click to collapse
I have tried flashing multiple images with ADB and fastboot, but neither of them work. Sometimes it will flash and it doesn't work, and sometimes the sparsechunks just don't get accepted into the OS. I do not know why this is happening, but I have gotten fastboot to do something to the phone, it just didn't produce any results.
Well...that's bizarre. The only reasons I can think of for a sparsechunk not successfully flashing is that it's not the right image for your model of phone, you're trying to flash an OTA update zip instead of a full firmware zip or you're trying to flash an image that is a lower version than your bootloader's version. I'm not sure what to make of the fact that it sometimes flashes successfully and sometimes does not. However, if flashing all of the images in the full firmware zip does not help you, using RSDlite won't help you either since it does the exact same thing. If I were you, I'd try to get Motorola to replace it. It's really easy to do. You pretty much just fill out a form and they send you a new one. Sorry I can't be of more help.
TheSt33v said:
Well...that's bizarre. The only reasons I can think of for a sparsechunk not successfully flashing is that it's not the right image for your model of phone, you're trying to flash an OTA update zip instead of a full firmware zip or you're trying to flash an image that is a lower version than your bootloader's version. I'm not sure what to make of the fact that it sometimes flashes successfully and sometimes does not. However, if flashing all of the images in the full firmware zip does not help you, using RSDlite won't help you either since it does the exact same thing. If I were you, I'd try to get Motorola to replace it. It's really easy to do. You pretty much just fill out a form and they send you a new one. Sorry I can't be of more help.
Click to expand...
Click to collapse
Thanks, I am already in the process of having Motorola replace the phone as I figured that would be the most logical option. Thanks for all the help! I will leave this thread open as a mystery to the community that hopefully someone will solve and in the process help someone else.
Hey everyone,
I'm afraid that I may have nerfed my phone and I'm hoping someone can help me.
I was trying to root my phone so that I could attempt to fix the bad microphone volume issue. I tried following some directions I found on digitalendpoint dot zendesk dot com. I'm not allowed to post the actaul url.
I got all the way to the end of step 5, but when I issued the "fastboot reboot" command my phone restarted but once it displays the Sony / Xperia logos for a few moments it reboots, and continues this cycle indefinitely. :crying:
I can get my phone back in to fastboot, and when I enter fastboot devices I see my phone listed. However, adb cannot see the device.
Is there any hope???
matthewrt2 said:
Is there any hope???
Click to expand...
Click to collapse
Do you have the correct drivers installed on the PC for your phone?
If the phone still fires up then you can fix it.
The easiest method is to install PC Companion and follow these instructions.
If you are determined to use a custom rom then you might want to read this post
I have the correct drivers. Unfortunately, I can't use PC Companion. I says that my phone has been modified (which is true) and refuses to flash the latest stock rom. However, I was able to restore my phone. I found that both Flashtool and Emma worked.
Didgesteve said:
Do you have the correct drivers installed on the PC for your phone?
If the phone still fires up then you can fix it.
The easiest method is to install PC Companion and follow these instructions.
If you are determined to use a custom rom then you might want to read this post
Click to expand...
Click to collapse
matthewrt2 said:
I have the correct drivers. Unfortunately, I can't use PC Companion. I says that my phone has been modified (which is true) and refuses to flash the latest stock rom. However, I was able to restore my phone. I found that both Flashtool and Emma worked.
Click to expand...
Click to collapse
Deleted