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

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

dragonhart6505 said:
Cwm.img in fastboot to get to cwm recovery, then flash with cwm.zip
you can't flash unofficial zips in stock recovery, which is why you need to boot cwm first
We are also currently implementing the ota into the next revision of our custom roms. It has a few updates to the system and we havent yet released those in the current state of the customs
Click to expand...

Okay, thankyou very much:-) I actually figured it out and managed to do it the "lazy" way. It was extraordinarily easy and much less steps. I just used the suggested Cydia impactor and someone else suggested [root] recovery tools, which flashed the recovery flawlessly, I did it to both CWM and Philz, one over the other. So for newbs, the closest to easiest way without a root/recovery method from the phone would be the one I'm describing for sure.
 
I use cmw v 6.0.3.7 but unfortunately while I tried to install from sdcard, it said error to mound sdcard
can you tell me how to solve it?
thanks
 
armymartinez said:
SuperUser link is bad. :(

Thanks.
Click to expand...

You can install super user from the play store if you need to. Both super user and super su work for our phones. You probably need to update the binary though. I recommend running a root checker afterwards to verify everything is working properly.
 
Today I made a recovery file while in CWM recovery mode. Then when I tried actually using it, it stated that the MD5 Sum was wrong. Why did this happen? I deleted my old recovery files to free up a little space so I was forced to start from either stock or awesomeROM.
This sucks because I had deodexed and zip aligned a stock from and just had my second core forced online via android tuner. Had my phone set up exactly how I wanted it and now am building it again.
I did a complete wipe prior to attempting to recover. Would this cause MD5 to not line up?
 
vestalpaul said:
Today I made a recovery file while in CWM recovery mode. Then when I tried actually using it, it stated that the MD5 Sum was wrong. Why did this happen? I deleted my old recovery files to free up a little space so I was forced to start from either stock or awesomeROM.
This sucks because I had deodexed and zip aligned a stock from and just had my second core forced online via android tuner. Had my phone set up exactly how I wanted it and now am building it again.
I did a complete wipe prior to attempting to recover. Would this cause MD5 to not line up?
Click to expand...

Are you using the original CWM for this phone? Most suggest to go with TWRP, as the prior recoveries can be faulty. My only explanation is that sometimes that happens. It was a backup that you tried to restore that said the MD5 didn't match, right? Only thing I know to tell you is that there's an option to disable md5 checking in TWRP, but md5s are generally created for security purposes, in ensuring that your file isn't corrupt.

Here's a link to get a new deodexed stock ROM, if you didn't know http://androidforums.com/showthread.php?p=6557821
 
vestalpaul said:
Today I made a recovery file while in CWM recovery mode. Then when I tried actually using it, it stated that the MD5 Sum was wrong. Why did this happen? I deleted my old recovery files to free up a little space so I was forced to start from either stock or awesomeROM.
This sucks because I had deodexed and zip aligned a stock from and just had my second core forced online via android tuner. Had my phone set up exactly how I wanted it and now am building it again.
I did a complete wipe prior to attempting to recover. Would this cause MD5 to not line up?
Click to expand...
If you have spaces in the backup name then it'll come back as a md5 error. Just rename it to something without spaces get passed it.
 
Was wondering if I could use part of this guide to make an updated one. I haven't got a response from the op yet so maybe my private message didn't go through so I will ask here.
 
You can probably get away with flashing the supersu zip from there site. If you are planning on using a rom besides stock it most likely will include super user
 
DaRkSkYxP said:
Was wondering if I could use part of this guide to make an updated one. I haven't got a response from the op yet so maybe my private message didn't go through so I will ask here.
Click to expand...

I'm afk from the android scene for a little bit. school just started back up, and I'm getting house renovation projects done. :) I forgot to reply to your PM, sorry. Feel free to use this guide! I obviously haven't had the time to update it :(
 
It's been a long time since I've rooted so this may be a noob problem but when I get to the point where I open the terminal window and have to enter "adb reboot-bootloader", I get the message "'adb' is not recognized as an internal or external command, operable program or batch file". I have PDAnet installed setup and connected, I have the 4 files in a folder called "root" and the terminal window is open for that. My phone has the FTM screen, but I get that error message when i enter that message at the terminal window. Any thoughts?

Edit: Nevermind, realized I made the rookie mistake of not getting the adb file and putting it in the directory. All good now, thanks for the steps.
 
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!
Click to expand...
Is the Cydia Impactor method reliable? This seems much easier than having to install additional software on your PC and manually typing commands. From my understanding, you still need to "install a device driver to talk to your device over USB" but don't need to install Android SDK. It appears that downloading, extracting, and running Impactor.exe is enough to root the device. Does SuperSU work fine, or is Superuser recommended? The first post says you still need Superuser.

Edit: I rooted with Cydia Impactor and installed SuperSU, everything seems okay so far.

sources:
How to root any Android Device using Cydia Impactor or How to Root a ZTE AWE phone! (Virgin Mobile) | Paul's Tech Talk
 
dragonhart6505 said:
Quite literally? None. Its a symlink command done with the updater-script to push the binary to /system/bin and set the permissions. So far, it has to be done outside of the Android OS

It goes like this...
1: enable USB Debugging
2: install pdanet drivers (select other when asked about which device)
3: download adb and fastboot and cwm (ill include them in a zip when i get the chance to write up)
4: connect to your pc (with drivers installed)
5: type "adb reboot-bootloader" (without quotes)
6: type "fastboot boot cwm.img" (without quotes)
7: flash the cwm.zip (ill include root privileges)
8: wipe cache/dalvik-cache and reboot

Simple, no?
Click to expand...

Yeah, that's simple.
 
When I do fastboot boot cwm.img the phone just stays black. It doesn't reboot into recovery. Everything else works up to that point. fastboot devices shows the device. Any ideas on what is going wrong?
 
Well how do I get root if this guide says I have to boot into temp cwm? Cydia Impactor gives "signature bugs unavailable," so I can't use that.
 
You must log in or register to reply here.
Back
Top Bottom