ALL X Owners looking to Root/Hack in the Future - READ THIS

[leggy]

does "one root click" still work? Would the leaked Froyo install after applying this root?

 

[GatorPT]

good news . after fighting this , i updated to 2.2 , but i cheated a little bit . i used rom manager to update to 2.2 , and the first thing i did was benchmark , and 1572 . wow . i never left the 1200 before update never above 1250.

 

[GatorPT]

and by the way leggy , i was one click root too. i have learned alot from this site , still dont know alot , but im learning , i have only had android for 9 weeks. was a blackberry guy , never got into modding the phones though , its pretty amazing what you can do to these android phones.

 

[santacruz]

pretty sure even if you update to the official 2.2, you can just sbf back to 2.1, root, and install w.e the hell you want anyway. Plus if birdman actually makes this bootloader announcement talk official, you wouldn't even really need to do that.

 

[GatorPT]

what does being able to ''crack the bootloader''? what is the bootloader?

 

[DaRkL3AD3R]

pretty sure even if you update to the official 2.2, you can just sbf back to 2.1, root, and install w.e the hell you want anyway. Plus if birdman actually makes this bootloader announcement talk official, you wouldn't even really need to do that.

Santacruz I think you missed my initial point. By installing a newer OTA you are updating the boot-loader. As of right now Birdman may have a crack for our 30.01 boot-loader, but what happens when the OTA hits and it's a different version, possibly fixing the holes he's working with right now?

And as I already stated, SBF flashing does NOT reverse the boot-loader. Once you update it, that's it. I'm simply saying this is the safest way to keep your phone from getting locked down as we have all the tools we need to work with it RIGHT NOW. There are no if's involved.

 

[dvader]

With it is most likely going to come some patched up holes to methods we currently use to hack, mod and theme our phones.

So it's "most likely" ??

As of right now no one knows just how sealed up 2.2 will be once it finally is released officially

Or is it "nobody knows" ??

If nobody knows, then I don't understand how you can say it's going to happen.. if you don't know then you don't know

 

[lindycu]

Sorry for the questions, as I'm on board with getting on the unofficial 2.2 but I want to make sure I'm going this correctly.

Okay, so I downloaded update.zip and DroidXRoot_V2. I'm running a non-rooted 2.1update1 X right now. Do I need to root using DroidXRootV2 first and then load the 2.2?

I also see a post on here about 2.3.4 or something for the DroidX...is this what I should eventually go to?

Also, I assume that I need to go back to the sticky post on what bloatware can and cannot be removed correct? If I root I'd like to strip off the things like CityID, Amazon MP3, etc.

 

[tntdroid]

Throw on Flyx after that and no more bloat

Sent from my DROIDX using Tapatalk

 

[leggy]

Thanks Gator. Was your reference the link that leader posted for birdman?

 

[P3Droid]

wrong and wrong.

There are some misrepresentations in the original post.

First, the newest updates can still be rooted using the newest method from sebastion.
second, cracking the bootloader while progressing is not imminent.

 

[doctorlove316]

There are some misrepresentations in the original post.

First, the newest updates can still be rooted using the newest method from sebastion.
second, cracking the bootloader while progressing is not imminent.

I believe that this is true.

I was able to root the latest 2.2 leak using the Droid 2's method just fine.

Also, where did that information for the OP come from? There's no links or anything that point to where the information came from, such as the information about the bootloader being updated with the OTA and not being able to flash the .SBF.

Not trying to be negative or anything but I'm just looking as to where all this came from.

 

[DaRkL3AD3R]

I believe that this is true.

I was able to root the latest 2.2 leak using the Droid 2's method just fine.

Also, where did that information for the OP come from? There's no links or anything that point to where the information came from, such as the information about the bootloader being updated with the OTA and not being able to flash the .SBF.

Not trying to be negative or anything but I'm just looking as to where all this came from.

Sorry for the confusion. Basically the boot-loader changed when we installed the leaked 2.2. The original version of the boot-loader was 27.01, and even after SBF flashing we do not go back to the original, still stuck on 30.01.

This means that there may be cracks available in the 30.01 boot-loader, but a future version may patch them up. By staying on the leaked 2.2 you are immune to a pushed OTA which may contain a newer, more secure boot-loader.

