Want to hack but want to stay safe, what to do?

SpartyOnDX

Member
Sep 17, 2010
18
0
0
Ok, so I just bricked my last DX by trying to flash the OTA2.2 with the 2.1 SBF. Bad idea, as I found out. I want to mess with things, thats what I do, but I don't want to brick every DX I get and have to play dumb at VZW. I hate blur and feel my DX runs slower than it should. What are my options when I get the new DX?

Should I go with a leaked 2.2 so I can always flash back to 2.1? (correct me if I was wrong with that statement)

Should I go OTA2.2 and use what TBH leaked to flash if I brick it? Or will the locked bootloader cause other problems with ROMs and such?

Or something else?

I am a noob with all of this so I am bound to make mistakes, so I would like to have a "safe" way of hacking. Hey, I can only become a none noob by trying things, and learning from my mistakes, right?:cool:
 
Why don't you just install the leaked 2.2. It runs great, and if you ever want to upgrade to the official, you always flash that one back to 2.1 and run the OTA.
 
I would say to do some research first.

Read about the leaked 2.2 vs the OTA 2.2.

Read about the different custom ROMs and themes.

Read about the risks and what's needed to install the ROMs or themes.

Go through the threads about them around the internet and read about what people like and dislike about them.

It's all personal preference.
 
You should simply install the OTA 2.2 and wait a few weeks before doing anything else. You may find that your phone runs more quickly with the update. It will also give you time to research.
 
I know what u want to here. Root that bad boy. Dl launcherpro to get the blur away. Then run the leaked 2.2. Then hit up Flyx to kiss the bloat away. Then its up to you what u want. I got all that and added a black keyboard a black media gallery and a black notification bar.

sent by me on my X
 
There's no such thing as "safe hacking" - it's part of the fun! Want to stay safe and really hack? Your best bet is to get a Google developer's account and buy a developer's phone. You can use it on Wifi only and if you screw it up for a few days it's not a big deal. You can also look into a small tablet, that should be cheaper but many of them (like the Archos) seem pretty locked down and limited.
 
FYI, if I were you, I'd hope that when the new DX comes you even have a choice. I imagine at some point all the new DX's produced will probably come with the OTA 2.2 already on it. Until then though...

I'd suggest what I've done and I'll try and explain why. I have the leaked 2.3.15 Froyo applied over the Stock image available by one click in ROM Manager, with Tranquility installed after to blow away the Blur / Bloatware. With the leaked 2.3.15 update applied over the leaked 2.2 available easily in ROM Manager, you're basically at OTA 2.2, but without the new bootloader keys which caused your brick and prevent the 2.1 SBF from working. Granted that's kind of a mouthful, but if you manage to mess up along the way, you can always still SBF back to 2.1 :) As well, if you make a backup in ROM Manager before each step of the process, if you should mess up, at least you might save yourself a few steps the next time by restoring the backup you had of your progress.

While there's no such thing as "safe hacking" especially if you're new to all of this, if you don't OTA at least you can always go back. There's a bunch of things on other Android phones that you can't do / have to do differently on the DX. If all you're looking to do is install either Tranquility / FlyX / etc, then you're probably fine either way as long as you follow the Droid X specific guides. As well, make sure you get your hands on either the leaked "System SBF" for the OTA, or the leaked Full SBF for 2.1. The problem with the "System SBF" is that it won't fix everything. It should fix anything related to any theming you're going to do, but if you're going to try and do anything outside of that / install / build a custom ROM you better know what you're doing on the OTA IMHO, or at least follow a good set of directions and do so extremely carefully.
 
  • Like
Reactions: SpartyOnDX
ok, thanks for all the input. I think I will go the leaked 2.2 route. I really want to get rid of Blur and the bloatware so messing around with some roms will interest me. Trying to install tranquility is what lead me to bricking my DX.

One more question: If I go the leaked route...will it be pretty hard for me to completely brick my DX since I can always flash back to 2.1?
 
ok, thanks for all the input. I think I will go the leaked 2.2 route. I really want to get rid of Blur and the bloatware so messing around with some roms will interest me. Trying to install tranquility is what lead me to bricking my DX.

One more question: If I go the leaked route...will it be pretty hard for me to completely brick my DX since I can always flash back to 2.1?

Near impossible to brick it as long as you stay away from the OTA. (That rhymed, LOL :p )
 
  • Like
Reactions: SpartyOnDX
The main thing is to do a complete BACKUP of 2.1 and 2.2 stock. That way you have something to go back to after tasting everything out there. Im running Tranquility (off the 2.2 froyo found on Rom Manager) and loving it.

Sent from my DROIDX using Tapatalk
 
  • Like
Reactions: SpartyOnDX
Wait, so when I just bought my Droid X yesterday, came home and checked for updates, then a couple minutes later was on 2.2.......are you guys saying that was not a verizon update but a leaked version my phone downloaded on its' own??
 
Wait, so when I just bought my Droid X yesterday, came home and checked for updates, then a couple minutes later was on 2.2.......are you guys saying that was not a verizon update but a leaked version my phone downloaded on its' own??

Who said anything like that?
 
@Kurolover35

There is a leaked 2.2 floating around the webs that one can install and then there is the official one released by Verizon. From my understanding, the leaked 2.2 and the leaked update to 2.2 are the same as the official, EXCEPT that the official OTA2.2 (what you downloaded) version has a newly locked bootloader, that just simply acts as a pain in the a** for the hacking community and a general F.U. from Motorola.