Database Users

[Q] Stubborn Droid 2

To preface, I've been off the phone hacking/ROM flashing scene for a couple years now; previously working with Windows Mobile, so I know a lot has changed but I'm not largely unfamiliar with the general process of what we are doing here.
Droid 2 In Question:
System Version - Version.2.3.20.A955.Verizon.en.US (After OTA Update 03 NOV 10)
Baseband - BP_C_01.09.07P
I've got a stubborn Droid 2 that just WON'T boot to recovery. I bought a fresh Droid 2 last week, rooted via the 1-2-3 'One-Click' successfully. Then I attempted to follow AngDroid's Fission install step by step for my first ROM flash. http://forum.xda-developers.com/showthread.php?t=823473
Issues:
ROM Manager wouldn't do ANYTHING when I would select 'Reboot into Recovery' or attempting to select ROM using 'Install ROM from SD Card'.
Found and installed Koush's Bootstrapper, got 'SUCCESS!' pop-up when selected 'Bootstrap Recovery' yet when I tapped 'Reboot Recovery' nothing happened.
I then attempted to re-install the SBF (which I'm still not 100% clear on what the role of the SBF is, perhaps just the Baseband?) using both AngDroid's instructions in his Fission thread as well as using RSD Lite 4.7+patch AND 4.8 AND 4.9 instructions from this thread. http://forum.xda-developers.com/showthread.php?t=827624 All those attempts where unsuccessful. RSD wouldn't allow me to 'Start' the SBF flash which I can only assume is because I had the latest version on my Droid 2.
I then decided to restore my phone to factory and start over, so I booted the device pressing x, then search and selecting wipe data/factory reset. Once done, it rebooted and to my surprise it still had the Superuser Permissions app that was installed during the 1-2-3 One-Click process.
I went as far as to install the full Android SDK/Eclipse setup for ADB use and continued to run into 'operation not authorized', 'root not allowed on production ROMs' and 'failure' with any command attempting to remove SU Permissions app and install a diff. SU app/reboot into recovery.
I checked to see if I still, in fact, had SU permissions by re-installing Barnacle, it stated that it needed su but the Superuser Permissions app never prompt me to authorize su. There is also no way (that I see) to manually authorize su for barnacle, or any app, in the SU Permissions app.
Way Forward?
I believe that I either need to re-root and try to reboot to recovery again but I am not confident that will work.
I am starting to think that ROM Manager and Droid 2 Bootstrapper apps didn't have SU and might be why they didn't respond when I selected 'Reboot Recovery' options? As I stated I do not know how to manually authorize.
With this information, what am I to do from here?

That's strange. After root, you should be able to install SU from the market if the one click root doesn't already do it for you. When you run Koush's bootstrapper, the first time you should get a pop up from the SU program asking you if you want to allow or deny the bootstrapper. After that, everytime you load up the bootstrapper you should see a little pop up stating that it has been granted superuser privileges.
Try rooting again, this time use the 1 click root for 2.3.20 found here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html, and then go through the steps again and report back

Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?

wjones said:
Thanks. I will check it out when I get back home this evening. Can you outline the process if I wanted to wipe the device as if I pulled it out of the box, will no SU app or anything and start from scratch?
Click to expand...
Click to collapse
Id wipe cache and wipe data/factory reset and start fresh. I've never had any of your problems and I think they can be fixxed with a factory reset.

Sounds like you didn't get rooted properly.
If it were me, I'd sbf and start over.
- Charge battery fully
- Get drivers from Motorola and install them (wait for it to finish)
- Get RSD 4.8+, and 2.3.20 sbf (make sure you get the full file)
- Wipe data and cache in stock recovery (access by power + X key, then search key)
- Boot into bootloader (power + Up key)
- Load RSD and make sure your device shows
- Choose the sbf and click Start
If you follow those steps exactly and sbf doesn't work, then you probably have a hardware problem either on your phone, your PC, or the USB cable.

karnovaran said:
Sounds like you didn't get rooted properly.
- Boot into bootloader (power + Up key)
Click to expand...
Click to collapse
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!

wjones said:
Perhaps this is why RSD wouldn't let me flash before. I hadn't known about this. RSD always showed the device (which was in PC Mode and Debugging mode) but the START button was greyed out. I will certainly try again from the Bootloader. Thanks!
Click to expand...
Click to collapse
Yeah I don't know why some methods recommend PC Mode. Sbfs are meant to be flashed in bootloader.

Honestly, it sounds like everything is working like it should be, it's just some steps are being skipped or overlooked. Like the SBF in bootloader, and the sbf doesn't erase your data, you need to do a factory reset after sbfing so thats why your superuser app was still there.
There really is no such thing as a phone being stubborn, and majority of errors like that are from the user. Not to be insulting but thats just the case. The only time I have ever seen a stubborn piece of hardware is from overclocking, where some can go higher than others due to having a better piece of wafer. But if you rooted correctly, bootstrapped, etc, there is no reason that you wouldn't be able to install a ROM.

Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App

wjones said:
Alright! So the issue was two things that kept this ish from working. 1) I needed to unroot from the initial root tool. It was definitely working ton some level because I could run barnacle and auth su but clockworkmod stuff wouldn't. 2)I OTAd before unrooting and that, while less likely, possibly gummed up the gears!
I am now re-rooted on 2.23 or whatever and will flash Fission later.
Thx for the help!
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Is this solved now? May I close it?

Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App

wjones said:
Let's wait until I can attempt the flash. Might have a problem still but things are looking good so far. Will report back once flash is done!
Thx
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
No problem! I'm in no rush to close it, was just curious Hope it all goes well

DONE!
It worked like a charm! Thanks for all the support!

wjones said:
It worked like a charm! Thanks for all the support!
Click to expand...
Click to collapse
Awesome. Could you add [SOLVED] to your thread title before the mods close it?

[Q] Can Someone Tell Me What I'm doing Wrong?

This has happened to me twice now, I've had to replace my D2 because it keeps bricking for some reason. I don't know why, but now whenever I try to download something from my SD card (a rom or a theme) It just bricks. I go to mounts/storage, click on that then I go to download from SD, I select my rom and it doesn't work. It'll go to the boot logo, show Matt's logo (I used Matts Epic2.5) and won't stop repeating it over and over again.
Sometimes it'll show the whole logo, then after maybe 5 times it'll show half the logo then stop and keep repeating this process. I don't know why, but it used to always work in the past. What am I doing wrong? Do I need to wipe my data and cache every time now? I never had to before.
I really miss my Droid 1 (root wise lol)

BTW, I don't know if this means anything, but do I need to deodex my phone or however you say it :S, sorry I'm really new to droid 2. I don't even know what deodex means lol. Anyone help me on explaining what that means?

Deodexing or de-odex-ing is how it makes more sense to me just means that all of the apk's or applications on your phone are together and don't have stray .odex files in the /system/app folder (or wherever they're located). Phone dev's will leave these .odex files out of the .apk's so that load times are supposedly faster but the file called services.jar which needs to be edited for detailed themes has to be de-odexed before it can be edited and if one file is de-odexed then the others should all be.
I'm not sure what specifically the problem is and please don't be offended if I'm going too far but in order to mount /system the entry in mounts/storage has to read "unmount /system". Make sure the you've got the entire ROM, but wiping cache and data is worth a shot too.
Also if you have a major problem with your droid 2 you just need to flash the .sbf there are two different ways to do it (and two versions of the sbf). One in windows and the other in linux and (thanks to me lol) the linux version is available to anybody with a windows computer too.

Yeah I fixed my phone today using the windows sbf. Do you think it's worth it to deodex my phone? And I don't know what the problem seems to be I have the full rom and I never had to wipe before :/ I guess I'll just wipe every time now.

Most of the ROM's now are de-odexed so you shouldn't have to the only reason you would need to is to theme. To check and see if it's deodexed just use Terminal emulator and enter
Code:
$ cd /system/app
$ ls
This means change directory to /system/app then list the files in there.(it's a lower case L)
If there are files that end in .odex then it's not de-odexed.

UPDATE: I sbf my phone and got it "unbricked". So I just got root access and then I tried to instal the 2.5 Epic Rom. These are the steps I went through.
1. Went to Titanium Backup and restored my Droid Bootstrapper app.
2. Opened the app and did the Flash Recovery, is said success then I went into recovery mode.
4. I went to Mounts and Storage, pressed OK on Mount/system
5. Went to Install from SD Card.
6. Went to EUnleashed2.5 (however it is)
7. It installed only halfway and said install is complete and the screen would just sit there when it was only less than halfway full.
9. Now my phone is bricked again and I am currently unbricking it.
What am I doing wrong?
EDIT: By the way, if those things that I clicked on aren't exactly right, it was because I was typing it from memory because my phone was bricked and I couldn't actually see them.

First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.

karnovaran said:
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
Click to expand...
Click to collapse
Lol thanks, that makes a lot more sense to me now. I just saw his post about 3.0, I can't wait till it comes out. Thanks for the help!

Tried to install Liberty on my Droid X, messed up, stuck in a hole, plz dig me out

Up until today I never did anything to my droid x as far as rooting and roms. I kept everything completely factory and android was at its latest version which is gingerbread 2.3.3 and system version 4.5.605.MB810.Verizon.en.US.
My goal today was to finally experiment this and install Liberty Rom. I completely failed because of all the version complications and plenty of other errors. Before I describe my final problem I should backtrack and let you know exactly what I did today so you can possibly get me out of this mess.
1. The very first thing I did was follow all of the steps at a forum on droid-life "How To: Get Rooted Gingerbread On DROID X" sorry it won't let me post the link.
After all of this I ended up with gingerbread again, but I guess a rooted version. No idea why this was the tutorial I followed when trying to install liberty. Throughout the tutorial I ended up buying "Droid X BootStrapper" because the tutorial had me use it.
Right after this tutorial I bought an app called Rom Toolbox for $5.00 downloaded Liberty through it and was trying to install through it. Every time it rebooted I would get a black screen. Never worked so many issues probably because I flashed the wrong sbf or something.
Here are the programs that I ended up buying today:
z4root (free), DroidXBootStrapper ($2.00), Rom Toolbox ($5.00).
That is everything I have done and all of the apps I own. Can someone please start fresh and give me short instructions to start from scratch on how to get the latest and greatest version of Liberty on my droidx from where I'm stuck at now. I want to completely start over and I am willing to do anything. I hope the apps I bought help and I also want to assume 2 of them probably do the same thing and I didn't need them.

Buying those tools will at least help support 2 members of the community (Koush & JRummy).
I'm pretty sure Z4Root does not work on the GB versions of DX firmware. That's probably why nothing is working. You aren't actually getting root.
you are on the .605 version of GB (when you see references to .602, .605, etc ...)
To get root, start here:
http://forum.xda-developers.com/showthread.php?t=1258599
You may also want to download the Droid2 recovery rather than the DX. The D2 version is a little newer and I think avoids a slight bug on later kernels when Debug is on. The D2 version works just fine on the DX. It can be downloaded free from here:
http://www.koushikdutta.com/2010/08/droid-x-recovery.html
Once you are rooted and have recover properly working, you should be able to use the Rom Toolbox to download and install Liberty. Just make sure you read carefully about the 'version' requirements on any ROM.

Oh ok so I was rooting it wrong.
I easily rooted the phone using Pete's Motorola Root Tools. I realized that Rom Toolbox Pro accesses clockwork recovery when the phone is rebooted instead of the phone just restarting fully. But, I still want to start fresh and do everything from the start again. Please let me know if you have any suggestions in the way or order I am doing things. My phone is currently up rooted at 4.5.596 and rooted by Pete's Motorola Root Tools but I want to start over from the beginning so here is what I am going to do:
Note: Before I do anything I am going to format my SD card for a fresh start.
1. Use RSD_Lite 4.9 to Flash my phone back to 2.3.340 using a file called VRZ_MB810_2.3.34_1FF_01.sbf. I always do this part with no problem.
2. Do a hold power+home then search and do a system wipe/restore. Then Activate service, sign into gmail etc.
3. Now that the OS is loaded (the old version with the grey bars 2.3.340) I am going to root my phone using Petes Root Tools. (I hope I can root it with this tool when the firmware is this version.)
4. Put the 3 zip files I have on my SD card to upgrade to GB 588. Also put my GB 596 file on here.
5. I will download 1 app. D2BootStrapper. Bootstrap recovery, reboot into recovery. Install all 3 zip files from SD card. Now I boot up in GB 588.
6. Now I go right back into D2BootStrapper. Bootstrap recovery, reboot into recovery. Install GB 596. Now I have GB 596 rooted and loaded.
7. After this, shouldn't I be able to download Rom Manager Premium and Rom Toolbox Pro and test as many roms as I want? always reverting back to my original backup.
I noticed after installing liberty I was getting all kind of force close popups. And the phone wouldn't connect to service. But then I just held power + home then hit the up/down arrows and did a wipe/restore and it loaded liberty and everything works. Is this normally what has to be done when installing roms?
If there is anything wrong with my process please let me know. Whew I can't believe all that I learned in 1 day.

You've got a lot of steps there that really aren't necessary. When you install a ROM like Liberty, it replaces EVERYTHING in /system. Thus, about all that is left from a .596, .588, .602, etc install is the kernel. The Kernel doesn't change very often in Motorola builds. The last change was on .602. Thus, for your purposes there is no difference between .602 and .605 (FYI, .605 was just a keyboard fix over .602).
So, if you search around, you should find an SBF or AIO flash file to get you to .602.
Or you can simply take the OTA update from VZW after SBF'ing to .340
Once you've flashed your Rom, be sure to clear data/factory reset. You should then start with a clean system.

Alright, if you don't mind can you please let me know what steps I can avoid.
I didn't think it was possible to have a rooted .605 but I guess I was wrong.
So my goal should be to get to .605, then root it. Then install roms from there?

On your first post you said you were on .605. I'm assuming that is still the case.
If so, then root it with pete's tool (I think you've already done that).
Install D2bootstrap, then ROM Toolbox and install your rom from there.
I have to be honest, in that I've not used Liberty in a while, nor have I used Rom Toolbox. It shouldn't be a problem, just make sure that the version of Liberty you are using is for the GB kernel. Some of the older versions of Liberty (Which I did use, and like) were for the Froyo kernel (in that case, stay on .340 and do your upgrades).
Make sure you wipe data in recovery after installing the ROM. Lots of 'Boot Loops' are due to not wiping data after flashing a new rom.

Yeah
Yeah I read up on all of that. I actually might not end up going with Liberty. Going to try others like ICX. But before I do any of this I need to get to .605.
No I am not at .605 I believe that's where my phone was before I started all of this.
Right now I am flashing back to 2.3.34
Once I am back up and running there. Can you please recommend the easiest way to get to .605 and that will be my final question.

.605 should update automatic. If not you can disable the updater using titanium backup by freezing system updater.
1. Use petes tools install cwm as well
A. Droid x bootstrap get this
B. Titanium backup. Backup your apps
2. Make a backup using cwm and backup apps with tb
3. Put the rom zip files on the sd card.
4. Reboot to recovery. Reformat system data etc
DO NOT REFORMAT THE SD CARD.
5. Wipe cache davik etc.
6 flash rom. And reboot.
7 run tb for your apps
Should be a smooth and clean install. The roms are already rooted so no need to worry about that. Hope this helps
Sent from my MyTouch 4G Slide using xda premium

We aren't supposed to link to other forums, so expect this link to get removed.
http://rootzwiki.com/showthread.php?399-UPDATED-GUIDE-LINKS-DX-SBF-s
I would point you to a link here, but couldn't find a quick/easy link to what I wanted.
In this list is an SBF file for .602. Since you seem comfortable with doing SBF's, I would just SBF straight to .602 and root it from there.
Don't know much about ICX, but would encourage you to look at the CM7DXGB thread over at Rootzwiki as well.

ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.

HunterT said:
ohh, well I just went to Settings > About Phone and its auto updating to .605
Am I not going to be able to root it after this update or should it be fine.
Click to expand...
Click to collapse
Pete's Root tool should root .605 just fine.

One last thing
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?

Zaphod-Beeblebrox said:
Pete's Root tool should root .605 just fine.
Click to expand...
Click to collapse
Pete's will work on .605 I did two the other day
Sent from my MyTouch 4G Slide using xda premium

HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
Couple things most of the updates are to add support fix minor bugs etc.
I run the one from petes all the time I forget which version. I haven't had problems.
On my mt4g slide I had to flash a modified verson of clockwork due to my phone being newer and not as much support
With that said its not a difficult process to get a new recovery image. You would need terminal emulator and root explorer. Couple of great guides on here on how to do so. Also other methods as well.
All in all the ones that pete's give you should suffice. Unless your one of the extreame types of people who want the newest or like messing around.
Just remember backups can make the process and hassle of soft bricking your phone much easier to fix and takes a few mins to do.
Look around the forums lots of great information from the devs, experts, etc
Sent from my MyTouch 4G Slide using xda premium

HunterT said:
As far as Clockwork recovery goes.
Should I always be in the latest version 5.0.2.0 (the blue version)
Or the old version 2.something (the green version)
Why is there 2 version and why would I ever want to flash back to the old version 2.something?
Click to expand...
Click to collapse
The newer version changes the way backups are stored. The new format is smaller and quicker.
Among other issues/bug fixes as mentioned before, but the backup issue is important as the new version will not restore the old style backups.

Looking for Help

Ok watched video and liked it. Next running the current (as of last nite) Cm7. Would like to get the camera working have read some of the threads. Best I can figure its not happening. Also having some problem viewing youtube videos. Is there a rom that solves these problems or should i go back to some form of mod gingerbread. Or what?

I believe you are using the official CyanogenMod nightlies, correct?
The official nightlies don't incorporate the fixes for video and other media out of the box.
You could install the fixes, but you will have to Google around and find them, then install the zip in
I recommend using the unofficial CyanogenMod nightlies over in the Rootzwiki Droid X Developer Forum.
It supports all the fixes plus 720p video playback, as well as other fixes.
If you're interested find the thread and follow the instructions given.
Sent from my Transformer TF101 using XDA App

http://rootzwiki.com/topic/10191-updated-info-on-revnumbers-cm4dx-gb/
There is the thread on RevNumbers.
And I agree that those are the better bet for CM7.
Since you appear to be on official...
You're not on the correct kernel to flash RevNumbers nightlies.
Make sure you are (I don't think you are) on .602/.605 system version.
Follow the usual procedure to back up your applications with Titanium Backup and all that good stuff...
Then SBF to .602
http://rootzwiki.com/topic/331-guide-flashing-droid-x-sbf/
My signature has a more thurough walkthrough of the actual backing up/re-rooting/flashing procedure if you need it.

Definitely suggest going to the gingerbread based cm7 on DX. There's two different releases of it just compiled on 01/07/2012 and instructions for applying any fixes are in the OP. The only one necessary for certain is the camera fix. If you need help, I can give you a hand, but not FAST, as I'm at work during regular business hours M-F EST

base BP_C_01.09.07P
kernel 2.6.32.9-g55626e1 [email protected]#1
mod cyanogenmod-7-11162011-nightly-droidx
build cyanogen_shadow-eng 2.3.7 gingerbread eng.buildbot.20111116.084404 test-keys
Ok so you folks are saying that i loaded the nightly and need to get the full os before the nightly ok. while i'm in the is there anything that can be done about under volting be low 300 to save battery. Do i need a updated radio or kernel?

speops38 said:
base BP_C_01.09.07P
kernel 2.6.32.9-g55626e1 [email protected]#1
mod cyanogenmod-7-11162011-nightly-droidx
build cyanogen_shadow-eng 2.3.7 gingerbread eng.buildbot.20111116.084404 test-keys
Ok so you folks are saying that i loaded the nightly and need to get the full os before the nightly ok. while i'm in the is there anything that can be done about under volting be low 300 to save battery. Do i need a updated radio or kernel?
Click to expand...
Click to collapse
Kernel is the problem...but we can't manually update our kernels.
Do a nandroid (just in case) and titanium backup.
Then sbf to .602. This will update your kernel for you (and is the best [only outside of certain update.zips that rom manager provides] method).
Root using the method detailed in my sig.
And flash the rom.

Ok sbf too .602 but having problems rooting tryed pete's tool but it just sits there. if i reboot my computer it says to connect my phone then just sits there. tryed z4mod 1.3.0 it keeps force close. Any ideals ? Also ever time i plug phone in to computer it trying to open window for verizon backup page.

speops38 said:
Ok sbf too .602 but having problems rooting tryed pete's tool but it just sits there. if i reboot my computer it says to connect my phone then just sits there. tryed z4mod 1.3.0 it keeps force close. Any ideals ? Also ever time i plug phone in to computer it trying to open window for verizon backup page.
Click to expand...
Click to collapse
You make sure USB Debugging was enabled?

Yes it was in and used same port for sbf. ? When using rs and it boots phone it shows 100% on 1 column but the next 1 says in progress. How long should I allow this to care on before unplugging it. Shave sbf 2 because the phone app wouldn't let me call out. It would show contact and green phone and click when you touched it but nothing happened.

Ok here where we are at.
1) went in and checked the debugging and allow unknow source (nobody said anything about this but tryed it at this point). Used moto 5.4.0
2) I have sbf .602 using rsdlite 5.4.4 (left the cable in the same port for the rest of this).
3) wiped data using the power & home button to get to the bios menu.
4) tryed to boot with pete's tool v1.07 ( it just sat there waiting for the phone to be hooked up)
5) tryed just for fun Z4mod 1.3.0
6) Read some more tryed the Droid 3 easy root v7 it ran half to night sitting there waiting for the phone to be hooked up.
So what am I missing??????

speops38 said:
Ok here where we are at.
1) went in and checked the debugging and allow unknow source (nobody said anything about this but tryed it at this point). Used moto 5.4.0
2) I have sbf .602 using rsdlite 5.4.4 (left the cable in the same port for the rest of this).
3) wiped data using the power & home button to get to the bios menu.
4) tryed to boot with pete's tool v1.07 ( it just sat there waiting for the phone to be hooked up)
5) tryed just for fun Z4mod 1.3.0
6) Read some more tryed the Droid 3 easy root v7 it ran half to night sitting there waiting for the phone to be hooked up.
So what am I missing??????
Click to expand...
Click to collapse
After you SBF you must recheck USB Debugging.
Sent from my Transformer TF101 using XDA App

I have checked a number times!!!! Also how well does factory wipe clean these because this phone was rooted before. What about the dalvik memory?

speops38 said:
I have checked a number times!!!! Also how well does factory wipe clean these because this phone was rooted before. What about the dalvik memory?
Click to expand...
Click to collapse
Try using a different USB port or a different computer. Also, try reinstalling or updating your moto drivers.
A data wipe won't remove root, but SBFing will. It's always safe and recommended to wipe the dalvik cache.
Sent from my Transformer TF101 using XDA App

Planing on trying a different computer on Saturday.