So it's "most likely" ??

Or is it "nobody knows" ??

If nobody knows, then I don't understand how you can say it's going to happen.. if you don't know then you don't know

As for quoting me as saying "its most likely" more secure, and that "nobody knows for sure," well yeah, no one knows. I am not an owner of a DeLorean DMC-12. Anyone's guess is as good as it gets until the future becomes the present. HOWEVER with these steps you are immune to the possibilities. And if we find out that hey all is just swell with the official 2.2 release, it doesn't update our boot-loaders and we can still get our root on, then we can always SBF back to 2.1 and do it fresh.

Until then, you can take your chances. I will gladly let you take the OTA before me and report your findings, for the good of Droid-kind

 

[DaRkL3AD3R]

There are some misrepresentations in the original post.

First, the newest updates can still be rooted using the newest method from sebastion.
second, cracking the bootloader while progressing is not imminent.

Newest updates meaning the 2.3.13 or something that was released very recently?

Even if the crack on the boot-loader isn't happening anytime soon, neither will there be another update past Froyo. One can comfortably sit on the leaked 2.2's for a few months until Gingerbread possibly gets in the mix, or they release some amazing bug fix patch (not sure what bugs there are to fix anymore...)

Either way, no one knows anything that happens past now for sure, and it definitely doesn't hurt to be on the safe side. That's all I'm trying to advise here.

It's easy to SBF flash back from leaked 2.2. It's not easy to flash the boot-loader to an older version.

 

[doctorlove316]

So this is just all speculation still?

BTW, this is from WadeIvy who provided us with "The Gift"...

"For the record: You can downgrade your bootloader (Motorola Droid X users)"

and

"Right now downgrading bootloader isn't officially necessary. If it is ill provide a tutorial and the files..."

 

[dvader]

this isn't the xbox 360. it's not like Motorola is trying to prevent piracy.
it's legal to modify your phone.
IMO it's unlikely they will patch any exploit

 

[DaRkL3AD3R]

So this is just all speculation still?

BTW, this is from WadeIvy who provided us with "The Gift"...

"For the record: You can downgrade your bootloader (Motorola Droid X users)"

and

"Right now downgrading bootloader isn't officially necessary. If it is ill provide a tutorial and the files..."

Yes as of right now its all speculation. I'm playing it on the safe side until official reports start to hit the net on the exact whats about the official Froyo release.

I read those tweets too, but until its posted and out in the wild and confirmed, again, playing it safe. I don't see the harm in sitting on leaked 2.2 until official confirmation is out that it's perfectly ok to install official 2.2. Not like I'm telling people to install virtual poison on their phones

this isn't the xbox 360. it's not like Motorola is trying to prevent piracy.
it's legal to modify your phone.
IMO it's unlikely they will patch any exploit

How can you possibly say that? Didn't they patch up the 2.1 root process by removing the sqlite_stmt_journals folder, our path to run the exploid file in root?

 

[doctorlove316]

That's fine and everything. Always good to play it safe with the uncharted. I'm just worried about all people now that are going to screw something up and come crying about it. It's bad enough that there are so many X users that are brand new to Android and are rooting using these "one-click" methods and do all these things having no idea what they could be doing to their phones.

For the record though, I also planned on staying on my leaked 2.2 until I see what bugs pop up and if it's still rootable or not but I'm guessing it will be since using the Droid2 exploit works for the latest leaks.

 

[WAldenIV]

If I were to simply wait a couple of days once the OTA update is available, would the hacking community know if the bootloader had changed and what exploits would work?

My plan has been to avoided rooting and running custom ROMs,etc, until after the 2.2 update.

 

[dvader]

How can you possibly say that? Didn't they patch up the 2.1 root process by removing the sqlite_stmt_journals folder, our path to run the exploid file in root?

I'll expand
I'll be honest, I don't know what they did, so I'm not speaking from a position of knowledge on that issue, but if all they did was remove a folder, then that's not much of a patch.
my point was, that if they wanted to really lock things down they probably could have, but it's my understanding we can still root 2.2
and with froyo's impending release, it's unlikely they will hold it up for this new possible exploit. (just my opinion)