Post Reply

kexec bootloader bypass coming in a few days

OP ssinisterss

12th April 2012, 05:24 AM   |  #21  
Senior Member
Flag Philadelphia, PA
Thanks Meter: 865
 
1,334 posts
Join Date:Joined: Jan 2008
More
This work was started by [mbm] on the Bionic and he sent his partially functional code base to kholk, who then got a very "dirty" version of it to work on his GSM RAZR.

Kholk sent that back to [mbm] to complete the work for the CDMA/LTE RAZR because kholk lives in Italy and has no CDMA/LTE service to test anything on involving the radios.

When the RAZR giveaway happened, because I knew the principal player involved, I did some lobbying for [mbm] to receive one of the phones and kholk agreed, for the above mentioned reasons and because he wanted to give something back to [mbm] for all of his months of work on this project.

Guess who got the RAZR?

Whether or not this can be ported to the D3 remains to be seen but I think it's likely that it will, with some considerable amount of work. None of this is at all simple or straightforward and it is the culmination of years of work that started with the OG Milestone.
Last edited by cellzealot; 12th April 2012 at 05:32 AM.
The Following 5 Users Say Thank You to cellzealot For This Useful Post: [ View ]
12th April 2012, 06:33 AM   |  #22  
gierso's Avatar
Senior Member
Flag Monterrey
Thanks Meter: 44
 
366 posts
Join Date:Joined: Aug 2010
More
I have been following that thread Since the inminent release 2 months ago... i dont know when it will be Out but kholk already said that it should work with the similar devices as d3 razr bionic and d4 ... i hope he hurries up cuz im getting desperate

Enviado desde mi XT862
12th April 2012, 11:05 AM   |  #23  
thingonaspring's Avatar
Senior Member
Thanks Meter: 220
 
428 posts
Join Date:Joined: Mar 2006
Thanks to cellzealot for adding some context to this thread.

A working Kexec and kernel is not a simple thing to do by any measure, but as the droid 3 already has a 2nd init exploit (safestrap, clockworkmod) and there is the possibility of a working kexec/kernel for very simillar hardware (Razr), then the chances appear good that this could work.

That said - don't underestimate the amount of work required here. Just getting a working kernel running will take a lot of effort. If that's successful, then there'll be a ton more work to enable all the nice features that a custom kernel can provide (overclock/undervolt, ICS tiler, BFS scheduler......).
13th April 2012, 12:03 AM   |  #24  
Member
Thanks Meter: 8
 
47 posts
Join Date:Joined: Sep 2010
I don't have much (or really any) experience with hardware stuff like this, but I'm a capable programmer and "fluent" in C. If source for this is released, I'd be more than happy to help out as best I can.
13th April 2012, 03:10 AM   |  #25  
Hashcode's Avatar
Recognized Developer
Thanks Meter: 22,450
 
3,232 posts
Join Date:Joined: Sep 2011
Donate to Me
More
I can probably add some clarification to this.

Over the last 2 months, I've been developing a new Kindle Fire 3.0 kernel. I had full source from Amazon for the 2.6.35 kernel, and it was developed as a close device to the Blaze Tablet for which source is plentiful.

That being said, there have been many challenges along the way.

Now imagine adding the complexity of kexec and all of the phone features which tablets dont have.

Also, even with a full 3.0 kernel, I'm still having issues securing a portion of the ducati source code to create a 512mb compatible hw codec binary, as the stock binary from TI is hard coded to 1gb of ram. And it doesnt have the custom camera code that Moto adds to it.

So after months of work, you'd have a very functional ICS w/o hardware codecs ... which is almost what we have now.

Sent from my DROID3 using XDA
13th April 2012, 03:29 AM   |  #26  
Senior Member
Thanks Meter: 44
 
391 posts
Join Date:Joined: Jul 2008
That's crushed some hope.

If it means that HW codecs are off the menu for the forseeable, I'd love to see CM7.2 being ported for the interim for those who want performance but need HW codecs/flash and the like.
13th April 2012, 03:34 AM   |  #27  
ssinisterss's Avatar
OP Senior Member
Flag so. california
Thanks Meter: 19
 
219 posts
Join Date:Joined: Apr 2010
More
Quote:
Originally Posted by Hashcode

I can probably add some clarification to this.

Over the last 2 months, I've been developing a new Kindle Fire 3.0 kernel. I had full source from Amazon for the 2.6.35 kernel, and it was developed as a close device to the Blaze Tablet for which source is plentiful.

That being said, there have been many challenges along the way.

Now imagine adding the complexity of kexec and all of the phone features which tablets dont have.

Also, even with a full 3.0 kernel, I'm still having issues securing a portion of the ducati source code to create a 512mb compatible hw codec binary, as the stock binary from TI is hard coded to 1gb of ram. And it doesnt have the custom camera code that Moto adds to it.

So after months of work, you'd have a very functional ICS w/o hardware codecs ... which is almost what we have now.

Sent from my DROID3 using XDA

i wish it was as fast as the Gnex guys can make a kernel i know being open a kernel can be made in a few hours to a few days.would it be easier for the D4 since it has 1gb of ram?

i may have to move onto the Gnex now
Last edited by ssinisterss; 13th April 2012 at 03:54 AM.
13th April 2012, 07:17 AM   |  #28  
Hashcode's Avatar
Recognized Developer
Thanks Meter: 22,450
 
3,232 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Quote:
Originally Posted by ssinisterss

i wish it was as fast as the Gnex guys can make a kernel i know being open a kernel can be made in a few hours to a few days.would it be easier for the D4 since it has 1gb of ram?

i may have to move onto the Gnex now

Difference is that the 3.0 GNex kernel actually exists at the moment. Where the 3.0 kernel for the D3 does not exist.
13th April 2012, 11:52 AM   |  #29  
cappysw10's Avatar
Senior Member
Flag Upstate NY
Thanks Meter: 96
 
1,347 posts
Join Date:Joined: Jul 2010
Quote:
Originally Posted by Hashcode

Difference is that the 3.0 GNex kernel actually exists at the moment. Where the 3.0 kernel for the D3 does not exist.

Hash, what are you waiting for?

If I learned anything from being here....patience.
13th April 2012, 02:17 PM   |  #30  
gierso's Avatar
Senior Member
Flag Monterrey
Thanks Meter: 44
 
366 posts
Join Date:Joined: Aug 2010
More
Quote:
Originally Posted by Hashcode

I can probably add some clarification to this.

Over the last 2 months, I've been developing a new Kindle Fire 3.0 kernel. I had full source from Amazon for the 2.6.35 kernel, and it was developed as a close device to the Blaze Tablet for which source is plentiful.

That being said, there have been many challenges along the way.

Now imagine adding the complexity of kexec and all of the phone features which tablets dont have.

Also, even with a full 3.0 kernel, I'm still having issues securing a portion of the ducati source code to create a 512mb compatible hw codec binary, as the stock binary from TI is hard coded to 1gb of ram. And it doesnt have the custom camera code that Moto adds to it.

So after months of work, you'd have a very functional ICS w/o hardware codecs ... which is almost what we have now.

Sent from my DROID3 using XDA

look hash uses his droid 3 for surfing xda!!



i must relearn all my prog skills to help.
very rusty right now. nooo, more than rusty.
Last edited by gierso; 13th April 2012 at 02:22 PM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes