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

Root ZTE Warp Sequent N861 Kernel source is now out!

You beat me to it, I actually contacted ZTE last week to ask them to post it, you have to remind them at times...

You where right to suspect it wont' work tho, it wont build due to an error in drivers/mfd/pmic8058.c
 
You beat me to it, I actually contacted ZTE last week to ask them to post it, you have to remind them at times...

You where right to suspect it wont' work tho, it wont build due to an error in drivers/mfd/pmic8058.c

You should see the emails I have from theme. I suppose you might have better contacts than I ;)
 
With the Blade we spent a lot of time explaining their legal obligations under the GPL to put out the kernel source, and got a number of (non working) kernel sources out of them.

I had a lot of problems getting the to put out the Warp Kernel source last year, but they are a lot more organized now, however it seems there is still internal communications issues since the guys responsible for posting the kernel source don't know when the devices are on sale..

we have the details for a guy in the Shanghai office, and of late, if we email him, the source normaly shows up in the support site a few days later..
 
Needed to add /arch/um to have make clean work, does 3.0.8 have another method?
this is missing across all 3.0.8 that zte released
Edit:
I pulled the entire /um from the arthur source. Didn't have time to test, but I believe all it needed from that was /um/scripts/makefile.rules
I also am looking for testers to prove that you have a working source. But don't expect anything for awhile.
 
I would.....I have the cwm, but it doesnt clear cache correctly, that and I have bricked two previous phones, not zte warp sequents, but two other phones and reallllly dont feel like bricking this phone. Im stoked though, this is going to be just stock kernel test not oc?
 
I would.....I have the cwm, but it doesnt clear cache correctly, that and I have bricked two previous phones, not zte warp sequents, but two other phones and reallllly dont feel like bricking this phone. Im stoked though, this is going to be just stock kernel test not oc?

If we can build a stock I can modify it.
 
I'm ready to test. Rooted, recovery-clockwork-4.0.1.5s-warp2.img works fine so far, had error msgs first boot into recovery, reading /cache/recovery.log, cleared cache, np. Backup and restore work.
I have my stock boot and recovery images. What's next?
 
I'm ready to test. Rooted, recovery-clockwork-4.0.1.5s-warp2.img works fine so far, had error msgs first boot into recovery, reading /cache/recovery.log, cleared cache, np. Backup and restore work.
I have my stock boot and recovery images. What's next?

I'll make a build tonight. You will need to backup your boot.img
 
We will test the source first. Only when everything works, then we can move on.
Zte is known for releasing broken source code.
 
+1 if we can get an update on this. I have 3 of these phones so im looking for a point in the right direction. . I dont know much about this stuff but directions are easy to follow if their thorough, and if u dont leave me hangin with a broken phone, considering these are new phones i dont know any fallback methods like kdz_updater.
 
This project is open and on github if anyone wants to take over and sort out the memory leak. I don't have time nor a phone to test on.
So its yours to do with as you please.
Credits to me for the overclock ;)
 
Quick question,kinda offfffff topic,,but......I was wondering if one of you guys can make me or inform me how to make a ota update zip that i can flash thru stock recovery.as you might have guess im stuck with ftm and stock recovery.
 
Back
Top Bottom