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

Root Bootloader cracked **Update - This was a fake **

Status
Not open for further replies.
from what it looks it works on all the motorola droid devices, but like myself and mazz said, its just odd, you got some who think it will work, and are making it work, and you got others that claim its a scam to get people to recognize one individual as someone who is great. there is no way to know for sure until its proven that it works.
 
damn. i know there are a few that has to be working on this. I wish they would work on it, but thanks.

it'd be awesome if a dev would work on this, they could make the devour a lot better if they would work on it.

You might be better off (if you have the money) picking up a used Motorola Droid on craigslist and selling the Devour if you're wanting to get into roms. I got one for $100 for my wife back around christmas time. Every now and again I see them pop up on there for pretty cheap since a lot of people are getting newer phones and just trying to make a quick buck off their old phones. Just be careful and make sure the ESN is unlocked and clear. Plus, it doesn't hurt to meet at a Verizon store. Might be too much effort for some, but I don't mind taking a few steps to make sure I have a legit device.

Anyways, back on topic.....I really hope that this is real. I love CM7 on my Droid and seeing as how I prefer my Droid X's 4.3" screen, this would great if the mod community gets this working! Might be silly to put Honeycomb on the Droid X, but it would certainly be cool to mess with. Heres to hoping it's true :)
 
So it looks like the keys posted did not work for the droid x. But aliasexorg (freemymoto) has gotten keys using the method nenoled posted. He just needs to test them to see if they work. That is straight from freemymoto team. That's where we are currently. There were a lot of mixed signals going on and I thought I would try to give a current report.
 
I love this. A bit of controversy gets our blood moving again. Honestly, it's been a bit too calm here in the DX section, of late. ;)
 
I was reading somewhere that each phone has it's own signature, so what works for one phone won't work for another; basically each phone would have to be signature compared, but the vulnerability still exists.

How true this is, I don't know. I think it's all speculation at the moment until something concrete comes out.

I will try to find where I read that information from; it wasn't posted by dev, but by a moderator I believe, so take it with a grain of salt, or two ;)
 
I love this. A bit of controversy gets our blood moving again. Honestly, it's been a bit too calm here in the DX section, of late. ;)

Yeah I've been able to get away with checking when I wake up and before bed.. now I gotta get on every hour or so to keep up. Justhope its real and not like the mythical unicorn i spent 4 years trying to catch only tofind out they aren't real
 
I was reading somewhere that each phone has it's own signature, so what works for one phone won't work for another; basically each phone would have to be signature compared, but the vulnerability still exists.

How true this is, I don't know. I think it's all speculation at the moment until something concrete comes out.

I will try to find where I read that information from; it wasn't posted by dev, but by a moderator I believe, so take it with a grain of salt, or two ;)

I read the same thing. The statement was followed with some clarification. "Each Phone" refers to the different models- DX/D2/Atrix... not each DX has a different signatures.

I'd love CM7 on my X! Let's hope this all pans out.

Edit: That's a different post than I read...
 
I read the same thing. The statement was followed with some clarification. "Each Phone" refers to the different models- DX/D2/Atrix... not each DX has a different signatures.

I'd love CM7 on my X! Let's hope this all pans out.

Ok, that makes more sense now :D

Link that please so I can read it :D:D
 
This made me laugh!


@nenolod
William Pitcock
@phandroid gets an award for most inaccurate coverage of this vulnerability (haha)
 
This made me laugh!


@nenolod
William Pitcock
@phandroid gets an award for most inaccurate coverage of this vulnerability (haha)

Maybe instead of giving out awards he should have popped in with a single post to correct the misinformation ;)
 
well i have been reading in their IRC chat log, and so far they are all saying its false, its "nenelods way or trolling" im not sure, i quit paying attention to them after a while, because they got on the subject of hard drives.... but lets hope that this is for real, and not some scam.

If that's true why would nenelods want to do that to his rep?
 
If that's true why would nenelods want to do that to his rep?

well im not sure, i had been in there irc chat channel all morning for the most part, and they just did nothing but sit there and talk about him being a troll, and that he has done this before, (back in october i think is what they said) so im not sure, i dont think he would want to, but you can never be too sure of people these days. i dont know the guy, never followed him until now, so lets all hope for the best.
 
FreeMyMoto

I've been using the wrong terminology. What @nenolod posted were "fingerprints", not "signatures". My apologies.

"Fingerprint" vs "Signature" only means the fact that it's 240-bit makes sense. That's not bad news, folks. My oops just caused confusion.

From what I understand, the "key" that nenolod posted
97 6a 21 7a 67 41 37 9f 26 53 4a 61 7f 2a 86 ae ff 71 21 78 2e 61 4f 71 90 3e 00 27 fe 9b <== initialization vector

is an initialization vector that is used as the starting vector for a formula in mathematica that will return the private keys used for signatures.

I'm guessing it's kind of like a keycode encyrptor...you enter a value k and the the random values generated are based algorithmically around that value k. To decrypt it, you can either brute force, which can be nearly impossible, or use the initial keycode value k to "backwards solve" the encryption.

What I think nenolod was saying was that the initialization vector, along with some other crap he posted, were the values needed to unlock the private keys. Think of them as keycode values. Plug them into the sha1sum formula, whatever that is, and it'll return to you the actual keys.

This post was brought to you with the most primitive of encryption/decryption knowledge from a novice programmer.
 
This made me laugh!


@nenolod
William Pitcock
@phandroid gets an award for most inaccurate coverage of this vulnerability (haha)

Maybe instead of giving out awards he should have popped in with a single post to correct the misinformation ;)


The truth of the matter is that when I tipped the post to writers at Phandroid, I got some of the information wrong. It was when it was all breaking. I apologize. They were ok with it. I couldn't get to sleep last night. I was so upset.
 
looks like birdman is calling it bs for now

With the current info its impossible to replicate what nenolod claims. And even the parts that can be replicated have some logic holes.

So im calling bullshit on the unlock (and you guys know i don't like to do that easily, i TRUST people way too easily)
 
Status
Not open for further replies.
Back
Top Bottom