New problem!!!!
1) got a 64bit windows laptop loaded moto usb driver
2) booted computer and checked phone for usb debugging on
3) down loaded pete's one step root
4) unzipped and ran program it said it was looking for phone plugged it in
5) pete's tool took over and rooted .602
6) went into market and got droid2 paid ran it
7) wiped data and wipe dalvik
8) loaded cm7 154 and it said something about wrong kernel.
9) rebooted
Now it will not let me back into clockwork.
10) try droid X bootloader try going though rom manger
no luck it goes blank but the screen is still some what lite.
Help!!

speops38 said:
New problem!!!!
1) got a 64bit windows laptop loaded moto usb driver
2) booted computer and checked phone for usb debugging on
3) down loaded pete's one step root
4) unzipped and ran program it said it was looking for phone plugged it in
5) pete's tool took over and rooted .602
6) went into market and got droid2 paid ran it
7) wiped data and wipe dalvik
8) loaded cm7 154 and it said something about wrong kernel.
9) rebooted
Now it will not let me back into clockwork.
10) try droid X bootloader try going though rom manger
no luck it goes blank but the screen is still some what lite.
Help!!
Click to expand...
Click to collapse
You tried to flash a Froyo kernel rom over stock Gingerbread (using the Gingerbread kernel), which bricked your device.
SBF back to .602, root again, and flash RevNumber's unofficial CM7 nightlies (and Gapps) from RootzWiki.
Sent from my Transformer TF101 using XDA App

