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

Root [DEVELOPMENT] SickleKernels For the SV

So they release 4.1's source right after the 4.2 update is pushed. What gives, HTC? You release the previous code that I have been waiting for when I get 4.2?
ase2avum.jpg

4.1 may be enough. I can try porting it forward this weekend (I'm probably going to port k2_cl as well) so that we can have a unified kernel. I'll be getting every version this time in attempts of a kernel to use for cm
 
Oh God, Cricket's kernel is ugly. Kill me. I'll see what else I can do to optimize/look into the kernel of the 4.2s'.
rutenu2a.jpg

Mine is higher, one, because of the kernel, and two because I made some additional modifications. I'm even using some wasted cache for additional ram (if that makes any sense).
 
So I've been working on integration of the kernels... Not been a walk in the park, so to say. I have decided that I am now going to wait until the Boost Mobile variant gets the promised 4.4 update. This will allow me to upgrade all variants to a KK kernel :)
 
So I've been working on integration of the kernels... Not been a walk in the park, so to say. I have decided that I am now going to wait until the Boost Mobile variant gets the promised 4.4 update. This will allow me to upgrade all variants to a KK kernel :)

That should make the others happy. Xpirt, over at XDA, said he would tackle it himself also if it came down to it. Seems only the K2_CL is getting this huge update as of right now. Still no official confirmation for the others. They may get stuck with 4.2.2/Sense 5.
 
That should make the others happy. Xpirt, over at XDA, said he would tackle it himself also if it came down to it. Seems only the K2_CL is getting this huge update as of right now. Still no official confirmation for the others. They may get stuck with 4.2.2/Sense 5.

My inside sources say the others won't be updated officially and will remain at 4.2
 
Basically, Boost is the only CDMA variant I think. Unless having a RUIM slot classifies the phone as CDMA lol

Cricket would be the closest to working with Boost. As for K2_UL and K2_U. That's more of a challenge because they are strictly GSM.
 
Basically, Boost is the only CDMA variant I think. Unless having a RUIM slot classifies the phone as CDMA lol

I could easily get 4.4 to work on Cricket. I know that for a fact, but I am not a kernel dev. I would need a Kernel dev to supply me with the proper custom Kernel and I could take it from there.
 
So wait..... 4.4 will be given to the boost HTC One SV but not for other US carriers? Why is that and what about international?

As it stands, Boost Mobile (K2_CL) is not going to do the 4.2.2 update that K2_PLC_CL, K2_UL, and K2_U just recently received. They are going straight to 4.4 KitKat. I do not know why. This was something they decided to do themselves. As for others, it appears they will be left behind on 4.2.2. But that doesn't mean they couldn't receive it at a later date, but so far there has not been any statements from HTC saying that this will happen, but that it will only be for K2_CL.
 
Yes boost only. It is because the one Sv is the only lte HTC phone on boost. They want to have one kk device on both sides. Plus all the money they put into this phone, they need to sell more to make their money back
 
Boost is a brand so they have the ability to bump up to 4.4 if they willingly choose to. As for Cricket, it is up to them if they want to. As for EU, it is up to those who are branded as well. Those who are unbranded, well, that will be up to HTC themselves.
 
Yes boost only. It is because the one Sv is the only lte HTC phone on boost. They want to have one kk device on both sides. Plus all the money they put into this phone, they need to sell more to make their money back

As it stands, most people will get to porting for other gracious K2 variants~<3 But who knows..
 
Won't be that easy to port given the significants of their API levels, their kernel, their partition layout needing to be desperately considered, and most importantly, the fact that boost is CDMA while others are GSM. Cricket is really the best one of having a chance with a fully successful port without any bugs.
 
When I ported K2_UL 4.2.2 over to Boost I was missing out on the proper custom kernel needed and the mere fact that we are CDMA and they are GSM which caused some issues. That project has pretty much come to a halt now that 4.4 is on its way.
 
Won't be that easy to port given the significants of their API levels, their kernel, their partition layout needing to be desperately considered, and most importantly, the fact that boost is CDMA while others are GSM. Cricket is really the best one of having a chance with a fully successful port without any bugs.

Yeah. The only one that matched the CDMA Cricket partition was (I think) either K2_U/K2_UL. That's how I was able to install TWRP without having to downgrade HBOOT. Good for you, Boost. Actually making headlines.
 
Yeah. The only one that matched the CDMA Cricket partition was (I think) either K2_U/K2_UL. That's how I was able to install TWRP without having to downgrade HBOOT. Good for you, Boost. Actually making headlines.

I am gonna put effort in to porting it over to Cricket first and see how that goes when the time comes. Others will be mostly busy with the kernel I could assume, and whoever is left will most likely tackle on porting it to K2_UL and K2_U.
 
Only problem is that the majority of those on AF and XDA are gonna sit back and wait on others. So the manpower to make all of this possible is sadly limited.
 
I am gonna put effort in to porting it over to Cricket first and see how that goes when the time comes. Others will be mostly busy with the kernel I could assume, and whoever is left will most likely tackle on porting it to K2_UL and K2_U.

I like how a bunch of carriers just leave their users in the dust. For 3 times, Crickets given me RUIM phones and they all got stuck on 4.2.
[GS3 d2cri - 4.2.2, ugh. PLC - 4.2.2, yay. ZTE - 4.2.2 I guess yay.]
I mean, 4.3 is for the d2cri, but uh..I don't want Knox.
 
I like how a bunch of carriers just leave their users in the dust. For 3 times, Crickets given me RUIM phones and they all got stuck on 4.2.
[GS3 d2cri - 4.2.2, ugh. PLC - 4.2.2, yay. ZTE - 4.2.2 I guess yay.]
I mean, 4.3 is for the d2cri, but uh..I don't want Knox.

Dont feel bad. Boost has ALWAYS been known to be last when compared to others lol. It actually feels nice that boost is FINALLY gaining some recognition for once lol.
 
Verizon's also been known for that lol

Verizon sucks!!! Not only are they known for being behind. But they are also know for sending out random updates designed specifically to cut out root access and S-Off. They focus so much on denying you the right to access your device that they cannot keep up with the competition. And they still charge you an arm and a leg for their bogus services. Anyone with verizon is an idiot :-)
 
Verizon sucks!!! Not only are they known for being behind. But they are also know for sending out random updates designed specifically to cut out root access and S-Off. They focus so much on denying you the right to access your device that they cannot keep up with the competition. And they still charge you an arm and a leg for their bogus services. Anyone with verizon is an idiot :-)

No offense to Verizon users, but also, they kept people from using the 2013 Nexus 7 at launch, until they got sued XD. The power of laws, man...
While I'm at it, I'm gonna take a look at CM11 on the d2cri, heh ;)
I'm not gonna leave though.
 
Back
Top Bottom