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

Root defunct

Here is something to keep in mind as the kernel device tree is worked on. I was perusing the defconfigs, and all of the msm8960-codename_defconfig's stuck out (since the awe/nex falls into that group). I just spent some time figuring out what devices most of the other msm8960 codenames are attached to. Most of them are not released yet, some don't have names yet - only model numbers.

Here ya go:

Code:
DEFCONFIG         MODEL   DEVICE
msm8960-apollo    N9101   ZTE Imperial
msm8960-becky     Z995    ZTE Overture
msm8960-coeus     Z930L
msm8960-demeter   T83     ZTE Dave
msm8960-gaea      ????    Unknown
msm8960-hera      N9511   ZTE Source
msm8960-iris              ZTE Grand S Flex
msm8960-metis     Z740
msm8960-nestor    ????    Unknown
msm8960-nex       N800    Virgin Mobile Awe
msm8960-oceanus           ZTE Blade Apex
msm8960-stormer   N9520   ZTE Stormer
msm8960-warplte   N9510   Boost Warp 4G


Released devices that have the MSM8930/MSM8630 chipset:
ZTE Imperial        apollo    (U.S. Cellular)
ZTE Overture        becky     (AIO Wireless)
ZTE Source          hera      (Cricket Mobile)
Virgin Mobile Awe   nex       (Virgin Mobile)
Boost Warp 4G       warplte   (Boost Mobile)
AT&T Z998           ????      (AT&T Go Phone)
 
I say go for it. I know I'd much rather follow a video of somebody else doing it rather than have to follow a guide and hope I'm doing it right. :)

Oh yeah, did the CWM zip work for you?

Yes it worked fine, got me booted back no problem without factory reset. You think id risk my girlfriends phone with this?! Hell hath no fury like a pregnant woman scorn!
 
Here is something to keep in mind as the kernel device tree is worked on. I was perusing the defconfigs, and all of the msm8960-codename_defconfig's stuck out (since the awe/nex falls into that group). I just spent some time figuring out what devices most of the other msm8960 codenames are attached to. Most of them are not released yet, some don't have names yet - only model numbers.

Here ya go:

Code:
DEFCONFIG         MODEL   DEVICE
msm8960-apollo    N9101   ZTE Imperial
msm8960-becky     Z995    ZTE Overture
msm8960-coeus     Z930L
msm8960-demeter   T83     ZTE Dave
msm8960-gaea      ????    Unknown
msm8960-hera      N9511   ZTE Source
msm8960-iris              ZTE Grand S Flex
msm8960-metis     Z740
msm8960-nestor    ????    Unknown
msm8960-nex       N800    Virgin Mobile Awe
msm8960-oceanus           ZTE Blade Apex
msm8960-stormer   N9520   ZTE Stormer
msm8960-warplte   N9510   Boost Warp 4G


Released devices that have the MSM8930/MSM8630 chipset:
ZTE Imperial        apollo    (U.S. Cellular)
ZTE Overture        becky     (AIO Wireless)
ZTE Source          hera      (Cricket Mobile)
Virgin Mobile Awe   nex       (Virgin Mobile)
Boost Warp 4G       warplte   (Boost Mobile)
AT&T Z998           ????      (AT&T Go Phone)

I guess if the other devices have a large number of users, I will do the "port" for them.
 
Reverted my phone back to bone stock for the purpose of recording the tut. Go to record, try to download supersu and found out its downloading that stupid software enhancement update. 74mb on throttled service...ugh!! Gotta wait. The video will be up this afternoon sometime. I'll link it when its done.
 
no clue on msl codes, i dont use stuff like that but i think you can dump it from QPST
rom is STILL compiling...ugh
 
that's no kitkat or art :'(

I guess i'll be the first to tell you that kitkat would be the last rom to be brought to this phone.

kitkat was a world of work for the galaxy s4, took me forever to get a working build out and it had a lot of developers. the first logical step would be to port a Cyanogenmod with the same base android version as the rom we have. which is 4.1.2

Our matching version of cyanogenmod is the standard CM10.0
It would be the most painless, compatible way we could go.
 
Yeah its for the warp, wouldn't flash if you tried i'm sure.

If the right person played with that rom, they could bring it over.

Ive never built a rom from scratch, just pulled out apps i deemed unnecessary from the zip. I would be willing to try though, so long as I had just a pure base and the tools necessary to compile. What do I need and are you willing to help me out? If your not too terribly busy.
 
im STILL compiling, and its AOSP 4.4.2_r1 released 2 days ago:


rbheromax@agerthorn:~/android$ make -j4
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
TARGET_PRODUCT=full_nex
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-13-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=out
============================================

so just know...its coming :)
 
do not flash that rom... its not for the warp 4g its for the original warp. if it did flash it would brick your phone permanently

oh and none of it is transferrable
 
I guess i'll be the first to tell you that kitkat would be the last rom to be brought to this phone.

kitkat was a world of work for the galaxy s4, took me forever to get a working build out and it had a lot of developers. the first logical step would be to port a Cyanogenmod with the same base android version as the rom we have. which is 4.1.2

Our matching version of cyanogenmod is the standard CM10.0
It would be the most painless, compatible way we could go.

It's either KitKat, or my phones going on a date with a baseball bat
 
well get your baseball bat ready... kuz this phone may never see a usable kitkat. not only is going from jb to kk a huge pain, but zte has certain quirks most of the time that cause anything newer than 4.1 to be nearly useless
 
Back
Top Bottom