wiki.cyanogenmod.com/wiki/Full_Update_Guide_-_Rogers_Dream_911_Patched
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22-26.17
Jun 2 2009, 21:33:16
Code:
./exploid
[1] _+Stopped <signal> ./exploid
Did I do anything wrong in this step?
Code:
You will see a message come up. The exploit has now been setup. Unplug & re-plug in the USB cable to the computer.
Now type in the following commands:
adb shell
rootshell
NOTE: This will prompt for a password, the password is "bacon".
I can't key in the password bacon
I try running cmd as an admin
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd C:\Program Files (x86)\Android\android-sdk\platform-tools
\
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ rootshell
rootshell
rootshell: permission denied
$ rootshell bacon
rootshell bacon
rootshell: permission denied
$ rootshell
rootshell
rootshell: permission denied
$ rootshell: bacon
rootshell: bacon
rootshell:: permission denied
$
I also try the ls command after chmod 777 exploid and the output:
Code:
the output is ls exploid screen_lock_status pattern lock_status
Please see pics for my detailed setup
Well first off I assume the proper drivers are installed? It looks as if your computer isn't detecting your phone
Sent from my HTC Vision using xda premium
Well first off I assume the proper drivers are installed? It looks as if your computer isn't detecting your phone
Click to expand...
Click to collapse
I don't know; I am using the google usb driver and fastboot
Please see attachments for more details
Should I reinstall android sdk?
Well an easy way to check is by typing adb devices and a bunch of numbers should come up saying that you're attached. If not then you may need to reinstall the proper drivers (don't need to reinstal sdk)
Sent from my HTC Vision using xda premium
I reinstall sdk and run the cmd adb device and all I got is a bunch of adb device command
Please see attachment for more details
So did I set it up correctly?
Type adb devices
Sent from my HTC Vision using xda premium
I think the driver is properly installed.
Please see attachment for details
Still not working
horny-sama said:
I think the driver is properly installed.
Please see attachment for details
Still not working
Click to expand...
Click to collapse
yes it looks like the drivers are fine and your computer is seeing your phone no problem.
this is the same proses i used to root my rogers dream and i dint have any issues.
by looking at the pictures you attached did you put exploid and amonra in the same folder as adb is in?
by looking at the pictures you attached did you put exploid and amonra in the same folder as adb is in?
Click to expand...
Click to collapse
I did. Please see attachment for details
Should I format my sd card and start over again?
I'm trying to root a new Droid 4 for a friend. I rooted one a month or so ago using Motofail without any trouble. But it's not working for me this time.
I'm running Windows 7 x64.
I installed the latest Motorola drivers.
I connected the phone to USB cable and let it install all the drivers with USB Debugging enabled and with it disabled. I did both in Charge only and Mass Storage.
One thing that is unusual in this situation is that the phone hasn't been activated with Verizon. I'm doing this so my friend can keep using his old phone until I have this one set up. I've done this in the past with several Droid Razrs but the other Droid 4 I rooted was already activated. If you think this is causing the trouble, let me know.
Model Number: DROID4
System Version: 6.13.215.XT894
Android Version: 2.3.6
Build Number: 6.5.1_167_DR4-1_M-215
I get the following in command prompt when attempting to root:
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
682 KB/s (501292 bytes in 0.717s)
[*] Owning phone...
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
[*] Waiting for phone to reboot.
* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
[*] Cleaning up...
error: device not found
error: device not found
[*] Rebooting...
error: device not found
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
Can anyone help me? I know you can...
Sounds like your Motorola USB drivers are nonexistent or outdated. I would download the latest USB drivers and try it again. You cannot just go by the drivers Windows 7 downloads, you need to download them from the Motorola website.
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
Here's that link:
http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
Thanks for the reply. I downloaded the latest drivers and restarted the computer and now I get this...
[*]
[*] Motofail: Universal Motorola Android Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on Droid 3, Droid Bionic, Droid RAZR, and Droid 4
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest Motorola drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
550 KB/s (501292 bytes in 0.889s)
[*] Owning phone...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting device...
adb server is out of date. killing...
* daemon started successfully *
[*] Waiting for phone to reboot.
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Attemping persistence...
adb server is out of date. killing...
* daemon started successfully *
error: device not found
failed to copy 'su' to '/system/bin/su': Read-only file system
adb server is out of date. killing...
* daemon started successfully *
Unable to chmod /system/bin/su: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
link failed Read-only file system
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
[*] Cleaning up...
adb server is out of date. killing...
* daemon started successfully *
[*] Motofail: Universal Motorola Android Root Exploit
[*] Copyright (c) 2012 Dan Rosenberg (@djrbliss)
[*] Exploit complete.
[*] Rebooting...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error: protocol fault (no status)
[*] Exploit complete!
[*] Press any key to exit.
Press any key to continue . . .
It seems to me to go okay until the phone reboots... at that point the phone trys to activate and I wonder if that's messing up the system. Unless someone has a better solution, I'm going to activate the phone and then try it to see if it will make a difference.
Are you giving the program admin rights?
Sent from my DROID4 using Tapatalk 2
I give admin rights by right-clicking on run.bat and selecting Run as administrator? If yes, I've tried that. The problem isn't specific to Droid 4 as I just now tried rooting a Razr with the same results. It's telling me my "adb server is out of date" and then "device not found".
Can any of you guys tell me how to figure out where the problem is and fix it? It's weird because I've rooted 8 Razrs and 1 D4 before without a problem...
Unroot and reroot.
Sent from my DROID4 using Tapatalk 2
I was never rooted so how can I unroot?
Also make sure your phone is in charge only mode, and the screen is unlocked and on when the process begins.
Yes my phone was in Charge only with screen unlocked.
Thanks to all who are responding!
Try using the Droid 4 utility instead of just Motofail.
Then, like papi was saying, try running the unroot process to get rid of any trace of the exploit. You may want to boot into fastboot and run a data/cache wipe at this point. Then, run the root option again.
I got it guys!!! I copied five files from the Motofail folder: busybox, motofail, run.bat, su and Superuser.apk to my Android-sdk\platform-tools\ folder. I then ran run.bat as an Adminstrator and everything went off without a hitch. Yay!!!
But please, can someone tell me why it worked. I would really like to use this as a learning experience because I just spent a frustrating 8 hours or so fussing with this.
Thanks guys!
mrbuilder
It could have been that somehow the program couldnt find those files in the previous directory
Sent from my DROID4 using Tapatalk 2
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
pm2gonzales said:
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
Click to expand...
Click to collapse
Apparently that error is most commonly seen when there is another version of ADB on that machine. Are you running HTC Sync?
EDIT -- Sorry, i re-read your OP and you've already stated you aren't running HTC Sync. In any case that error still suggests another version of ADB is around somewhere.
pm2gonzales said:
I have a rooted and unlocked bootloader on my N1 running CM7.2, I'm trying to install black rose, but every time I time I try and do so, I keep getting the error "adb server is out of date... killing". Also another message that it can't connect to the device. I've read that some people are suggesting I get the adb fix for users with HTC Sync, but I have NEVER installed HTC Sync. I'm not sure how to get around this. I've update my SDK so I'm not sure what to do.
Click to expand...
Click to collapse
Hmm... Even though you don't have HTC Sync, there must be another instance of adb running around in your system.
Are you using tools for other android phones on your system? If they are installed, then they could be running a version of adb which could cause your problem. So if that's the case, find those processes and kill those.
Check your SYSTEM PATH (Environment variable) to see if there is another path to your adb.exe ( Just use one )
I probably should have mentioned, but I am running Windows 7 64-bit. Also, I've tried uninstalling and reinstalling the android SDK and I got the same result. To visualize, there is a screenshot of the error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have USB Debugging enabled, the phone says FASTBOOT USB. So the phone recognizes the connection at least.
Are you able to run adb commands? Again, are there SDKs for other android phones in your PC?
If you want, try putting adb and fast boot in a fresh directory, add that you path as an env variable, remove the other adb env variable paths(if any), and try again.
Reboot system too just to be sure
Sent from my Nexus One using xda app-developers app
pm2gonzales said:
I probably should have mentioned, but I am running Windows 7 64-bit. Also, I've tried uninstalling and reinstalling the android SDK and I got the same result. To visualize, there is a screenshot of the error:
I have USB Debugging enabled, the phone says FASTBOOT USB. So the phone recognizes the connection at least.
Click to expand...
Click to collapse
You're doing it wrong. You need to be booted into android, not fastboot.
race55 said:
You're doing it wrong. You need to be booted into android, not fastboot.
Click to expand...
Click to collapse
I'm still getting issues. I'm booted in to the system, USB debugging is enabled. I can use adb commands, like if I do adb devices, it shows my device connected. But throughout the installation, it keeps showing errors:
Code:
-------------------------------
| Nexus One BlackRose 120421 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Don't flash any unsigned radio image
Don't flash eclair rom(eg.EPF30), if you are SLCD Nexus One user
If you are using sense rom, please install HTC Sync and turn off that now
Your N1(USB Debugging ON) should be connected to PC
If your device has already installed latest BlackRose, it will enter into Blac
ose menu
Otherwise, BlackRose will be installed or updated automatically
* Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
* Getting device information...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
remote object '/data/local/tmp/ro.build.version.release_tmp' does not exist
adb server is out of date. killing...
* daemon started successfully *
1 KB/s (10 bytes in 0.007s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
* Installing BlackRose
adb server is out of date. killing...
* daemon started successfully *
1461 KB/s (4194304 bytes in 2.802s)
adb server is out of date. killing...
* daemon started successfully *
638 KB/s (26172 bytes in 0.040s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error opening /data/local/tmp/go.lol: No such file or directory
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
< waiting for device >
At which point it boots in to recovery (4EXT).
pm2gonzales said:
I'm still getting issues. I'm booted in to the system, USB debugging is enabled. I can use adb commands, like if I do adb devices, it shows my device connected. But throughout the installation, it keeps showing errors:
Code:
-------------------------------
| Nexus One BlackRose 120421 |
| Made by Lecahel(XDA-dla5244) |
| Dok-Do belongs to KOREA |
-------------------------------
Do at your own risk
Don't flash any unsigned radio image
Don't flash eclair rom(eg.EPF30), if you are SLCD Nexus One user
If you are using sense rom, please install HTC Sync and turn off that now
Your N1(USB Debugging ON) should be connected to PC
If your device has already installed latest BlackRose, it will enter into Blac
ose menu
Otherwise, BlackRose will be installed or updated automatically
* Waiting for device...
adb server is out of date. killing...
* daemon started successfully *
* Getting device information...
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
remote object '/data/local/tmp/ro.build.version.release_tmp' does not exist
adb server is out of date. killing...
* daemon started successfully *
1 KB/s (10 bytes in 0.007s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
* Installing BlackRose
adb server is out of date. killing...
* daemon started successfully *
1461 KB/s (4194304 bytes in 2.802s)
adb server is out of date. killing...
* daemon started successfully *
638 KB/s (26172 bytes in 0.040s)
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
error opening /data/local/tmp/go.lol: No such file or directory
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
adb server is out of date. killing...
* daemon started successfully *
< waiting for device >
At which point it boots in to recovery (4EXT).
Click to expand...
Click to collapse
open terminal, in which you run a random adb command. keep that window open and now try running the installer
Verstuurd van mijn GT-I9000 met Tapatalk
race55 said:
open terminal, in which you run a random adb command. keep that window open and now try running the installer
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
Same result :/. I don't understand what the problem could be, I can push apps and run adb commands just fine.
pm2gonzales said:
Same result :/. I don't understand what the problem could be, I can push apps and run adb commands just fine.
Click to expand...
Click to collapse
Blackrose installer is terrible. Try using the manual method, worked for me back in the day
Verstuurd van mijn GT-I9000 met Tapatalk
race55 said:
Blackrose installer is terrible. Try using the manual method, worked for me back in the day
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
With the manual method, I get this:
Code:
C:\blackrosemanual>fastboot flash hboot hboot_blackrose.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.229s
C:\blackrosemanual>
To confirm, I am in Fastboot mode as per README instructions.
pm2gonzales said:
With the manual method, I get this:
Code:
C:\blackrosemanual>fastboot flash hboot hboot_blackrose.nb0
sending 'hboot' (512 KB)...
OKAY [ 0.087s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.229s
C:\blackrosemanual>
To confirm, I am in Fastboot mode as per README instructions.
Click to expand...
Click to collapse
Did you fastboot boot the .lol file?
Verstuurd van mijn GT-I9000 met Tapatalk
race55 said:
Did you fastboot boot the .lol file?
Verstuurd van mijn GT-I9000 met Tapatalk
Click to expand...
Click to collapse
Yes, received the EXACT SAME error message.
Okay, I finally got it to work. I just kept trying and trying repeatedly until it actually worked. I think it had something to do with my android sdk or maybe the adb drivers because adb commands only work like 50% of the time. The 50% that it doesn't work, I keep getting those "adb server out of date" errors. But I finally got it at least.
try running Blackrose with other ROM, or you should install HTC Sync for your PC, i can't run Blackrose with CM7.2 too
Hi Guys,
Been having a bit of trouble connecting phone via ADB. I can get the connection to work, but it takes a bit of TLC and sometimes a sledgehammer.
Thought we could compile a list of ADB troubleshooting techniques?
If you have any further suggestions, please share.
c:\Fastboot>adb reboot recovery
* daemon not running. starting it now *
* daemon started successfully *
error: device offline
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Resolution: Reboot device
c:\Fastboot>adb reboot recovery
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Click to expand...
Click to collapse
Resolution: Kill all adb.exe processes from task manager and rerun the command. May need to do this a few times.
Edit: I should mention that I'm using adb.exe on Windows 8.1