Jump to content

The Zte Blade Apex 2 Topic - ALL THE INFO AND QUESTIONS, POST HERE!!!-


Guest Durreau
 Share

Recommended Posts

Guest Durreau

Well, because i have one soon, i open a post about this model... Root methods, Roms, versions of the phone and any doubts, feel free to write here!!!

Link to comment
Share on other sites

Guest Durreau

I have it in my hands !!! But as many customers say this terminal is quite difficult to make root. I uninstalled almost everything that came from the operator and various things, but without root is very difficult to get rid of many things that do not use and clutter on my device.

Another detail: the feeling of firmness that transmits is very good, does not creak at all when held in hand, I liked it. the screen has an unusual hardness, leaves me with the question if they have used Gorilla Glass to protect or further treatment (not shown information about it in the specifications).

If a developer could get a unit, that would be great, as it has enough power to move freely Lollipop (albeit with a clean and optimized KitKat rom - Cyanogenmod style - I'd settle pleasantly)

Anything else I'll keep commenting ...

This mini review was made with Google Translate, sorry if there is any lack of syntax ...

Link to comment
Share on other sites

Guest Durreau

This is all the info that the "about the phone" section have...

 

apex2.jpg

 

If Konstat or anyone needs any further information regarding the device will be happy to provide it :)

Edited by Durreau
Link to comment
Share on other sites

Guest Durreau

Well, the phone accepts the ADB commands, but when try to boot the image of TWRP recovery with the fasboot command the terminal says this:

