Root [Guide][Drivers][Root][Kernel][Recovery] How to install for the ZTE Awe

[cooldudezach]

Root Disclaimer

====================================
I'm adding this, so that people don't get mad at me. This guide does need to be rewritten. I wrote it before active development on this device, and some of the methods have changed so that it is easier. I will rewrite it, but it will have to wait until next week, when my festivities and family engagements are over. Happy Holidays!
====================================

(Taken from the "All Things Root Guide)

Spoiler

Quick note / disclaimer: as always, you are ultimately responsible for any root-related activities on your phone.

You should understand not only the benefits of rooting, but also any possible consequences (voided warranty, boot-loops, bricking, etc.) that might occur as a result of your root-related actions.

I am not liable for any root actions you might undertake as a result of information used from this guide.

Reading, researching, understanding, and carefully following the published steps and instructions can go a long way towards helping to make your rooting efforts a successful one.

Install the drivers:
Connect your phone to your computer via USB

Windows:

Install PDANet.
During installation, just keep hitting "Next" or "OK" until you get to the "Instalation Succeeded!" screen.
Uncheck all of the checkboxes, and click "Finish"

Linux (any variant that uses apt)

Open a terminal window.
Type these commands:

sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot

For Mac / Other Linux Variants:

Connect your phone to your computer via USB

On phone:
A menu should appear, select "Install driver"
On computer:
Navigate to the drive labeled "USB_Driver" (which is the phone)

Open the folder corresponding to your operating system.

Linux:
Extract the USB_Driver.tar.gz somewhere on your computer.
Open a terminal window.
Type these commands:

cd /path/to/USB_Driver
chmod 777 install uninstall
./install

Mac:
I need somebody who uses Mac to help here. There is a folder for it, I just am not familiar with how it works. Sorry ^_^;

Install Stuff:

Download Root software:

Superuser: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
CWM Recovery(img): Dev-Host - cwm-6.0.3.7-publicbeta1.img - The Ultimate Free File Hosting / File Sharing Service
CWM Recovery (flashable zip): Dev-Host - cwm-6.0.3.7-publicbeta1.zip - The Ultimate Free File Hosting / File Sharing Service
Overclocked Kernel: http://androidforums.com/awe-all-things-root/804147-kernel-oc-rbheromax-rb3-kernel.html

Place all files into the same directory.
Rename the Superuser zip to "Superuser.zip".
Rename the CWM Recovery img to "cwm.img".
Rename the CWM Recovery zip to "cwm.zip".
Rename the Overclocked Kernel to "ockernel.zip".

Connect your phone to your computer via USB.
Open a terminal window in the same directory.

Boot into temporary CWM Recovery:

With the device OFF, hold down the VOLUME UP button, and press the power button.
Hold the VOLUME UP button until a screen that says FTM appears.
In the terminal window, type:

adb reboot-bootloader

To check if you are in fastboot mode:
(Linux users may need to append the following fastboot commands with "sudo".)

fastboot devices

Your device should appear like this:

12ab345c    fastboot

You need to check/install the drivers if it shows something like this:
http://androidforums.com/awe-all-things-root/803847-fastboot-drivers.html

????????    fastboot

Boot into CWM Recovery:

fastboot boot cwm.img

At this point, your device should boot into cwm recovery.
You may need to run this command before you run the previous one.
(You may need to start over at "Install Stuff")
(I am not sure if it comes pre unlocked or not, and if not, whether you can use fastboot boot)

fastboot oem unlock

Once you are in CWM Recovery, use the volume keys to navigate up/down and the power button to select options.

This guide assumes that you have not installed CWM Recovery onto your device.
It also assumes that you do not have the files you wish to install on your SD card.
If you wish, you can install the files from your SD card rather than installing with sideloading.
Make sure you know where the files are located on the SD card (A great place is a folder at the root of the SD card!).
Select "install zip from /sdcard" instead of "install zip from sideload".
At that point, it will bring up a list of the files/folders on your SD card.
Navigate to where you put the file and select it with the Power button.
It will bring up another screen asking if you really wish to install it.
Select the option that says "Yes".

NOTE: It is recommended that you perform a nandroid backup before installing any of these files.
To perform a nandroid:

Select "backup and restore"
Select "backup"

CWM will now perform a complete backup of your phone.
Backups are located at /sdcard/clockworkmod/backups
Make sure you have enough space on you sdcard before you backup Total space you need is dependent on how many apps you have installed.

Now to install stuff!
Navigate back to the main menu.
Select "install zip"

To install Superuser:

Select "install zip from sideload"
In the terminal window on your computer, type:

adb sideload Superuser.zip

The file will upload to your device and install Superuser.apk and the su binary.
Congratulations, at this point you device is now rooted!

To install CWM Recovery:

Select "install zip from sideload"
In the terminal window on your computer, type:

adb sideload cwm.zip

The file will upload and install CWM Recovery.
You can now boot into CWM Recovery normally.
While the phone is off, hold VOLUME DOWN and press the power button.

To install Overclocked Kernel:

Select "install zip from sideload"
In the terminal window on your computer, type:

adb sideload ockernel.zip

The file will upload and install the overclocked kernel.
You can now download an app from the Play store to overclock your CPU!

If you wish to use Cydia Impactor to root, and install Superuser from the Play store:

Make sure you enable USB Debugging on your phone!
The USB Debugging option is located at Settings -> Developer Options -> Slide Toggle to On -> Enable USB Debugging -> OK

Download Cydia Impactor: Cydia Impactor
Extract and Open Cydia Impactor
Make sure that the dropdown says "# drop SuperSU su to /system/xbin/su"
Press "Start"
Your device should now be rooted, but it only has the superSU binary on it, you still need Superuser!

 

[ayi]

Each time I go into recovery (holding volume down, and power on), I get into android recovery which is completely different from CWM recovery screen.

I can never reach the CWM recovery unless if it's from temporary fastboot.

Lastly OC kernel either isn't install or not working help!

PS: each time it says installation complete.

 

[tli]

@cooldudezach, thanks for the guide! Good job!

Before sideloading and rooting, would probably be a good opportunity to do a Nandroid backup of the phone's stock setup... just in case.

 

[JoshuaAwe]

Root Disclaimer
(Taken from the "All Things Root Guide)

Spoiler

Quick note / disclaimer: as always, you are ultimately responsible for any root-related activities on your phone.

You should understand not only the benefits of rooting, but also any possible consequences (voided warranty, boot-loops, bricking, etc.) that might occur as a result of your root-related actions.

I am not liable for any root actions you might undertake as a result of information used from this guide.

Reading, researching, understanding, and carefully following the published steps and instructions can go a long way towards helping to make your rooting efforts a successful one.

Install the drivers:
Connect your phone to your computer via USB

On phone:
A menu should appear, select "Install driver"
On computer:
Navigate to the drive labeled "USB_Driver" (which is the phone)

Open the folder corresponding to your operating system.
Windows:
Linux:
For Ubuntu/Fedora/Mint:
For other:
Mac:
Install Stuff:
Download Root software:
Boot into temporary CWM Recovery:
Once you are in CWM Recovery, use the volume keys to navigate up/down and the power button to select options.
Select "install zip"

To install Superuser:
To install CWM Recovery:
To install Overclocked Kernel:
If you wish to use Cydia Impactor to root, and install Superuser from the Play store:

I had to enable debugging mode before it could root my phone with Cydia Impactor.

 

[cooldudezach]

I had to enable debugging mode before it could root my phone with Cydia Impactor.

Oh right! Thanks! That's the first thing I do when I get a new phone/install a new ROM, so I didn't even think about it.

 

[cooldudezach]

@cooldudezach, thanks for the guide! Good job!

Before sideloading and rooting, would probably be a good opportunity to do a Nandroid backup of the phone's stock setup... just in case.

Probably a good idea. I'll add it to the guide.

I DO have a completely stock CWM image I will be unploading and adding to this guide as well, for those who want a true stock image.
It has the stock recovery, boot, and system. It's in the pre-activated state fresh after a factory reset, which was annoying to get in the proper order. If I had known how to get fastboot without android, it would have been tons better.

 

[cooldudezach]

Each time I go into recovery (holding volume down, and power on), I get into android recovery which is completely different from CWM recovery screen.

I can never reach the CWM recovery unless if it's from temporary fastboot.

Lastly OC kernel either isn't install or not working help!

PS: each time it says installation complete.

Are you actually installing CWM recovery, or opening it via fastboot? To install it permanently, you still have to sideload the CWM zip file while in the temporary CWM.

As far as the kernel goes, when you install it, do you get any errors? Did you install the Superuser zip file as well? I'm not sure if you can change the CPU values without root.

 

[ayi]

Are you actually installing CWM recovery, or opening it via fastboot? To install it permanently, you still have to sideload the CWM zip file while in the temporary CWM.

As far as the kernel goes, when you install it, do you get any errors? Did you install the Superuser zip file as well? I'm not sure if you can change the CPU values without root.

no errors, I use a different method to root but I try again following the guide to the T, and even with the new kernel no overclock options.

https://www.dropbox.com/s/hatdlnfvvsbakw4/Screenshot_2013-12-10-16-08-26.png
https://www.dropbox.com/s/34lbe308gqgzqmq/Screenshot_2013-12-10-16-06-47.png

PS not sure why picture aren't displaying but it just - is the Kernel version name suppose to be different?

Hold downing the volume down button opens another "android recovery" that doesn't allow me to sideload, so I sideload it through the temporary CWM.

MAX GPU is still 400

 

[cooldudezach]

no errors, I use a different method to root but I try again following the guide to the T, and even with the new kernel no overclock options.

https://www.dropbox.com/s/hatdlnfvvsbakw4/Screenshot_2013-12-10-16-08-26.png
https://www.dropbox.com/s/34lbe308gqgzqmq/Screenshot_2013-12-10-16-06-47.png

PS not sure why picture aren't displaying but it just - is the Kernel version name suppose to be different?

Hold downing the volume down button opens another "android recovery" that doesn't allow me to sideload, so I sideload it through the temporary CWM.

MAX GPU is still 400

It looks like you still have the old kernel, for whatever reason. The first line of the kernel version should be something like this: "3.4.0-rb3-gf607cb8-dirty".

While you were in fastboot, did you do "oem unlock"? If you install the zip from recovery, it should replace the boot image. However, I think the phone has a backup system in case you clobber the boot partitions if it doesn't boot: It replaces the existing boot.img with a copy of the stock boot.img. It did this to me when I flashed a messed up boot.img, and it booted normally with the old boot.img. This could be what's happening here.

 

[ayi]

I didn't but I can try that,

Do a oem unlock? How do I know if it's successful or not.


c:\Android>adb reboot-bootloader

c:\Android>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s

c:\Android>fastboot oem


c:\Android>fastboot oem get-bootinfo
...

it doesn't give me any results but kernel didn't says the same.

What should i do here :'(?

 

[cooldudezach]

I didn't but I can try that,

Do a oem unlock? How do I know if it's successful or not.


c:\Android>adb reboot-bootloader

c:\Android>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s

c:\Android>fastboot oem


c:\Android>fastboot oem get-bootinfo
...

it doesn't give me any results but kernel didn't says the same.

What should i do here :'(?

Did you try installing the kernel after "oem unlock"?

 

[ayi]

Did you try installing the kernel after "oem unlock"?

yes ! no luck

c:\Android>fastboot oem get-bootinfo
...

nothing shows up afterwards :'( did i brick my bootloader

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\S>cd C:\android\

C:\Android>fastboot flash boot boot.img
sending 'boot' (6762 KB)...
OKAY [ 0.426s]
writing 'boot'...


nothing works on this fastboot ><, all the commands i try fastboot oem ? doesn't give anything back.

 

[cooldudezach]

yes ! no luck

c:\Android>fastboot oem get-bootinfo
...

nothing shows up afterwards :'( did i brick my bootloader

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\S>cd C:\android\

C:\Android>fastboot flash boot boot.img
sending 'boot' (6762 KB)...
OKAY [ 0.426s]
writing 'boot'...


nothing works on this fastboot ><, all the commands i try fastboot oem ? doesn't give anything back.

Those fastboot commands do not work on our device, for whatever reason. Fastboot flash just sits at writing 'boot'. I've let it sit for an hour once, and it did nothing.

I'm still stumped why the kernel isn't flashing. Are you able to flash the Superuser and CWM zips? Do you get any errors on the device when you install them?

 

[ayi]

Those fastboot commands do not work on our device, for whatever reason. Fastboot flash just sits at writing 'boot'. I've let it sit for an hour once, and it did nothing.

I'm still stumped why the kernel isn't flashing. Are you able to flash the Superuser and CWM zips? Do you get any errors on the device when you install them?

So far, superuser.zip flashed just fine, and it updated.

CWM.zip I can only fastboot it temporary, I just installing it multiple times but it boots up with the android system recovery (3e) instead of CWM .

There's no error

it says in the end

Flashing the kernel

* The end of installation *
* Have fun *

Funny thing is I just install rom manager and it detects CWM 6.0.3.7

 

[cooldudezach]

So far, superuser.zip flashed just fine, and it updated.

CWM.zip I can only fastboot it temporary, I just installing it multiple times but it boots up with the android system recovery (3e) instead of CWM .

There's no error

it says in the end

Flashing the kernel

* The end of installation *
* Have fun *

Funny thing is I just install rom manager and it detects CWM 6.0.3.7

Here's something to try:
After you get into temp CWM recovery, go to the option that says something like "mounts and storage". Choose the option to format /boot before the kernel install and format /recovery before the CWM install. let me know if that works.

 

[ayi]

Here's something to try:
After you get into temp CWM recovery, go to the option that says something like "mounts and storage". Choose the option to format /boot before the kernel install and format /recovery before the CWM install. let me know if that works.

There's only
format /cache
format /data
format /sdcard
format /system
format /sdcardata
format /carrier

 

[cooldudezach]

There's only
format /cache
format /data
format /sdcard
format /system
format /sdcardata
format /carrier

Derp, of course there is. I'd have known that if I opened CWM. Try this zip and let me know if it works at all.

I changed how it writes the recovery image.
https://app.box.com/s/ftcoy2maz8j25q0n5om1

 

[ayi]

Derp, of course there is. I'd have known that if I opened CWM. Try this zip and let me know if it works at all.

I changed how it writes the recovery image.
https://app.box.com/s/ftcoy2maz8j25q0n5om1

Yes! when I hold down the recovery volume down button when booting it goes into CWM!

No luck on straight side loading the kernel but I'll try what you suggest above and report back.

The kernel still doesn't sideload directly into the phone though, try multiple times.


ps: I swear there's a delay on androidforums.com, whenever someone replys or I reply it takes forever to update like 5 minutes

 

[cooldudezach]

Yes! when I hold down the recovery volume down button when booting it goes into CWM!

No luck on straight side loading the kernel but I'll try what you suggest above and report back.

The kernel still doesn't sideload directly into the phone though, try multiple times.


ps: I swear there's a delay on androidforums.com, whenever someone replys or I reply it takes forever to update like 5 minutes

GREAT! I'm still not sure why it wasn't working before. Did you redownload it at all?

When me and rbheromax get a couple more things figured out, we'll have a zip out that uses the same way I did to write the image. Should be out tomorrow night hopefully, but probably won't have GPU overclock. It's not working as it should

 

[ayi]

GREAT! I'm still not sure why it wasn't working before. Did you redownload it at all?

When me and rbheromax get a couple more things figured out, we'll have a zip out that uses the same way I did to write the image. Should be out tomorrow night hopefully, but probably won't have GPU overclock. It's not working as it should

Awesome , back to studying for finals tomorrow :'(. How are you writing the image differently this time?

 

[cooldudezach]

Awesome , back to studying for finals tomorrow :'(. How are you writing the image differently this time?

Rather than use this:

package_extract_file("recovery.img", "/tmp/recovery.img");
write_raw_image("/tmp/boot.img", "/dev/block/platform/msm_sdcc.1/by-name/recovery");
delete("/tmp/boot.img")

I'm using this:

package_extract_file("recovery.img", "/tmp/recovery.img");
run_program("/sbin/busybox", "dd", "if=/dev/zero", "of=/dev/block/platform/msm_sdcc.1/by-name/recovery");
run_program("/sbin/busybox", "dd", "if=/tmp/recovery.img", "of=/dev/block/platform/msm_sdcc.1/by-name/recovery");
delete("/tmp/boot.img")

It takes a little longer for it to flash, since it zeros out the partition first before writing. On the other hand, that ensures there isn't anything lingering from what was there before.

 

[cooldudezach]

I'm also going to be switching my files over to Dev-Host, so people will have md5 hashes they can check against.

 

[dragonhart6505]

have flashed the kernel, but its still the same. sideload and cwm does nothing. your v2 kernel appears to be down, so cant test that one. you say youve successfully oc'd with this kernel, but how exactly? noone else appears to be able to flash it. help please?

 

[cooldudezach]

have flashed the kernel, but its still the same. sideload and cwm does nothing. your v2 kernel appears to be down, so cant test that one. you say youve successfully oc'd with this kernel, but how exactly? noone else appears to be able to flash it. help please?

If you read through the last few posts, you'll see that the zips apparently don't write properly, and I'm changing how the zip writes the image, which did write it successfully. Just hang tight a little bit longer.

Edit:
adb sideload will only work when you select the option in CWM to start the sideload. Before that, adb sideload should just report 'closed'. It also will not work unless you type it like "adb sideload filename.ext". If it really isn't working, then I'm not sure what's up.

 

[dragonhart6505]

If you read through the last few posts, you'll see that the zips apparently don't write properly, and I'm changing how the zip writes the image, which did write it successfully. Just hang tight a little bit longer.

Edit:
adb sideload will only work when you select the option in CWM to start the sideload. Before that, adb sideload should just report 'closed'. It also will not work unless you type it like "adb sideload filename.ext". If it really isn't working, then I'm not sure what's up.

Ok gonna keep track of the kernel thread and help test the flashes. Also found out I had an older adb version, got the new one from the sdk. Thanks for your work! Can't wait til it works