• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Recovery Flash

benwalburn

benwalburn

Android Enthusiast
I'm trying to flash CWM onto my warp but it's giving me a lot of trouble. I'm using Ubuntu 11.10. I flashed it fairly easily on my old warp, but this one won't work.

After a lot of playing around with adb kill/start-server and sudo su I am able to reboot into the bootloader. At this point, I run the command "fastboot flash recovery QuietCwmRecovery-beta2.img" and it gives me an error about the file being too large.
I tried it several times, and eventually renamed the recovery to "recovery.img" and tried flashing again. This time, I don't get an error, but it still won't flash. It acts like it's flashing, but hangs forever.

Is anyone else getting this issue or know how to fix this?
 
Just a couple suggestions. First, it looks like you're trying to flash Quietstorm's ver of CWM. I would hold off doing that until hroark gets his version updated and publishes download links again. It contains functionality that Quietstorm's version doesn't have plus all new roms should be made to work with hroark's ver of CWM. The other thing may or may not apply since you mentioned sudo su. I'm pretty sure I had to use sudo when running the flashboot flash recovery command. (I do not use sudo su for this) It seems to hang if I don't.
 
JBrd400 said:
Just a couple suggestions. First, it looks like you're trying to flash Quietstorm's ver of CWM. I would hold off doing that until hroark gets his version updated and publishes download links again. It contains functionality that Quietstorm's version doesn't have plus all new roms should be made to work with hroark's ver of CWM. The other thing may or may not apply since you mentioned sudo su. I'm pretty sure I had to use sudo when running the flashboot flash recovery command. (I do not use sudo su for this) It seems to hang if I don't.
Click to expand...

I might as well. It's not flashing anyways.
 
no, fastboot won't flash. I get two errors now when checking fastboot devices
The first is if I don't use sudo, I get "no permissions fastboot"
The second is if I do use it, I get "???????????? fastboot" and if I try flashing anything, fastboot says <waiting for device>
 
Ah. I remember that pain.. Try killing and starting adb manually, so do:

sudo adb kill-server
sudo adb start-server

That *should* fix it
 
So are you running as root and does "adb devices" identify your phone?

Edit: I mean are you currently running as root? (sudo su -) You're trying various things so I'm trying to get an idea of where you're at now.
 
Alright, I just went through the process with my phone and here's what I did. Make sure you cd to the folder containing adb so you don't have to put the full path to it at each step. This also assumes you're using hroark's ver of CWM.

1. Switch to root
sudo su -

2. Double-check the phone is identified again. If not, kill/start adb server.
adb devices

adb kill-server (only if necessary)
adb start-server (only if necessary)

3. Reboot into bootloader
adb reboot bootloader

4. Flash the recovery partition. Edit the command line below with the path to your recovery.img file.
fastboot flash recovery <path to cwm .img file>/recovery.img

5. Reboot out of bootloader.
fastboot reboot
 
JBrd400 said:
Alright, I just went through the process with my phone and here's what I did. Make sure you cd to the folder containing adb so you don't have to put the full path to it at each step. This also assumes you're using hroark's ver of CWM.

1. Switch to root
sudo su -

2. Double-check the phone is identified again. If not, kill/start adb server.
adb devices

adb kill-server (only if necessary)
adb start-server (only if necessary)

3. Reboot into bootloader
adb reboot bootloader

4. Flash the recovery partition. Edit the command line below with the path to your recovery.img file.
fastboot flash recovery <path to cwm .img file>/recovery.img

5. Reboot out of bootloader.
fastboot reboot
Click to expand...

Sorry, but that is exactly what I did.
I get an error that says "waiting for device". If I use "fastboot devices" the computer detects the phone but didn't recognize what it is

Sent from my DROIDX using Tapatalk 2 Beta-4
 
Alright, just wanted to be absolutely sure you were using the same process. Out of curiosity, did you create an 51-android.rules file? If not, you might give it a shot. I think you have to restart udev once the change is made. (or reboot)

Using Hardware Devices | Android Developers

FWIW, this is what I have in mine:

SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
 
I heard about that before but couldn't find any information on it. I made the file and pushed it to /etc/udev/rules.d and chmoded it as directed.
I don't have the warp today, so I'll try it tomorrow asap and report back. Thank you
 
zte_usb_driver.tar.gz

There's all the rules.d files you need.. it's the official rules from the phone itself and if you read the readme it'll show you how to install them using that nifty included .sh file
 
Unfortunately, my attempt didn't work. My laptop charger crapped out on me, so I'm computerless for a few days. But I'll try that when the charger gets here

Sent from my DROIDX using Tapatalk 2 Beta-4
 
Oh, that's a bummer. Well, hopefully you'll be able to flash CWM once your system is up and running again.
 
Thank you Snake X, that worked. Now I have cwm and the fix flashed

Sent from my DROIDX using Tapatalk 2 Beta-5
 
You must log in or register to reply here.
Back
Top Bottom