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

CM11 Developer and Tester thread for ZTE MSM 8x30 devices

Status
Not open for further replies.
jimsmith80 said:
Ill check that out. I have a new build in progress right now. I could have just swapped the libs but i was feeling lucky

Network was set to 4 in the stock build.prop
Click to expand...

stock buildprop is coded by zte though lol. im sure that setting makes very little difference to stock

4 is cdma, no lte

8 is lte/cdma

7 is global apparently

but that ONLY applies after a full factory reset, if you change that value without doing factory reset i dont believe it does anything, so try out the menu and see what happens
 
rowloo said:
hey, does this work on the zte z998 as well, the specs are the same as the z930l but i just want to be sure. thank you
Click to expand...

yes itll work on any device made by zte with an 8930 chipset, so your unico is included. but it has to be built with the correct unico parameters, so if no one has built a unico variant yet you gotta build it to try it
 
New here. Have some knowledge with programing never used Linux tho.... I was a VGP major until finances failed tho....

Any who, I have a zte source(n9511) and can't make sense of how to get this ROM running where it reads sim card anyway I can get a little walkthrough as to how to fix sim error?
If not I'm sure I can make sense of past post's eventually....
Any help tho would be lovely.
Thank you c:
 
lucytripping said:
New here. Have some knowledge with programing never used Linux tho.... I was a VGP major until finances failed tho....

Any who, I have a zte source(n9511) and can't make sense of how to get this ROM running where it reads sim card anyway I can get a little walkthrough as to how to fix sim error?
If not I'm sure I can make sense of past post's eventually....
Any help tho would be lovely.
Thank you c:
Click to expand...

The radio related items are not built into the test rom. I'm working on getting it up and running on the warplte. Read the last dozen or so posts back, and that should give you an idea of what needs to be done.
 
ok, so i flashed the rom on the AT&T Z998 and it is impossible to test as of now... the display is EXTREMELY distorted (including the boot animation). the rom flashed fine and everything went smoothly, it booted up pretty fast with the unico's version but the boot logo and the first-boot setup screens were horrible (the pixels seemed mixed/distorted along the horizontal) i am not sure why this is happening as the unico and the z998 have the exact same specs. the only difference is the physical shape with the camera. i have no idea how to fix this as i have barely any developing experience. thank you
 
rowloo said:
ok, so i flashed the rom on the AT&T Z998 and it is impossible to test as of now... the display is EXTREMELY distorted (including the boot animation). the rom flashed fine and everything went smoothly, it booted up pretty fast with the unico's version but the boot logo and the first-boot setup screens were horrible (the pixels seemed mixed/distorted along the horizontal) i am not sure why this is happening as the unico and the z998 have the exact same specs. the only difference is the physical shape with the camera. i have no idea how to fix this as i have barely any developing experience. thank you
Click to expand...

well i can explain why the specs match... because they are different names for the same phone lol

z998 is the model number, unico is the model name

as far as it not working i really dont know, if you used a rom/boot.img combination made specifically for the unico, then that is where that device stands at the moment, it may need adjustments to the display libs, or something in the kernel could need adjustment

EDIT: looking back though the straight talk version DOES have a different model number though, so it may very well have a different codename and need a different build, according to my research though they are one and the same though so its kinda confusing...

there is a straight talk unico, the one listed on the main page, then an at&t unico, different model numbers... do us, and yourself, a favor and check the stock build.prop for a codename, or pastebin it and link us so we can find it but it should be listed under board name or something along those lines
 
Frizznickrz said:
Unfortunately, adb reboot bootloader simply reboots and bypasses the bootloader. I am able to boot into the bootloader by holding Vol+ and power, but it ignores fastboot.
Click to expand...

i know this is kinda of a dated post, but if vol- is "zte safe mode" as he called it, i would assume thats ftm, meaning vol+ would be stock recovery, i think we forgot to tell him that the phone would show a blank screen or andy and freeze there lol
 
I'm almost across the finish line with the ril. I used the libs from the zte force. booted up, and bam I have signal bars lol. I still can't make a call, but I'm pretty sure It will only take minor adjustments to get it the rest of the way there. Sadly it will be next weekend before I get a chance to work with it again.
 
