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

Root defunct

well really the only thing we have to worry about is visual glitches and wif/bt
wifi/bt wont be that hard to fix if we all contribute and visual glitches we may just have to live with
 
actually sdcard has never worked on any zte device since the original warp on anything past 4.1 so ya got that to worry about. and the display issues they seem to have

and no the warp method wont help, it had gb and a much older kernel so it could be adjusted. also ive notices in the past ztes dont like non stock init binaries so keep that in mind
 
well really the only thing we have to worry about is visual glitches and wif/bt
wifi/bt wont be that hard to fix if we all contribute and visual glitches we may just have to live with

thanks for letting us know. I know it is early but how is the performance? is it lagging? I hate that.
 
well really the only thing we have to worry about is visual glitches and wif/bt
wifi/bt wont be that hard to fix if we all contribute and visual glitches we may just have to live with

most of those visual glitches are simply fixed by turning off hardware overlays from what ive been reading on other builds. wifi/bt are mostly radio/kernel discrepencies, but i dont have wifi at home and only use my bluetooth for my moga pro...but i can live with that. i got my GSIII
 
actually sdcard has never worked on any zte device since the original warp on anything past 4.1 so ya got that to worry about. and the display issues they seem to have

and no the warp method wont help, it had gb and a much older kernel so it could be adjusted. also ive notices in the past ztes dont like non stock init binaries so keep that in mind

oh no, look like it's going to be extremely buggy.
 
maybe, maybe not. those are just possibilities, it is a different device than past ztes. i dont want to smash everyones hope to bits but i dont want you all to get your hopes too high either. it could be a dead end, or it could work perfectly out of the gate
 
maybe, maybe not. those are just possibilities, it is a different device than past ztes. i dont want to smash everyones hope to bits but i dont want you all to get your hopes too high either. it could be a dead end, or it could work perfectly out of the gate

i agree that starting from 10.0 would probably be a better start, but if he gets it booting were already in the right direction
 
pretty much. i hope it works kuz then i can port it to a cm11 repo and adjust it for the warp 4g. i got a cm10.1 build to run all the way through but no boot animation and im exhausted so im gonna have to wait till tonight to do any more work. im pretty sure i accidentally deleted the gralloc.msm8960.so from the rom so im of no use at all right now lmao
 
pretty much. i hope it works kuz then i can port it to a cm11 repo and adjust it for the warp 4g. i got a cm10.1 build to run all the way through but no boot animation and im exhausted so im gonna have to wait till tonight to do any more work. im pretty sure i accidentally deleted the gralloc.msm8960.so from the rom so im of no use at all right now lmao

at least you got it booting ^_^ thats a score for the warp. get some rest and come back to it. leave some notes so you know where you left off
 
pretty much. i hope it works kuz then i can port it to a cm11 repo and adjust it for the warp 4g. i got a cm10.1 build to run all the way through but no boot animation and im exhausted so im gonna have to wait till tonight to do any more work. im pretty sure i accidentally deleted the gralloc.msm8960.so from the rom so im of no use at all right now lmao
Wait, so did it boot to the homescreen, or get stuck on boot?
 
video tutorial is up awaiting your approval
ZTE AWE (N800) Root/Recovery/Kernel - YouTube

Not bad. A couple things I'd like to note, though.
-If you root with cydia impactor, you can just use adb reboot-bootloader, while the phone is on, without going into ftm mode. (which is just download mode) I used ftm mode to root without cydia impactor by flashing the superuser zip, which installs the su binary and superuser.apk. (cydia installs the superSU binary, not the Superuser su binary)
-The second core seems to be locked/unlocked from device to device. not sure why.
-Can you post a screenshot of your about phone? I want to see if the update.zip changes anything, because it replaces every partition. For that reason, I did not use update.zip to return to stock.
-Should probably have mentioned the backup in the beginning of the video.

Edit:
Oh yeah, the bootanimation and bootsound can be replaced.
 
Not bad. A couple things I'd like to note, though.
-If you root with cydia impactor, you can just use adb reboot-bootloader, while the phone is on, without going into ftm mode. (which is just download mode) I used ftm mode to root without cydia impactor by flashing the superuser zip, which installs the su binary and superuser.apk. (cydia installs the superSU binary, not the Superuser su binary)
-The second core seems to be locked/unlocked from device to device. not sure why.
-Can you post a screenshot of your about phone? I want to see if the update.zip changes anything, because it replaces every partition. For that reason, I did not use update.zip to return to stock.
-Should probably have mentioned the backup in the beginning of the video.

Edit:
Oh yeah, the bootanimation and bootsound can be replaced.

Good point. I dont mind rerecording it if you would prefer a more detail oriented tut. Its kinda my thing, recording lol.
 
Flashing the update.zip didnt make a difference as to whether or not the instructions work. Its actually how I returned to stock for the purpose of recording. I also included the stock recovery.img from it, cwm gives status 7 when trying to flash the update.zip
 
Back
Top Bottom