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

If we kill our phones its our problem not theirs. When we start modding we accept the risk that we may do something that can't be fixed however we still mod. I just wish Moto would give us the choice rather than taking it away..... By locking it they pretty much guarentee that someone will try to bypass it and end up completely killing the phone.

I would love to help with the drivers but I know next to nothing about linux or coding really...

Sent from my Liberated D2G

Actually moto phones are some of the easiest to fix. They really did a great job on being able to fix a bricked phone. RSDlite is amazing and runs great on WINE.
theres also an sbf script that along with the sbf file allows for like a 2 command sbf via terminal, and it is easily the simplest bit of software ive ever used. and it works! no bumbling with drivers, no timing button presses, it just works.
 
As I told Alias on Twitter, I posted on Reddit's /r/Android and /r/AndroidDev boards. The former actually netted me a contact with a guy that does drivers for an Anti-Virus company. The friend who replied said he probably could do it, but wasn't sure if he would do it. He then suggested we get this guy a free DX, and I said I could see what could be done. The guy then contacted his friend, and that was the last I heard of it (earlier today, so give it time).

If we can't get drivers, I'm probably going with the Galaxy Tab 10.1, since Samsung at least allows custom roms OR I'll wait until the Kal-El stuff from NVidia hits after summer. I really wanted a Xoom, especially since NVidia outlined new models every year for the next 3 years (through 2014), but if the bootloader is locked, and this device isn't a phone, I really have no use for it.

Motorola is shockingly awful. Do any other cell companies lock their bootloader this tightly?
 
Sounds like the guy wanted a free X. :)

No, they don't. The frigging NSA doesn't lock their stuff down this tight. Look up NSA encryption specs, then compare them to the 2048-bit (assumed)asymmetric encryption used on the Motorola bootloader.
 
If we kill our phones its our problem not theirs. When we start modding we accept the risk that we may do something that can't be fixed however we still mod. I just wish Moto would give us the choice rather than taking it away..... By locking it they pretty much guarentee that someone will try to bypass it and end up completely killing the phone.

I would love to help with the drivers but I know next to nothing about linux or coding really...

Sent from my Liberated D2G

Actually moto phones are some of the easiest to fix. They really did a great job on being able to fix a bricked phone. RSDlite is amazing and runs great on WINE.

Yea, i know its easy to fix (ive had to sbf about 7 times this week from working on sensor problems with d2 ports) but still, Im sure theres a way to completely kill the phone. Im just saying that we should have the choice to risk it if we want to.....

Sounds like the guy wanted a free X. :)

No, they don't. The frigging NSA doesn't lock their stuff down this tight. Look up NSA encryption specs, then compare them to the 2048-bit (assumed)asymmetric encryption used on the Motorola bootloader.

Sounds like the government needs to learn something from Motorola....
 
The only way to really brick a Droid is a hammer. Plus you get multiple paper weights! Its a great deal.

In all seriousness, considering all the horrible things I've done to my phones, I was never able to brick one.
 
Can you run a dmesg | tail after loading kexec then one after trying to execute it.

dmesg does print no messages, neither on ismod then on kexec -l kernel...

I think the point is the address of the sys_call_table is different on the defy...
find_sys_call_table give me 0xc04420fc, but if I try to change kexec_load syscall with sys_call_table[__NR_kexec_load]=kexec_load I got a reboot.....
 
The reboot is during insmod on the line:
sys_call_table[__NR_kexec_load]=kexec_load

And it is a hardreboot...

sent from my moto defy with taptalk
 
I think this should be priority number 1.

I totally agree! My ordering was in no particular order - just the order that I started typing in. :)

I would kill for some driver devs.

Alright guys, I as well as a million other people, I know not really, read droid-life daily. Somebody has to be in contact with kellex or something along those lines and see if we can get a main post on the front page about this cause and the need for driver devs. Everyone over there hates the locked bootloader as much as the next person and maybe one of those readers will have something to offer?
 
Yes, for sure!
On Monday I will have time. Did you have a source repository?

I'm getting is updated and set up better prolly Tuesday.

I've inquired about an X, if I can get my hands on one I'm on board aliasxerog.

Made a deal for an HTC Incredible in the process lol.

We're having issues gathering the funds for one. We got a total of 15 dollars donated to us. So, when we get the cash you'll be getting one to help us. Also, do you have any Droid device?
 
I totally agree! My ordering was in no particular order - just the order that I started typing in. :)

I would kill for some driver devs.

Alright guys, I as well as a million other people, I know not really, read droid-life daily. Somebody has to be in contact with kellex or something along those lines and see if we can get a main post on the front page about this cause and the need for driver devs. Everyone over there hates the locked bootloader as much as the next person and maybe one of those readers will have something to offer?

I'll ask him tonight.


Sent from my DROIDX using DroidForums App
 
Back
Top