Found the problem. When using rslite you need to un zip the .602 file do not us rslite to uncompress it. It was making a bad os on phone once i did that it loaded and rooted like clockwork. Thx for all you folks hanging in the with me.

Android Ver 2.3.7
Base Ver bp_c_01.09.13p
kernel ver 2.6.32.9-g34b306d [email protected]#2
mod ver cyanogenMod-7.1.0-DROIDX-KANG
Build Num GRH78C
So what is next? Can i do nightly from here? Is there anything else to install

speops38 said:
Android Ver 2.3.7
Base Ver bp_c_01.09.13p
kernel ver 2.6.32.9-g34b306d [email protected]#2
mod ver cyanogenMod-7.1.0-DROIDX-KANG
Build Num GRH78C
So what is next? Can i do nightly from here? Is there anything else to install
Click to expand...
Click to collapse
You can flash RevNumber's unofficial nightlies. Attempting to flash an official nightly will brick your device.
Sent from my DROIDX using XDA App

Milestone X on Ntelos- Suggestions?

I know a noob making a new thread is bad, but I feel like I need very specific advise here.
I've been running Cyanogenmod for years, it was unstable, no progress was being made, I could not use many of the phones functions and once 2.3 officially hit the Milestone X on Ntelos I decided, "Hey, I think I'll take the official rom and just root it".
So I SBF's back to an official SBF and for about a month I did everything I could to get an OTA update to roll out, it never came. I got antsy and searched the web for a 2.3 SBF for Ntelos and found one with the filename
1FF-p3a_shadow_cdma_shadow-user-2.3.5-4.5.1_57_MX2-34-111019-release-keys-signed-ntelos-US.sbf.zip
Which I found on MotoSBF
So it worked, I managed to root it and it's been horribly unstable, so about a month ago I decided that I'd take Cyanogenmod with all of it's faults over this. In reading over the threads here I found my DX Bootstrap would no longer work so I got DX2 BS, and installed Clockwork Mod Droid X 2nd init. Previously I had attempted DX BS which when flashing Cyanogenmod I'd get a boot error, I think I have made progress with the DX2 bootstrap as I no longer get a boot error I just get stuck with the M logo forever.
So would I be correct maybe to assume that it's Cyanogenmod that is now my issue? I want a custom rom that is at least gingerbread and pretty clean/fast, I don't know which ones work on an Ntelos Milestone X except MIUI (and I have to be honest, I HATE MIUI, the cluttered desktop feel of the iOS is one of the things I hate most about iOS in the first place).
I just need two bits of advice here, is the ROM I'm flashing most likely the issue, and if so, what ROM would you suggest for my particular phone.
And let me also check if my steps are correct.
I install DX2 Bootstrap Recovery
I install Rom Manager and my Premium, flash clockwork recovery DX 2nd Init.
I boot into DX2 Bootstrap Recovery, factory reset, install ROM from SD Card.
That sound like proper procedure being I'm on the latest OTA rooted?
*edit I should add that I have attempted to go back to previous versions, but that does not work out sadly*

