Rooting woes <waiting for device>. Am now lost...

October 7, 2010

Hi, this (Orange San Francisco) is my first Android phone and I'm determined to root it but after following Paul's great advice and video and any other info I could find I still get < waiting for device >

I am trying this on Ubuntu 9.something. Here's what I've done:

1.Downloaded boot.blade.superboot.mcri.r3.img (from link in Paul's howto)

2.Downloaded fastboot (from link in Paul's howto)

3.Unpacked fastboot

4.Copied boot.blade.superboot.mcri.r3.img to fastboot directory

5.Turned off & unplugged phone, removed battery.

6.Replaced battery, turned on phone while holding 'up'.

7.Got the green android on screen.

8.Plugged in phone to PC

9.In a terminal, cd'd to fastboot directory & entered "./fastboot-linux flash boot boot.blade.superboot.mcri.r3.img"

< waiting for device >

Hmmmm. Not giving up yet...

10.Downloaded & unpacked android-sdk-linux_x86

11.Added "/dir_to/android-sdk-linux_x86/tools" to $PATH

12.Restarted terminal & checked path was ok.

13.Ran "android-sdk-linux_x86/tools/android"

14.Installed:

Android SDK Tools, rev 7

Documentation

SDK Platform Android 2.2, API 8, rev 2

SDK Platform Android 2.1-update1, API 7, rev 2

SDK Platform Android 1.6, API 4, rev 3

SDK Platform Android 1.5, API 3, rev 4

Samples for SDK API 8, rev 1

Samples for SDK API 7, rev 1

Google APIs by Google, Android API 8, rev 2

Market Licensing package, rev 1

15.Rebooted pc (just to be sure)

(retried steps 5+)

5.Turned off & unplugged phone, removed battery.

6.Replaced battery, turned on phone while holding 'up'.

7.Got the green android on screen.

8.Plugged in phone to PC

9.In a terminal, cd'd to fastboot directory & entered "./fastboot-linux flash boot boot.blade.superboot.mcri.r3.img"...

< waiting for device >

I've run out of ideas. Any help greatly appreciated.

Thanks from an Android noob

October 7, 2010

http://android.modaco.com/content/zte-blad...rivers-and-adb/

I had to install USB drivers from here before mine would be seen in Device manager.

October 7, 2010

Hi, this (Orange San Francisco) is my first Android phone and I'm determined to root it but after following Paul's great advice and video and any other info I could find I still get < waiting for device >

I am trying this on Ubuntu 9.something. Here's what I've done:

1.Downloaded boot.blade.superboot.mcri.r3.img (from link in Paul's howto)
2.Downloaded fastboot (from link in Paul's howto)
3.Unpacked fastboot
4.Copied boot.blade.superboot.mcri.r3.img to fastboot directory
5.Turned off & unplugged phone, removed battery.
6.Replaced battery, turned on phone while holding 'up'.
7.Got the green android on screen.
8.Plugged in phone to PC
9.In a terminal, cd'd to fastboot directory & entered "./fastboot-linux flash boot boot.blade.superboot.mcri.r3.img"

< waiting for device >

Hmmmm. Not giving up yet...

10.Downloaded & unpacked android-sdk-linux_x86
11.Added "/dir_to/android-sdk-linux_x86/tools" to $PATH
12.Restarted terminal & checked path was ok.
13.Ran "android-sdk-linux_x86/tools/android"
14.Installed:
Android SDK Tools, rev 7
Documentation
SDK Platform Android 2.2, API 8, rev 2
SDK Platform Android 2.1-update1, API 7, rev 2
SDK Platform Android 1.6, API 4, rev 3
SDK Platform Android 1.5, API 3, rev 4
Samples for SDK API 8, rev 1
Samples for SDK API 7, rev 1
Google APIs by Google, Android API 8, rev 2
Market Licensing package, rev 1

15.Rebooted pc (just to be sure)

(retried steps 5+)
5.Turned off & unplugged phone, removed battery.
6.Replaced battery, turned on phone while holding 'up'.
7.Got the green android on screen.
8.Plugged in phone to PC
9.In a terminal, cd'd to fastboot directory & entered "./fastboot-linux flash boot boot.blade.superboot.mcri.r3.img"...

< waiting for device >

I've run out of ideas. Any help greatly appreciated.
Thanks from an Android noob

If you run "./fastboot-linux devices" do you see any kind of response ?

If you don't get anything back then it means there's no communication between the phone and the PC using the fastboot interface which would be why the flash isn't working.

At which point I'd start by checking the cable and then ideally try a different PC. I'm no expert of Linux so I don't know whether there is are issues with the Blade and Ubuntu but if you try a windows PC you'll definitely need the windows drivers (which are linked to in various places on this board)

October 7, 2010

http://android.modaco.com/content/zte-blad...rivers-and-adb/

I had to install USB drivers from here before mine would be seen in Device manager.

Thanks for the prompt reply.

Aren't these drivers for Windows though? I'm using Ubuntu...

October 7, 2010

Thanks for the prompt reply.

Aren't these drivers for Windows though? I'm using Ubuntu...

DOH!

Sorry - skim read the OP and missed that bit!

October 7, 2010

If you run "./fastboot-linux devices" do you see any kind of response ?

If you don't get anything back then it means there's no communication between the phone and the PC using the fastboot interface which would be why the flash isn't working.
At which point I'd start by checking the cable and then ideally try a different PC. I'm no expert of Linux so I don't know whether there is are issues with the Blade and Ubuntu but if you try a windows PC you'll definitely need the windows drivers (which are linked to in various places on this board)

When I run "./fastboot-linux devices" I just get the command prompt back. I know the cable works as I can 'mount' the phone when it is on normally and copy files to it...

I could wait till I get home and try it on W7 there but I'm at work and too damn impatient to get it rooted! :)

Edited October 7, 2010 by max-lothar

October 7, 2010

If you're on Linux, you need to create a udev filter.

It's pretty simple if you can use a terminal.

Open a terminal, type the command below (after the #)

(you may need to get the right version of vi first, so run this:

#sudo apt-get install vim

select yes if asked, it is just installing vi properly)

#sudo vi /etc/udev/rules.d/51-android.rules

This will ask for your password and then the terminal will become a blank black screen

press ctrl-i

copy and paste (or type) this line into the terminal:

SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"

Now press the escape key. press the colon key (:), type wq and press enter.

You'll go back to a prompt where you have to type the following (again, after the #:

#sudo chmod a+r /etc/udev/rules.d/51-android.rules

When this is executed, you'll be able to run fastboot with it not actually <waiting for device> anymore.

I got this info from: http://developer.android.com/guide/developing/device.html

It was a pain to find, hopefully it helps though - and good to see a Ubuntu user here!

October 7, 2010

If you're on Linux, you need to create a udev filter.

...

I got this info from: http://developer.android.com/guide/developing/device.html

It was a pain to find, hopefully it helps though - and good to see a Ubuntu user here!

Well, well, well - I got it working! I followed your post and it still didn't work. I restarted udev: "sudo restart udev". Still didn't work. Then I tried...

sudo ./fastboot-linux flash boot boot.blade.superboot.mcri.r3.img (from the fastboot dir)

BINGO!!!!!!!!!

To root my phone I had to run the command as root on my pc - how ironic :)

Thanks to all - now I really won't get any work done today!!

October 7, 2010

Ahh yes! root is an easy mistake to make, glad to see it all woks ok though :)

October 7, 2010

Well, well, well - I got it working! I followed your post and it still didn't work. I restarted udev: "sudo restart udev". Still didn't work. Then I tried...

sudo ./fastboot-linux flash boot boot.blade.superboot.mcri.r3.img (from the fastboot dir)

BINGO!!!!!!!!!

To root my phone I had to run the command as root on my pc - how ironic :)

Thanks to all - now I really won't get any work done today!!

You've managed to do better than me, then. I have Ubuntu 10.04 on my home PC and, despite hours of playing around with it on Sunday afternoon, installing the SDK, setting up the udev filter etc etc, simply couldn't get it to work at all! I'm a Linux noob but think I managed to follow various tutorials I found around the web pretty accurately. No success, however, as I couldn't get either fastboot or adb to access the phone. I tried running it as root and that didn't work either! Most frustrating.

My computer is a dual-boot system with a small WinXP installation so I tried this as a last resort - the windows command installed R2 without any problems! I subsequently attempted to upgrade the ROM to R3 using Ubuntu and almost bricked the phone but thankfully, was able to rescue it using WinXP. I really don't like it when things don't work for no apparent reason but I think I'll have to continue to use the WinXP install in future unless I go the ClockworkMod route!

October 7, 2010

I really don't like it when things don't work for no apparent reason but I think I'll have to continue to use the WinXP install in future unless I go the ClockworkMod route!

As Winston Churchill said: "Never, never give up". If I can do it under Ubuntu - I'm sure you can. There's probably just that one diddy thing that's stopping it working. I'm no expert (LOL) as you can tell from my first post but I have (an Android zone-free installation of) Ubuntu 10.04 at home so can try what you've tried so far.

As the Beatles once sang: "we can sort it out"...

October 7, 2010

See this thread for probably the easiest way of modding...

http://android.modaco.com/content/zte-blad...ing-with-no-pc/

Sign In

Rooting woes <waiting for device>. Am now lost...

Recommended Posts

Guest max-lothar

Guest Chillimonster

Guest Matchstick

Guest max-lothar

Guest Chillimonster

Guest max-lothar

Guest steviem

Guest max-lothar

Guest steviem

Guest Maringer

Guest max-lothar

Guest rjm2k

Please sign in to comment

Browse

Activity

Important Information