Root Still cannot root zte awe after several methods

[chrisnunya74gmailcom]

Also, talk to Scary Alien and PhennomX4 to look at the process. In addition, show them the screen shot. My guess is that you are running into the same problem that Kelley Draves ran into. Or, there is a missing or bad/wrong step in my process, which is based off of Spock's.

 

[scary alien]

Pretty sure the "adb is out of date..." message is not your problem here (that message typically indicates an adb client/server version mismatch or that there was an adb daemon that was started from another process).

Typically, adb connection issues are directly related to these things:

- the necessary adb USB driver, specific to your device, has not been installed
- USB debugging has not been enabled (and/or you haven't yet authorized the RSA fingerprint for the connecting device in the pop-up dialog)
- you might need to have MTP turned-off/disabled for USB debugging to work
- is the device is properly connected and the USB cable is good (if not, try another)

Hope that helps!

 

[roadkill42]

http://androidforums.com/awe-all-th...beta-4-1-2-l-awe-v2-0-works-stock-device.html try this should give u root and twrp its a nice ROM to let us know if it worked

 

[McBad]

I think The adb reboot seems to work bc the phone goes blank with the charge light remaining on. Maybe I'm not turning mtp off correctly, I'm just switching the connect to pc option to "connect to pc software", is ther a different way?

Usb debugging is on. How do I authorize the rsa fingerprint?

As far as the driver goes I've got the pdanet installed, and I've connected this phone installing drivers, plus it's connected fine in the past.

That said when I connect using the connect to pc option as I described above, the pc does not seem to register the device. It only sees it if I connect with mtp

 

[scary alien]

I think The adb reboot seems to work bc the phone goes blank with the charge light remaining on. Maybe I'm not turning mtp off correctly, I'm just switching the connect to pc option to "connect to pc software", is ther a different way?

If adb reboot is causing your device to reboot, then you probably do have adb connectivity, but it would be more of a warm-and-fuzzy if you can get "adb devices" to show "<your device's serial number> device" in it's output.

I certainly can't use USB debugging on my Nexus 5 while MTP is enabled. To disable it, I do this:

Settings -> Storage -> menu (3 vertical dots at the top right of screen) -> USB computer connection -> un-select "Media device (MTP)"

Usb debugging is on. How do I authorize the rsa fingerprint?

You should get prompted for this when when you first connect from a previously unseen system. This is what the screen looks like:

Spoiler

I don't know how old your version of Android is, but older versions didn't give this prompt (I don't remember when it first started showing...).

As far as the driver goes I've got the pdanet installed, and I've connected this phone installing drivers, plus it's connected fine in the past.

That said when I connect using the connect to pc option as I described above, the pc does not seem to register the device. It only sees it if I connect with mtp

PDAnet should be good, but it wouldn't hurt to search for "adb USB driver" with key words for your specific device (i.e., "adb USB driver ZTE Awe").

 

[McBad]

Where would I see the adb output to check for my device?
My storage setting doesn't have the 3 dot menus but mtp is not selected in the connect to of setting. That rsa prompt is something I've not ever seen, this android version is about 2 years old (4.1.2).

I appreciate all your help. Will check for a new adb driver but I'm starting to think I might try to flash back to b04 like Kelly bc there don't seem to be many more chanfpges I can try via this path.

Thanks again.

 

[roadkill42]

Did u try the link I posted

 

[scary alien]

Where would I see the adb output to check for my device?
My storage setting doesn't have the 3 dot menus but mtp is not selected in the connect to of setting. That rsa prompt is something I've not ever seen, this android version is about 2 years old (4.1.2).

I appreciate all your help. Will check for a new adb driver but I'm starting to think I might try to flash back to b04 like Kelly bc there don't seem to be many more chanfpges I can try via this path.

Thanks again.

No problem...happy to help when/if I can .

Actually, in reviewing your post #91, I see that you're actually having issue getting fastboot to respond. The same issues/solutions basically apply to fastboot as USB, i.e., you've got to have fastboot-specific USB drivers installed, but there's no "enable fastboot" mode needed.

You've also got to make sure your device is indeed in bootloader mode (which you hopefully were via your adb reboot bootloader command), so I'm guessing your issue is the fastboot USB drivers.

 

[McBad]

Did u try the link I posted

Not yet. But it looks promising. I appreciate it and will let you know if it works

 

[roadkill42]

U can put this phone in that mode by holding the volume up and hold power button

 

[McBad]

Which mode?

 

[roadkill42]

Fast boot then plug into PC should install drivers for u

 

[roadkill42]

U will see white box appear saying ftm or something like that the bat light should b lit up to

 

[roadkill42]

U will see white box appear saying ftm or something like that the bat light should b lit up to

Opps i miss led u sorry hold both up and down volume bottoms down and power bottom at same Tim u be in fast boot a black screen and bat light on then to get out of it pull battery good luck

 

[McBad]

Ok, thx. Will give it a shot monday since all the stuff is on pc at work.

 

[roadkill42]

I did my awe with out a PC if u have WiFi at ur place u can try that ROM I link for u it can be all done through factory recovery

 

[chrisnunya74gmailcom]

You may want to check out this video, Mcbad. He goes over commands to check your devices that I omitted.

 

[roadkill42]

That should work I would flash twrp the latest in this forum and this su I post its the latest su works on android m and bellow

 

[scary alien]

That should work I would flash twrp the latest in this forum and this su I post its the latest su works on android m and bellow

FYI, I'm guessing the ZTE Awe is not (yet?) running M, but currently root for M/6.0 requires a modified boot image along with the new beta SuperSU flashable.

 

[roadkill42]

FYI, I'm guessing the ZTE Awe is not (yet?) running M, but currently root for M/6.0 requires a modified boot image along with the new beta SuperSU flashable.

I'm running it on my awe and warp4g and my tablet running cm11

 

[scary alien]

I'm running it on my awe and warp4g and my tablet running cm11

Ah, yes--CyanogenMod would of course have the proper policy updates .

That's awesome--thanks!

 

[roadkill42]

Ah, yes--CyanogenMod would of course have the proper policy updates .

That's awesome--thanks!

My tablet running cm 11 awe running Spock's sulu ROM warp 4g running Tesla that phen did all running that su works fine

 

[McBad]

You may want to check out this video, Mcbad. He goes over commands to check your devices that I omitted.

I rewatched this video and followed the steps. I entered teh adb devices command and it produce a list of devices whcih seems to show my phone A00003t...etc . then when i doo the adb reboot-bootloader I noticed something...

the computer makes a noise similar to the video of the phone disconnecting but the reconnecting noise is not the same. instead of the single"dadu" i get a "dududududu". wondering if this means anything bc then if i try fastboot devices command it doesnt return anything and if i try the fastboot boot recovery.img is goes to waiting for device...

 

[roadkill42]

I rewatched this video and followed the steps. I entered teh adb devices command and it produce a list of devices whcih seems to show my phone A00003t...etc . then when i doo the adb reboot-bootloader I noticed something...

the computer makes a noise similar to the video of the phone disconnecting but the reconnecting noise is not the same. instead of the single"dadu" i get a "dududududu". wondering if this means anything bc then if i try fastboot devices command it doesnt return anything and if i try the fastboot boot recovery.img is goes to waiting for device...

That noise u talking about is phone concting to PC depends which windows the video is and yours determines what tone is playing .have u tryed the link I gave?

 

[McBad]

I tried the L Awe dowload that roadkill linked to. It also stalled after the adb reboot-bootlaoder
I can see the device via adb devices command prior to teh adb reboot-bootloader but after if I type adb devices it does not show my device.