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

Root DX (MB810) ezSBF & Root 2.3.4/4.5.621 (no milestone .sbf)

did you verify md5 checksum before mounting iso image to disc?
MD5 & SHA-1 Checksum Utility: verify the hash checksum to ensure the file integrity is correct with the matching file
Droid2_D2G_DX_DX2-RootCD-2012.iso
md5 Hash:7BAEE9C34F6EF7AD0B4FA219AE387C68
sha-1 Hash: 6D2A2019D746BBBCF0A92FFB60305B793381EDA6

if that is correct, it's your pc, usb cable, and/or phone
but now that you are rooted, doesn't matter, till next time
 
Upvote 0
thanks, it worked perfect BUT:
im removing stuff with titanium bckp and found this at the end of the list.

&#1092;&#1086;&#1085;&#1086;&#1074;&#1099;&#1077; &#1088;&#1080;&#1089;&#1091;&#1085;&#1082;&#1080;:&#1072;&#1091;&#1076;&#1080;&#1086;&#1074;&#1080;&#1101;&#1091;&#1072;j <<--can i remove it? is it needed for the root? or is a virus?

the icons on the side are a phone and an orange happy face..

it has no "run app" option, but does has the backuop and uninstall button..
 
Upvote 0
Hi. I went to Cricket store with my Verizon DroidX and paid $15 to connect this phone to an already existing line and also had it flashed instore.

Since then after I text more than a couple lines of texts I start having multiple problems. First, it alerts me on my phone that it is not sent. I try to re-send to no avail.

Secondly, supposedly it jumbles up my texts to weird symbols to whoever I am sending it to after approximately two text lines. Anything before it seems to send just fine.

I was hoping I could root my phone and hope that it solves the problem and also want to get tethering so that I can use the internet on my laptop off of my phone.

Thanks for anyone that can help!
 
Upvote 0
Yes did Handcents and it didn't help. Still after a couple lines of texts it sends the text to whoever I sent it to in jumbled letters/symbols. Then it shows "not sent". I try to re-send and it does the same thing. When I shorten my text then it sends.

If it wasn't a feature I use to death then I probably wouldn't be so adamant about trying to find corrective action.
 
Upvote 0
I read this thread and had the night by myself soooooooooooooooo...........lol

Thank you so much:) The trusty old DX was put away and i have been using my S3 but decided to root. I had root prior to .621 and flashed lots of roms but gave up on things when the over the air came. My camera button is broken so i could not root anyway until i read your rooting method. I saw that i could root without using the camera button:)
This worked 100%. Again, thank you so much. If i ever need a backup phone, i now can use my DX (needed root to use the Droid Firewall to stop data use).

Lenny
 
Upvote 0
Thanks to the assistance of CoolPeote & others I got my DroidX to work on 621, including working wifi. I pretty much haven't done much with it since. Now I'm looking to get service through page plus cellular, so I'm back trying to see if I can update the phone to cm7.2 or cm9 beta.

Before I make an attempt, I want to be sure of one thing: all of the instructions I find say to "place the CyanogenMod update.zip in the root of the SD card". However, there isn't a single place on the cyanogenMod site for such a file, they're all named somethingElse.zip. Is it simply a matter of renaming the nightly or release build file of my choice from whatever.zip to update.zip?

One thread said he tried that and it failed. Also, if that is the procedure it surprises me nobody lists the rename step. Equally surprising is a lack of the update.zip file so many threads mention.

I've got the hammer cocked and am ready to pull the trigger, just want to know before I do the gun isn't going to blow up in my face.
 
Upvote 0
Upvote 0
I had found your guide & read it before I posted the note here. Its hard to find a source for cm, but managed to. I downloaded cm-7-20121209-NIGHTLY-shadow.zip, Pooka-CM4DX-GB-20120519.zip and CM9-beta-DX-08122012.zip Of these I was only able to successfully install Pooka, which was a cm 7.1 rom.

I was previously running the 4.5...621, which is a 2.3.4 gb kernel. After the Pooka install the kernel was 2.6.32.9-g1282440..., built May 20, 2012. The Android version is 2.3.7

Going from memory since last July, I recall I cannot sbf to anything earlier than .621, so that is my starting point. Is that correct?

I don't recall how I managed to install .apk files from sdcard when on .621 last July, but somehow managed to. After installing Pooka I still had that issue, but just installed afresh from market using wifi.

What is the latest CM I can install on my droidX, and what prevents me from updating the kernel if anything? Although I can't go back earlier than 621, I would like to go forward to ics or beyond as newer code becomes available.

I presume the locked bootloader is no longer an issue, now that exploits have been found to circumvent it. Or are those exploits limited to work only on the gb kernel?

I must admit I'm still a bit confused about the whole "locked bootloader" problem. If the bootloader is separate from the kernel and is in essence in non-updatable ROM, seems like anything could be loaded with the exploits found.
 
Upvote 0
Its hard to find a source for cm,
Pooka's CM7 link in my list
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs

Going from memory since last July, I recall I cannot sbf to anything earlier than .621, so that is my starting point. Is that correct?
correct

I don't recall how I managed to install .apk files from sdcard
just use file manager or root browser, select, will ask if you want to install
What is the latest CM I can install on my droidX,
on stock install D2 bootstrap, update cwm to dx 2nd init, on custom rom use what comes with rom
and what prevents me from updating the kernel if anything?
bootloader, little more complicated than that, but basically that's it
Although I can't go back earlier than 621, I would like to go forward to ics or beyond as newer code becomes available.
there will not be any official update, so stuck with gb kernel, think there is a cm9(ics), but latest working rom is MIUI DefX by Wizard0f0s

I presume the locked bootloader is no longer an issue, now that exploits have been found to circumvent it. Or are those exploits limited to work only on the gb kernel?

I must admit I'm still a bit confused about the whole "locked bootloader" problem.
bootloader is still locked, lots of threads on the bootloader
If the bootloader is separate from the kernel and is in essence in non-updatable ROM, seems like anything could be loaded with the exploits found.
no one has got that to work
 
  • Like
Reactions: droidmanx1
Upvote 0
My Quote:
What is the latest CM I can install on my droidX,
You replied: on stock install D2 bootstrap, update cwm to dx 2nd init, on custom rom use what comes with rom

When I said "CM" I meant CyanogenMod, not Clockwork Manager. However, the rest of your post generally gave me the answer, CM9. Since the DroidX is currently limited to GB kernels, it puts a cap on the CyanogenMod versions available, as they are tied to specific kernel requirements.

And based on what I've read about CM9Beta, it seems to suck battery, so CM7.1 might be the best - latest version.

I have yet to look at other ROMs, like the very popular Mui, or Liberty ...

I might be an expert computer geek but far from a phone power user.
 
Upvote 0
Since the DroidX is currently limited to GB kernels, it puts a cap on the CyanogenMod versions available, as they are tied to specific kernel requirements.
that's not quite right, several moto phones have cm10 now on gb kernel, M2, DX2, D3.... , it's just not easy and may never be fully working roms
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones