[AC Question]

Hello! I am trying to root my ZTE Sonata 2, and all third party user friendly apks and exes have failed me. I think this is because the phone came out fairly recently and there was a change in kernels in 2014(??)
Anyway, I am now attempting to simply use android sdk commands via my pc, which all goes fairly well at first
--sdk tools installed in c drive
--correct drivers for zte handset
--device connected w/usb debug mode
--registers with "adb devices"
The method I've seen is to start it in bootloader mode with "adb reboot bootloader" then enter "fastboot oem unlock," but my phone just reboots normally and "fastboot oem unlock" just returns with "waiting for device"
Also, the device won't even show up with "fastboot devices"

It's a ZTE Sonata 2 running Android 4.4.4 KitKat and a Windows 7 laptop

I'm 100% a beginner with this stuff, so the problem might be really obvious, but I've had zero luck just searching around.

[drfurry]

dont suppose you figured out how to root your phone after all?

[EEK EEK]

Hello! I am trying to root my ZTE Sonata 2, and all third party user friendly apks and exes have failed me. I think this is because the phone came out fairly recently and there was a change in kernels in 2014(??)
Anyway, I am now attempting to simply use android sdk commands via my pc, which all goes fairly well at first
--sdk tools installed in c drive
--correct drivers for zte handset
--device connected w/usb debug mode
--registers with "adb devices"
The method I've seen is to start it in bootloader mode with "adb reboot bootloader" then enter "fastboot oem unlock," but my phone just reboots normally and "fastboot oem unlock" just returns with "waiting for device"
Also, the device won't even show up with "fastboot devices"

It's a ZTE Sonata 2 running Android 4.4.4 KitKat and a Windows 7 laptop

I'm 100% a beginner with this stuff, so the problem might be really obvious, but I've had zero luck just searching around.

I'm having same issue with Alcatel Pixi 4 "7, in my opinion, bootloader it's missing from device for "secure reasons". I think we must add somehow bootloader back, in fact. there's a unanswered question, why does it even have allow oem unlock if bootloader is missing, that question can go to conclusion that bootloader might not be missing.

[Rukbat]

there's a unanswered question, why does it even have allow oem unlock if bootloader is missing

Is there a choice of unlocking the bootloader in Developer Options?

(Why does adb allow "reboot bootloader"? Because adb is a universal program for all Android phones, those with unlockable bootloaders and those without.)

bootloader might not be missing.

It's not, or the phone wouldn't boot. Whether you can boot into the bootloader is another matter.

Try reading this thread on XDA for further information on unlocking the bootloader, rooting, installing TWRP, etc. (Please read the bold notes at the end of the first post, especially Note 3. If you have a 4034N, click the link in Note 3 and read it.)