Does anybody know how to root the D3 5.7.960 xt862 with a Mac? I tried using Motofail in Terminal and get the following message:
[*]Press enter to root your phone...
[*]
[*] Waiting for device...
*daemon not running. starting it now on port 5037 *
*daemon started sucessfully *
Then nothing happens.
I've got it running in the right directory, have debugging mode on, install Moto Drivers, what else am I missing.
jwanny10 said:
Does anybody know how to root the D3 5.7.960 xt862 with a Mac? I tried using Motofail in Terminal and get the following message:
[*]Press enter to root your phone...
[*]
[*] Waiting for device...
*daemon not running. starting it now on port 5037 *
*daemon started sucessfully *
Then nothing happens.
I've got it running in the right directory, have debugging mode on, install Moto Drivers, what else am I missing.
Click to expand...
Click to collapse
Try turning debugging on and off and plugging and unplugging the cord from the device. I don't have a mac but I have had that issue on my Linux machine (I don't tinker with android on Windows, no idea of it happens there too)
Sent from my XT860 using xda premium
jwanny10 said:
Does anybody know how to root the D3 5.7.960 xt862 with a Mac? I tried using Motofail in Terminal and get the following message:
[*]Press enter to root your phone...
[*]
[*] Waiting for device...
*daemon not running. starting it now on port 5037 *
*daemon started sucessfully *
Then nothing happens.
I've got it running in the right directory, have debugging mode on, install Moto Drivers, what else am I missing.
Click to expand...
Click to collapse
You do not have to install Moto drivers for a Mac. In fact, where did you get Moto drivers???
doogald said:
You do not have to install Moto drivers for a Mac. In fact, where did you get Moto drivers???
Click to expand...
Click to collapse
Motorola's page apparently. Found a link on a root help site.
Endoroid said:
Try turning debugging on and off and plugging and unplugging the cord from the device. I don't have a mac but I have had that issue on my Linux machine (I don't tinker with android on Windows, no idea of it happens there too)
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
I tried and still the same thing. I only have the Factory USB so I know it's not those. Tried both USB ports, turning on/off debugging. Still same thing. I wish my old PC work! Thanks for the suggestion.
Related
I just got my phone, i test it to see if it works and everything goes well
So now i start the process to unlock bootloader, then i get the token, the .bin and then flash it and it unlocks and restarts
Now i go and shut down the device and now it doesnt want to turn on, the screen is dead and when i connect the cable no light appears, although the device is somehow recognized by my PC when i connect it (Device Manager says My HTC)
I have tried holding power and volume down for 1 minute and nothing happens
Is there somehow to save the phone?
Did you try to longpress power when the phone is connected at pc?
Yes i have tried... In fact, the PC tries to recognize the phone in the Device Manager when i do this, but it fails and after a while it rolls back to Android 1.0 it says (I uninstalled HTC drivers)
Is there like a way to flash something to it while in this way?
When i run
fastboot devices
It says
C:\Users\Administrator\Desktop\fastboot>fastboot devices
???????????? fastboot
Or adb devices
C:\Users\Administrator\Desktop\wao>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Poesini said:
Yes i have tried... In fact, the PC tries to recognize the phone in the Device Manager when i do this, but it fails and after a while it rolls back to Android 1.0 it says (I uninstalled HTC drivers)
Is there like a way to flash something to it while in this way?
Click to expand...
Click to collapse
if it recognizes something when you plug it in there should be way to bring it back. have you tried reinstalling the drivers?
Poesini said:
When i run
fastboot devices
It says
C:\Users\Administrator\Desktop\fastboot>fastboot devices
???????????? fastboot
Or adb devices
C:\Users\Administrator\Desktop\wao>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
But you can boot in fastboot?
And your bootloader is unlocked?
I dont know if its booting into fastboot mode, i just connect the phone to the PC via the cable and thats all it shows
And as far as i know i made it to get my bootloader unlocked i flashed the unlock_code.bin
Poesini said:
I dont know if its booting into fastboot mode, i just connect the phone to the PC via the cable and thats all it shows
And as far as i know i made it to get my bootloader unlocked i flashed the unlock_code.bin
Click to expand...
Click to collapse
Sorry but, your "log" said:
fastboot devices:
?????????? fastboot
Click to expand...
Click to collapse
So you're in fastboot!
Try with a flash or TWRP or CWM and report the log here.
OMG i dont know how i did it i wrote
fastboot reboot
And somehow this time it worked -_-
So your phone now running android?
No prob?
Yeah it showed battery like at 3% i guess it was too low
The thing is that it wouldnt show anything charging and no LED, but now it seems it is
Im gonna charge full and try to flash it again
Thanks !!
Probably your phone was in fastboot so you don't have the led.
However, good!
p.s. For thanking there is the button!
Poesini said:
Yeah it showed battery like at 3% i guess it was too low
The thing is that it wouldnt show anything charging and no LED, but now it seems it is
Im gonna charge full and try to flash it again
Thanks !!
Click to expand...
Click to collapse
i wouldnt charge all the way. maybe 40% and try just in case you get stuck and button combo doesnt work(i havent had it happen but people have been reporting it). you will have to wait for the battery to die to recover and if its 100% that could take a while. also people have reported the led not coming on when battery is fully dead after plugging it in
Yeah i guess so but somehow it didnt show anything and volume down + power didnt work
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
tjsas1 said:
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
Click to expand...
Click to collapse
If your phone is running Android 4.2.2, and you are sure that you got the updated Android SDK tools for this particular version, then on enabling USB debugging, you should get a prompt on your phone "Allow USB debugging?" after connecting and running "adb devices", to which you need to answer "Ok"
If you are not running Android 4.2.2, try using ADB through wifi
rugglez said:
If your phone is running Android 4.2.2, and you are sure that you got the updated Android SDK tools for this particular version, then on enabling USB debugging, you should get a prompt on your phone "Allow USB debugging?" after connecting and running "adb devices", to which you need to answer "Ok"
If you are not running Android 4.2.2, try using ADB through wifi
Click to expand...
Click to collapse
Hi,
Thanks for you reply. The phone is on Android 4.0.4, also tried enabled USB Debugging but no popup is showing.
Hope you can help me
God Bless!
Thanks,
Thomie
Try the following:
1. A different port (are you using a USB 3.0 port? If so, try a USB 2.0 port). Try changing the port anyway even if you were using 2.0 too. You may need for windows to install the driver after changing the port.
2. Restarting adb service by executing "adb kill-server" and "adb start-server"
3. Uninstall the driver from device manager and restarting, and letting windows install the driver on its own
4. If none of these works, reinstall the SDK Tools and in that make sure that "Google USB Driver" is installed.
Lets hope one of these works
tjsas1 said:
Hi,
I am gettings this error when ever I do ADB commands to my SU660. Here what I have tried to do:
1. Restart the Phone and even the PC
2. Change Cable
3. Get latest ADB Tools
Hope some one can help me. I need to upgrade my brother's phone
God Bless!
Thanks,
Thomie
Click to expand...
Click to collapse
Try this one http://forum.xda-developers.com/showthread.php?t=1752074
Maybe your adb is out of date,get a new version
Sent from my XT875 using XDA Premium 4 mobile app
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Li-polymers said:
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Click to expand...
Click to collapse
Have you turned on USB Debugging under Settings>Developer Options>Debugging ??
If you haven't, then turn it on and then try rooting :silly:
Li-polymers said:
HI all,
i cant seems to root my device, i followed doomlords guide strictly, but the command prompt never goes beyond "WAITING FOR DEVICE"
i don't know what the problems is, i believe i have installed all the drivers.
can any one help?
Click to expand...
Click to collapse
"WAITING FOR DEVICE" is sign u have to active this option SETTINGS -> DEVELOPER OPTIONS -> USB Debugging :highfive:
I did that, I'm not that ignorant.
Sent from my C5303 using xda app-developers app
Tried Connecting the USB cable to some other free USB port in your computer??
Or you could try uninstalling the drivers under Device manager...and then reconnecting the USB cable..:fingers-crossed:
By the way, i followed DoomLord tutorial to root the phone. Is it possible to "unroot" the phone then ? Without losing the change ?
In fact i needed to be root to change a system file to fix wifi
ramcool789 said:
Tried Connecting the USB cable to some other free USB port in your computer??
Or you could try uninstalling the drivers under Device manager...and then reconnecting the USB cable..:fingers-crossed:
Click to expand...
Click to collapse
thanks for the tip, re-installing drivers solved the issue. thanks again.
Okay, so I rooted my HTC One M7 AT&T, got S-OFF, tried a couple different ROMs, wanted to put it to GE so i changed the CID, which somehow also changed my hboot to 1.54, and now when i try to return the whole thing to stock using a guide i found online.
i can't get my computer to recognize my phone when it goes to the bootloader. when using the phone normally such as texting, facebook whatever it works, i can get to the internal storage. BUT when i try to do anything with fastboot it will not work. it says <waiting for device> forever.
so basically i dont know what to do. PLEASE HELP ME
jwmccarrier said:
Okay, so I rooted my HTC One M7 AT&T, got S-OFF, tried a couple different ROMs, wanted to put it to GE so i changed the CID, which somehow also changed my hboot to 1.54, and now when i try to return the whole thing to stock using a guide i found online.
i can't get my computer to recognize my phone when it goes to the bootloader. when using the phone normally such as texting, facebook whatever it works, i can get to the internal storage. BUT when i try to do anything with fastboot it will not work. it says <waiting for device> forever.
so basically i dont know what to do. PLEASE HELP ME
Click to expand...
Click to collapse
Make sure you have the correct drivers installed. Have you used HTC Sync Manager before?
yoda1998 said:
Make sure you have the correct drivers installed. Have you used HTC Sync Manager before?
Click to expand...
Click to collapse
I have the correct drivers. I have uninstalled and reinstalled HTC sync manager twice.
sustinc also
jwmccarrier said:
I have the correct drivers. I have uninstalled and reinstalled HTC sync manager twice.
Click to expand...
Click to collapse
do you have the red fastboot USB showing up in your bootloader upon connecting your phone?
yoda1998 said:
do you have the red fastboot USB showing up in your bootloader upon connecting your phone?
Click to expand...
Click to collapse
No, it says fastboot. but not fastboot usb. if i use the volume keys to move up or down it shows fastboot usb, but still does not allow me to use fastboot functions through my computer.
jwmccarrier said:
Okay, so I rooted my HTC One M7 AT&T, got S-OFF, tried a couple different ROMs, wanted to put it to GE so i changed the CID, which somehow also changed my hboot to 1.54, and now when i try to return the whole thing to stock using a guide i found online.
i can't get my computer to recognize my phone when it goes to the bootloader. when using the phone normally such as texting, facebook whatever it works, i can get to the internal storage. BUT when i try to do anything with fastboot it will not work. it says <waiting for device> forever.
so basically i dont know what to do. PLEASE HELP ME
Click to expand...
Click to collapse
What Windows OS are you using?
Are you using USB 3?
Read here
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
bored_stupid said:
What Windows OS are you using?
Are you using USB 3?
Read here
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I am using Windows 8.1
No I am not using USB 3. I tried all ports on my computer, and even a different computer.
jwmccarrier said:
I am using Windows 8.1
No I am not using USB 3. I tried all ports on my computer, and even a different computer.
Click to expand...
Click to collapse
This is how i got the drivers to work on windows 8.1
http://forum.xda-developers.com/showthread.php?p=49131915
use the old (dirty) solution
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Download this >> http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
jwmccarrier said:
I am using Windows 8.1
No I am not using USB 3. I tried all ports on my computer, and even a different computer.
Click to expand...
Click to collapse
Was the other PC runnings windows 8+ too, ( HTC drivers have known connection problems with windows 8. If Windows 7, was the drivers installed correctly
read the link I posted earlier
.
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