What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Getting Custom Kernels Running on the Droid X

Yeah an sbf should fix it. Just remember to make a nandroid backup. Ill have to see how it behaves in emulation prior to sending it out.

Also what operating system do you guys run on your computers?

Sent from my DROIDX
 
Sweet! I prolly wont support windows the if there's linux users out there. I dont have a windows machine so that makes my life easier.

Sent from my DROIDX
 
I'm all for this project. Just realized recently how debilitating the bootloader thing is.

Also, if it makes it easier, definitely do it on whatever platform. If/when you ever do get it working, it would be very helpful to get it at least windows-accessible (osx can suffer) since I'm sure a vast majority of forum users use windows machines.

Aaaaaand this needs to get spread around on forums, twitter, etc, so everyone and anyone who could help can if they want to.

Sent from my DROIDX using Tapatalk
 
Yeah an sbf should fix it. Just remember to make a nandroid backup. Ill have to see how it behaves in emulation prior to sending it out.

Also what operating system do you guys run on your computers?

Sent from my DROIDX

I'm dual booting Ubuntu and Windows. Sweet, I cannot wait to brick this thing.
 
With the possibility of another motorola ota update coming soon, I figured this minor piece of info might help. Someone mentioned a while ago that when motorola sends out these updates that the bootloader temporarily unlocks from being in engineering mode or something. I don't know much about cracking but I remember some people discussing the possibility of exploiting that hole. Whether its a feasible thing to do I have no clue, but maybe it'll toss some kind of hints out there.
 
Just fyi beesly and birdman don't think your radio method is going to work, that's a downer but I would LOVE to see you prove them wrong :P
 
Yea I just read their twitter posts...sucks to hear and I know birdman and the nenold guy worked a lot with some other people and got to the exact point that they did with the milestone...kernal loaded but no working radio..between them and the people working on the milestone for over a year im sure they tried every option to get the radio working but never got it so in guessing this is.going to be the same thing...I would loveee to see it happen but who knows...sick of devs moving away from the x because of it. If this thing got unlocked shortly after it was released I couldn't imagine how many amazing roms we would have right now

Sent from my DROIDX using Tapatalk
 
Just fyi beesly and birdman don't think your radio method is going to work, that's a downer but I would LOVE to see you prove them wrong :P

Sorry bro, its just already been tried before. We already know kexec won't work, even with kernel modules.

OP, get at @nenolod on twitter and shoot your idea to him.

Unless you have a new idea, he's prob just gonna say the same thing...

Sorry, I would love for it to work, but we've already done it.

KEEP TRING THOUGH! THANKS

Sent from my DROIDX using Tapatalk
 
Well I looked at what everyone did with kexec and the thing about getting the drivers running is that they're two different kernels which need two different drivers. Really though I'm not worried about that as much--someone else will figure it out as I have never written a driver in my life. My job right now is just getting a stable way to get a kernel running. kexec(8) can do it and has done it with every kernel update on my computers for the past six months. The thing about my approach is that its extendable with a config file that will load the new module that works with the new kernel (modprobe ftw). The current system works-ish in the sdk emulator except that the module is quite crashy. Radio works with the hack on the emulator. The issue is that we need to get motorola's drivers running on other kernels.

So to sum it up: kexec works its just a driver compatability issue.

Sent from my DROIDX
 
Yeah pretty much. That stuff is brutal to do and I really don't know if we can find someone willing. We can even have someone write a compatability layer.

Sent from my DROIDX
 
Back
Top