D:\Downloads\ZTE\Open C Recovery flashing>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [  0.313s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.368s

Any ideas?

Link to comment
Share on other sites

Guest KonstaT

Well, the phone accepts the ADB commands, but when try to boot the image of TWRP recovery with the fasboot command the terminal says this:

D:\Downloads\ZTE\Open C Recovery flashing>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [  0.313s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.368s

Any ideas?

What twrp.img is that? You can't just use a recovery image from some other random device. These are all highly device specific.
 
If you've done some splitting and hacking on the recovery image, make sure that you've used up-to-date tools that also support device tree image (dt.img).

 

Konstat, is this method for obtain root really working in any device? http://forum.xda-developers.com/showthread.php?t=2684210

LOL, I highly doubt that. Classic XDA bullshit thread. :D Method 1 has pretty much zero chance on of working on any device. There's some root exploits listed at the bottom of the post but I think most of them are outdated too.
 
Easiest way to root any Android device is to boot/flash a custom recovery and use it to install SuperSU package (or some other root management of your choice). Exploits only come after that if this is not possible for some reason (e.g. if you needed to dump the original boot/recovery partition first, which is not a problem with ZTE devices because of the stock firmware packages they provide).
Link to comment
Share on other sites

Guest Durreau

 

Easiest way to root any Android device is to boot/flash a custom recovery and use it to install SuperSU package (or some other root management of your choice). Exploits only come after that if this is not possible for some reason (e.g. if you needed to dump the original boot/recovery partition first, which is not a problem with ZTE devices because of the stock firmware packages they provide).

 

 

 

How to make a custom recovery for the apex 2? I want to try... and how to obtain the stock firmware?

Edited by Durreau
Link to comment
Share on other sites

Guest KonstaT

How to make a custom recovery for the apex 2? I want to try... and how to obtain the stock firmware?

Recovery image is usually built as a by-product of a ROM build (CWM for CyanogenMod and TWRP for Omni). Google search will find all kinds of recovery porting/building guides.
 
You can obtain a stock firmware by simply downloading it from the ZTE support site of course. Not necessarily the exact version you have on your device, but at least it's working stock firmware for your device. You don't have to worry about dumping boot/recovery partitions from your device (you'd need root access to do that).
Link to comment
Share on other sites

Guest Durreau

 

What twrp.img is that? You can't just use a recovery image from some other random device. These are all highly device specific.

 

 

Is the recovery for the MotoG LTE version, who shares the same SOC... i think i make all wrong :P

 

Well, i test the recovery image from the norway firmware and works with the "fastboot boot" command. im very noob in the android development, if compile the CWM recovery was easy... :/

Edited by Durreau
Link to comment
Share on other sites

Guest KonstaT

Is the recovery for the MotoG LTE version, who shares the same SOC... i think i make all wrong :P

 

Well, i test the recovery image from the norway firmware and works with the "fastboot boot" command. im very noob in the android development, if compile the CWM recovery was easy... :/

There's zero chance of Moto G recovery image booting on your device and you should never even try something like this.
 
That's a good sign that you can boot an image with fastboot. At least the bootloader isn't locked or anything.
Link to comment
Share on other sites

Guest Durreau

Is a must have Linux to set up the build enviroment? i want to try only to make the recovery... :(

Edited by Durreau
Link to comment
Share on other sites

Guest KonstaT

Is a must have Linux to set up the build enviroment? i want to try only to make the recovery... :(

You need Linux or OS X to build Android. You could also get somewhere by spitting an existing recovery image from a similar device and replacing kernel, dt image, command line, fstab, and other relevant bits from your device. You'd need to do this on an operating system that uses a filesystem that supports symbolic links (=Linux or OS X again).

Link to comment
Share on other sites

Guest Durreau

You need Linux or OS X to build Android. You could also get somewhere by spitting an existing recovery image from a similar device and replacing kernel, dt image, command line, fstab, and other relevant bits from your device. You'd need to do this on an operating system that uses a filesystem that supports symbolic links (=Linux or OS X again).

 

Is too much if you can build something similar? I can be the tester. I have installed linux take me a while, I have no place on the hard disk to accommodate the S.O

Link to comment
Share on other sites

Guest Durreau

Added Perma-root (By Megamejo of XDA Forums)

First root app: https://mega.co.nz/#!9ExyEIbL!hnym2y...m1q-RcrP3Hw3JQ
Second root app : https://mega.co.nz/#!8Yw1HTgL!jwO1Zb...hv0sVZmThADPY0

Root with First root app, then uninstall that app from app manager, then install second root BEFORE rebooting the device.

Have fun!

 

Original Post http://forum.xda-developers.com/android/general/orange-hi-4g-blade-apex-2-getting-t3076536

Edited by Durreau
Link to comment
Share on other sites

Guest Durreau

How can ZTE say that "by company policy" can not release the kernel code used in the Apex Blade 2? Is that legal? if Konstat or any developer could explain me that...

Link to comment
Share on other sites

Guest KonstaT

How can ZTE say that "by company policy" can not release the kernel code used in the Apex Blade 2? Is that legal? if Konstat or any developer could explain me that...

LOL yes, their 'company policy' is that their customer service doesn't have the slightest clue when it comes to things like this. You don't know how many times I've received the same generic bullshit copy&paste response.
 
Linux kernel is released under GPLv2 license and they are legally obligated to provide the source code. Failing to do this is a breach of contract and it can have severe legal implications. Companies this size, and that operate on markets with well-established legal systems, do realize this. While I'm not overall pleased how ZTE manages this, it's not by far the worst company in this business. They have an open source site and company github account (for Nubia line of devices). Generally the problem seems to be in communication and getting the message through.
 
ZTE tends to release kernel sources for 'families' of devices, which means several devices can build from the same source. They've already released several msm8226 kernel sources and at least 'ZTE Blade Vec 4G Kitkat kernel(3.4.x) source code' also includes a defconfig for Apex 2 (P892E10).
Link to comment
Share on other sites

Guest Durreau

 

LOL yes, their 'company policy' is that their customer service doesn't have the slightest clue when it comes to things like this. You don't know how many times I've received the same generic bullshit copy&paste response.
 
Linux kernel is released under GPLv2 license and they are legally obligated to provide the source code. Failing to do this is a breach of contract and it can have severe legal implications. Companies this size, and that operate on markets with well-established legal systems, do realize this. While I'm not overall pleased how ZTE manages this, it's not by far the worst company in this business. They have an open source site and company github account (for Nubia line of devices). Generally the problem seems to be in communication and getting the message through.
 
ZTE tends to release kernel sources for 'families' of devices, which means several devices can build from the same source. They've already released several msm8226 kernel sources and at least 'ZTE Blade Vec 4G Kitkat kernel(3.4.x) source code' also includes a defconfig for Apex 2 (P892E10).

 

 

Thank you for such important info Konstat, I will notify this to the users who request this at ZTE. The deconfig is the baseband of the device?

Edited by Durreau
Link to comment
Share on other sites

Guest KonstaT

Thank you for such important info Konstat, I will notify this to the users who request this at ZTE. The deconfig is the baseband of the device?

Defconfig is a configuration file that is used to compile the kernel (usually you extract it from a running device/boot.img though, but kernel sources usually have some kind of 'template' for supported devices - msm8226_P892E10_defconfig in this case).

 

P892E10 is the ZTE codename for Apex 2 (ro.product.name=P892E10). ZTE baseband versions on stock ROMs are usually completely irrelevant (hardcoded values that say nothing about the actual modem/baseband on the device).

Link to comment
Share on other sites

Guest Oriceles

Added Perma-root (By Megamejo of XDA Forums)

First root app: https://mega.co.nz/#!9ExyEIbL!hnym2y...m1q-RcrP3Hw3JQ

Second root app : https://mega.co.nz/#!8Yw1HTgL!jwO1Zb...hv0sVZmThADPY0

Root with First root app, then uninstall that app from app manager, then install second root BEFORE rebooting the device.

Have fun!

 

Original Post http://forum.xda-developers.com/android/general/orange-hi-4g-blade-apex-2-getting-t3076536

Hey Durreau, I have this same phone, I'm from Venezuela too, I tried that method but both apps gave me error, do I have to do something before installing?

Link to comment
Share on other sites

Guest Durreau

Hey Durreau, I have this same phone, I'm from Venezuela too, I tried that method but both apps gave me error, do I have to do something before installing?

 

You live in Caracas? Send me a PM (private message). And for this method: I only post this for testing, gave me error too, but for the owners of Orange Hi4 seems to work.

Link to comment
Share on other sites

Guest Oriceles

You live in Caracas? Send me a PM (private message). And for this method: I only post this for testing, gave me error too, but for the owners of Orange Hi4 seems to work.

No, I'm from Valencia, but can travel on weekends easily. Yeah I searched more of the subject and it seems is because Digitel have a newer software also known as B01 and other phone companies from Spain, Italy and Mexico have a previous version where the exploit of the apk's work

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.