good to hear :) mms may need some work but i DID get it working in the force, so hopefully its not too far off. mms would only apply to boost though, the data and phone service should apply to everyone cdma just so everyone is aware

see if you can get a logcat or something on why mms is fcing, and get a list of files you swapped from my force repo so we can put together a patch. also somebody might wanna tell the awe guy we have network XD
 
ok here, as i said, i am kind of a noob so i just put in the entire build prop file. (this is a stock file that came with the device as is, i am still running the stock rom) i did see coeus as the name though...

also, i think it just may be the kernel, a friend of mine with dev experience suggested that as well. also, the straighttalk version is cdma while the z998 is gsm...
 

Attachments

rowloo said:
ok here, as i said, i am kind of a noob so i just put in the entire build prop file. (this is a stock file that came with the device as is, i am still running the stock rom) i did see coeus as the name though...

also, i think it just may be the kernel, a friend of mine with dev experience suggested that as well. also, the straighttalk version is cdma while the z998 is gsm...
Click to expand...


it is a coeus

when you flashes the ROM, did it says coeus detected

who made the CWM you are using ?
 
I've been watching to see if u guys got it working and I see your really chipping away at it.The awe is my daily driver so I need it functional. hate to bother anyone but is it usable?
 
alright, when i flash it, it says something like "zte unico detected..." (something like that and i see your little title and credits and then it starts installing the system files.)
i rooted with framaroot (gandalf) and flashed the recovery image with terminal emulator...
this is where i got all the files and instructions...

[Root & Recovery] ZTE Mustang Z998

same guy also uploaded a "stoked" stock version of the rom... (didn't see much difference when i flashed it and i had data problems so i reverted)

http://unleashedprepaids.com/thread-8771.html
 
rowloo said:
alright, when i flash it, it says something like "zte unico detected..." (something like that and i see your little title and credits and then it starts installing the system files.)
i rooted with framaroot (gandalf) and flashed the recovery image with terminal emulator...
this is where i got all the files and instructions...

[Root & Recovery] ZTE Mustang Z998

same guy also uploaded a "stoked" stock version of the rom... (didn't see much difference when i flashed it and i had data problems so i reverted)

[Stoked Rom] ZTE Mustang Z998
Click to expand...


can you test this new coeus kernel, after you flash cm11, flash this zip

https://www.mediafire.com/?uy64cqorgssexas

I made a mistake in the coeus kernel config file
 
so i flashed it and most things ran smoothly, the display was up and running and i was getting wifi, signal... the kernel does need improvement, the phone keeps freezing, sometimes before i even unlock it and i have to reboot it everytime, this is extremely frequent. (its the type of freeze that you get when u overclock too high...), it is too hard to work with it if it keeps freezing. thank you for everything so far
 
i took a look at the warplte stuff, have a few suggestions that may help, may make things worse or just not help at all but hey why not? lol

here is a copy of your system.prop i made modifications to, i marked where i made changes or additions for your benefit i dont recommend leaving my comments in there though it makes it kinda jumbled and confusing lol, i just wanted you to know which things were added, and which things were changed for reference, toy with them and see if any of the things help of hurt the situation

# system.prop for warplte # # cannot take spaces # Junkie Additions rild - Pastebin.com

also, here is the apn i made for the force. as far as im aware this is the newest fully working copy that fixes both send and recieve for mms, does absolutely nothing else though lol, so maybe that is why your mms is fcing because it doesnt have an mms apn

https://github.com/junkie2100/android_device_zte_aurora/blob/jellybean/prebuilts/etc/apns-conf.xml


EDIT: sorry i take that back i think the apn has something to do with the lte as well, its been a while though
 
oh, hey you guys can try the camera stuff from the force too, i know its a different kernel so it may not work out but ya never know. it worked for that device and a number of other ztes. youll wanna check my repo im not sure what all got added for it, best guess basically lol, sorry. also it was the 5mp rear cam on there, so im not sure if itll work with the 8mp ones but it might

they were lifted from some foreign device, cant remember which. ill take a look see if i can pick out the most likely suspects for you and post a list
 
Status
Not open for further replies.
Back
Top Bottom