misfit410 said:
I know a noob making a new thread is bad, but I feel like I need very specific advise here.
I've been running Cyanogenmod for years, it was unstable, no progress was being made, I could not use many of the phones functions and once 2.3 officially hit the Milestone X on Ntelos I decided, "Hey, I think I'll take the official rom and just root it".
So I SBF's back to an official SBF and for about a month I did everything I could to get an OTA update to roll out, it never came. I got antsy and searched the web for a 2.3 SBF for Ntelos and found one with the filename
1FF-p3a_shadow_cdma_shadow-user-2.3.5-4.5.1_57_MX2-34-111019-release-keys-signed-ntelos-US.sbf.zip
Which I found on MotoSBF
So it worked, I managed to root it and it's been horribly unstable, so about a month ago I decided that I'd take Cyanogenmod with all of it's faults over this. In reading over the threads here I found my DX Bootstrap would no longer work so I got DX2 BS, and installed Clockwork Mod Droid X 2nd init. Previously I had attempted DX BS which when flashing Cyanogenmod I'd get a boot error, I think I have made progress with the DX2 bootstrap as I no longer get a boot error I just get stuck with the M logo forever.
So would I be correct maybe to assume that it's Cyanogenmod that is now my issue? I want a custom rom that is at least gingerbread and pretty clean/fast, I don't know which ones work on an Ntelos Milestone X except MIUI (and I have to be honest, I HATE MIUI, the cluttered desktop feel of the iOS is one of the things I hate most about iOS in the first place).
I just need two bits of advice here, is the ROM I'm flashing most likely the issue, and if so, what ROM would you suggest for my particular phone.
And let me also check if my steps are correct.
I install DX2 Bootstrap Recovery
I install Rom Manager and my Premium, flash clockwork recovery DX 2nd Init.
I boot into DX2 Bootstrap Recovery, factory reset, install ROM from SD Card.
That sound like proper procedure being I'm on the latest OTA rooted?
*edit I should add that I have attempted to go back to previous versions, but that does not work out sadly*
Click to expand...
Click to collapse
your missing a few steps I believe that maybe is causing your instability issues there is a newer version of clockwork mod that is more suited for your phone download rom manager and flash for the droid x its 5.0.2.0 click reboot into recovery after flashing new recovery
1 wipe/data factory reset
2 wipe cache partition
3under advanced wipe dalvik
4under mounts and storage wipe/format system (for some roms read op instructions for flashing)
be very careful with 4 if you reboot on accident you will be left without a system on your phone!!!!
5 flash the rom and the gapps recommended for that specific rom
6 reboot system
all these apply to flashing in one form or another for a clean install omit #4 if you are fearful most roms these days format the system before installing anyway pooka`s cm7 charge while off seems to be very stable for me try at your own risk like any rom yacks cm7 is good to plus it allows updates through goo app in market but I noticed fc`s with adw launcher when switching to landscape mode but overall not bad

Gave it a go step by step, end result is still just a locked Motorola logo

If everything you have tried has failed it definitely to be the ROM. As a side note i think a root can be unstable because the os linux is very unstable. My pre update root to gingerbread was unstable. I even had linux on my PC and it was just as unstable.
Sent from my DROIDX using xda premium

In another thread I found someone mentioned trying to install CM with the bootloader updated, and they posted a ROM that was pooka-something..
worked like a charm..