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

Root They know how the efuse works? Getting closer to more customr roms?

I have problem with the left earphone go in and out of working, not said that eloquently I know:p
 
LOL@"turd moto phone"

If you are technical enough to want to root your phone, run custom ROMs, etc. then you didn't do enough research before buying, or you bought knowing it was locked down and were foolish.

The platform can still be open without being able to replace the freakin' system kernel.



Verizon didn't lock the bootloader.

Also, it's "just."

They may not have been the locker, but I'm sure they were in on it. "Lets add our vz crapware, adds from places that paid us to lock their software in, then we use use Moto because they lock it down so no one can change roms to get rid of the things they don't use".
Seriously, we are lucky the GPS even works on this phone, and that they didn't have moto build in another efuse etc to prevent the navigation from working unless unlocked by purchasing a monthly subscription through verizon. I'll shut up now in case verizon is reading this. I don't want to give them any ideas!


BTW I was kidding when I said turd phone, it still better than the other phones out for VZ right now.... as I went on to say :P.

Sure we can flash some ROMS still, but not if you follow their upgrade path. It's just too dangerous until there is a new SBF.

BTW This is my first android phone. So I was not exacly sure what all the ROMS, thesme, root, etc worked until after my purchase. My Old phone broke, so I had to get a new one, can't spend too much time researching.
 
HTC's G2 for T-Mobile has a hardware root lock.. so locking down phones isn't far from being a common thing. Stop whining about Verizon, Motorola, etc..
 
Just out of curiosity. What is still possible on the x without replacing the system kernel? I'm personally fine with flyx and nextheme. Also I could be mistaken but I thought birdman had something to release when something happened? Or was that the supposed compromise of the efuse?
 
I'm with the others here, sad day for our phones, but the DX is the phone I've always wanted, and I will keep it until my contract expires. However it will be the last Motorola phone I buy. I had a lot of hope for Motorola making a come back, but now I just hope they sink like they always do, through their own terrible decisions.
 
@nenolod
non-dev droid2 and droidx running in high security mode at boot. no way to replace #mbmloader; kexec works but no radio.
5 minutes ago via web
 
@nenolod
non-dev droid2 and droidx running in high security mode at boot. no way to replace #mbmloader; kexec works but no radio.
5 minutes ago via web


Yeah, thats it, they are done it seems.. From the last of what I read They have nothing else to try, for now.
 
Yeah only thing they can do is try and get the radio working, but the milestone guys are the ones who get to this point and got stuck. They're the ones who crushed the last method that was to be attempted on the X.

Its not looking good if the milestone is still having the same issues...
 
What is we're actually working on the wrong device? I'm sure they've looked at the dev phones closely but have they tried the kexec exploit on the dev phone to see if they can get the radio working there? It seems like it would be easier to get it working on there if it's not locked. If it works on there but doesn't work on our phones then it would seem like the locked bootloader is the culprit, but if it doesn't work on there either, then perhaps there's still a chance that we just haven't figured out the correct method yet. Just a thought.
 
It doesn't have to do with it being locked down (while it does in the sense that all of this is a result of the lock down but). I believe the issue comes up because of the way the try and load the custom kernel on top/along with the stock one. It confuse/restarts the radio and then waits for something I think. They don't have a way to stabilize the radio so it doesn't fail.

I know for sure the kexec method is simply having a custom kernel loaded after the original stock has already been started, so it gets kind of messy.


(My understanding, not very precise or exact or even correct I'm sure haha)
 
OK it just seemed like to me that nenolod speculated that Moto might have locked down the radio and that's what was causing the second kernel problems, i.e. if the radio only works with a signed kernel from moto. But again I'm just guessing too.

If it's a matter of confusion on the radio's part because the second kernel is being loaded, then there's still some hope (however small that might be). Does anyone know if they're still actively developing for the Milestone or have they given up on it too?
 
22:54] <@nenolod> ryanbg: yeah. game over, it seems.

I do not believe it is game over just another road block however it does not concern me to any great extent. The DX is an awesome phone running tranquility 2.3.7 with no probs atm and it is amazingly fast especially since my last phone was a BB Storm (POS) so this phone is great, I am happy with it, things could be better however at what point is anything good enough people will always find an issue with something. I agree however that Moto is a steaming pile of $**t however I am not changing my phone until next year when I can get a Dual core android phone with 4g :) but it wont be a Moto.
 
What really sticks in my crawl the most about this defeat is that it gives not only Moto, but all the other manufacturers a blueprint on what to do to future phones to keep us from rooting. Now they know exactly how to win. So why stop trying, is there another project that's waiting for them? It seems to me that this is the ultimate challenge, so quitting just doesn't seem like the thing to do. However I acknowledge that all of those guys have more brains in the logs they leave in the toilet every morning than I do when it comes to this stuff, so if they say it's over, I guess I have to accept their assessment of the situation... sad, because just two days ago we were all CERTAIN that unlock was only a matter of time.

And I can understand the feeling surrounding Birdman... it's King James syndrome. The people of Cleveland hate Lebron because they love him so much they didn't want him to ever leave them. Same thing with Birdman. In walks this major hacker, and he dedicates all of his time to figuring out how to crack the Droid X, which is the phone most of us here in this forum have. So we develop a fondness for the guy, he's on our team after all, and he's doing his best to stick it to the man... so we're all behind him 100%, cheering him on, donating to his cause, and all that stuff. Then after trying everything the guy can think of, he resigns his role as the leader of the X-revolution and walks away... suddenly the community is lost. They no longer have their knight in shining armor to fight for them, or continue the good fight against the powers that be... who do we turn to now?

It seems like a bleak moment alright. I'm not even that interested in custom ROMs, over clocking, or replacing my kernal. I was just excited to see Moto's efforts to keep us from cracking their code fail so we could cheer out loud and rub in their faces. Now it seems they have beaten us all... that really stinks, and it's hard to accept.

Does anyone know the story of the statue of David? Before Michelangelo go ahold of the piece of marble that would become the statue of David, two other very prestigeous sculptors had been commissioned to turn the rock in to a statue. And for whatever reason, both failed. Well Michelangelo was a fiercely competitieve man, so he took it as a challenge that who highly reguarded sculptors would deem this piece of marble 'unworkable', and set out to show the world that he could take such a task head on and achieve what nobody before him was able to come close to doing.

I am holding out hopes that if Birdman really is done and moving on, that some other gifted hacker will step in, see the challenge before him and decide he's going to rise to the occasion and do what Birdman could not. But that isn't to say I don't hold the utmost respect for Birdman and the others who were in there trying their best to unlock the X.

I wish them much success in their next venture.
 
What really sticks in my crawl the most about this defeat is that it gives not only Moto, but
...
...
I wish them much success in their next venture.

Well put man I agree. Just wanted to see Moto get it shoved in their faces that they could never win.
 
There has to be a legal remedy somehow. I know I'm probably wrong in equating a cell phone to a desktop computer, but even my Mac allows me to install Windows out of the box. We must free the phones from lockdown one way or another
 
The more phones that come out with the same locked bootloader, the more likely some hacker will crack it. Just cause they haven't figured it out yet, doesn't mean no one will. Give it time. These are first few phones that have this type of protection.
 
There has to be a legal remedy somehow. I know I'm probably wrong in equating a cell phone to a desktop computer, but even my Mac allows me to install Windows out of the box. We must free the phones from lockdown one way or another

There is no legal remedy.

Just because you own the device, doesn't mean that Motorola has to provide you the tools to unlock the bootloader.

The recent ruling on the DCMA not being applicable to jailbreaking means that it's not illegal to break into the bootloader and load whatever we want - but Motorola does not have to support that endeavor. They can do anything in their power to prevent it, in fact.

Apple is the same way. They lock down the phone as tight as they can. They patch jailbreaks with every version release. AT&T refuses to provide a carrier unlock. None of this is illegal for them to do - and the mod community keeps breaking their protections, which is also not illegal.
 
Back
Top Bottom