Since this is the Droid X, what will it take to get CM7 on it? Basically do the kernels match? And will the baseband be updated? I can test it as long as I don't get stuck with a Verizon baseband, as I've already had to take one back because of that.
The stock ROM shipped with mine, which is on the Cellular South network, has the following:
System Version: Version.3.2.6.MB809.ACG-CellSouth.en.US
Android version: 2.2.2
Kernel: [email protected] #2
Baseband: BP_C_02.06.00R
I attempted to install the CM7 nightly 3 and it simply aborts the installation with "assert failed: run_program("/tmp/check_kernel") == 0"
Let's get this working because i'm sure there are other Milestone X owners who would love to be running CM7!!!
We will see. I think we Milestone Xers will be fine. Having used CM7 on an nTelos Hero and that had some Sprint stuff in it. Did not affect affect the radio at all. Should be just a ROM and that is it.
You might actually need some special attention from cvpcs on this one. Since we still can't load custom kernels on the X, this 2nd init process is little bit sorcery
This process only works with our froyo kernel. My guess is that the check_kernel script mentioned above will fail for Milestone people. Your kernel version will be slightly different.
I assume the process would work ok with your kernel, but the script might need to be modified to allow your version.
What is a Milestone X? The Droid X is the Shadow.
the milestone x is the basically the same phone as a droid x but without the droid branding builit in and is carried by regional carriers. hardware and specs are identical. as noted, there may be some differences in the kernal or software that may cause issues. i am not worried though. someone will attempt to load cm7 on one and we will see what happens and then someone will most likely figure out a work around for any issues. i won't be that guy though. i need the phone for work, so i will hold off until the kinks are worked out.
Zaphod-Beeblebrox said:
You might actually need some special attention from cvpcs on this one. Since we still can't load custom kernels on the X, this 2nd init process is little bit sorcery
This process only works with our froyo kernel. My guess is that the check_kernel script mentioned above will fail for Milestone people. Your kernel version will be slightly different.
I assume the process would work ok with your kernel, but the script might need to be modified to allow your version.
Click to expand...
Click to collapse
The check_kernel script looks for:
"Linux localhost 2.6.32.9-g55626e1 #1 PREEMPT Sun Nov 7 23:24:32 CST 2010 armv7l GNU/Linux"
uname -a returns:
"Linux localhost 2.6.32.9-gace4441 #2 PREEMPT Mon Feb 7 18:23:06 CST 2011 armv7l GNU/Linux"
Sent from my Milestone X using XDA Premium App
abcleanonme said:
The check_kernel script looks for:
"Linux localhost 2.6.32.9-g55626e1 #1 PREEMPT Sun Nov 7 23:24:32 CST 2010 armv7l GNU/Linux"
uname -a returns:
"Linux localhost 2.6.32.9-gace4441 #2 PREEMPT Mon Feb 7 18:23:06 CST 2011 armv7l GNU/Linux"
Sent from my Milestone X using XDA Premium App
Click to expand...
Click to collapse
If your brave, try changing the script to match your kernel. I bet it would work.
If you happen to have an SBF avail for your phone (I saw another thread in general where there is one for Alltell) I would think you could recover pretty easily if it fails.
Success! I didn't run into any problems after changing the check_kernel script.
Sent from my DROIDX using XDA Premium App
abcleanonme said:
Success! I didn't run into any problems after changing the check_kernel script.
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
You should send a note to cvpcs about that... maybe he can change the script to only look for generic froyo kernel.
Wait, now I can't get into clockwork recovery... it just hangs at the moto symbol. This is the one for Droid X (2nd init). It worked fine with the old one.
Sent from my DROIDX using XDA Premium App
Baseband question
abcleanonme said:
Since this is the Droid X, what will it take to get CM7 on it? Basically do the kernels match? And will the baseband be updated? I can test it as long as I don't get stuck with a Verizon baseband, as I've already had to take one back because of that.
The stock ROM shipped with mine, which is on the Cellular South network, has the following:
System Version: Version.3.2.6.MB809.ACG-CellSouth.en.US
Android version: 2.2.2
Kernel: [email protected] #2
Baseband: BP_C_02.06.00R
I attempted to install the CM7 nightly 3 and it simply aborts the installation with "assert failed: run_program("/tmp/check_kernel") == 0"
Let's get this working because i'm sure there are other Milestone X owners who would love to be running CM7!!!
Click to expand...
Click to collapse
I have the mexican version "Motoroi X". Will flashin cm7 update/change the baseband. Is there a workaround to have cm7 with the Iusacell (mexican carrier) baseband? I really want to have cm7 as my last phone was a HTC Desire with first and last custom rom CyanogenMod
abcleanonme said:
Wait, now I can't get into clockwork recovery... it just hangs at the moto symbol. This is the one for Droid X (2nd init). It worked fine with the old one.
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
You didn't say whether you used Droid X Bootstrap (or Droid 2)... but you aren't supposed to. It will brick your device (well, soft-brick) as it interrupts the 2nd-init process.
If you can successfully boot into CM, just long press the power button and select reboot ... you will then have an option to reboot into recovery.
If you did use bootstrap, you will likely need to SBF and start over.
Zaphod-Beeblebrox said:
You didn't say whether you used Droid X Bootstrap (or Droid 2)... but you aren't supposed to. It will brick your device (well, soft-brick) as it interrupts the 2nd-init process.
If you can successfully boot into CM, just long press the power button and select reboot ... you will then have an option to reboot into recovery.
If you did use bootstrap, you will likely need to SBF and start over.
Click to expand...
Click to collapse
No, I read to not use either of the bootstrap programs and didn't. After flashing cm7 I selected "Droid X (2nd init) in rom manager to install the newer clockwork recovery 4.x.x.x. it seemed to go okay, but when I selected reboot to recovery I encountered the hang up. Couldn't get it to boot into clockwork recovery for anything, so I sbf'ed back to stock, then updated to nightly 7 after rooting.
Sent from my MilestoneX using XDA Premium App
tavocabe said:
I have the mexican version "Motoroi X". Will flashin cm7 update/change the baseband. Is there a workaround to have cm7 with the Iusacell (mexican carrier) baseband? I really want to have cm7 as my last phone was a HTC Desire with first and last custom rom CyanogenMod
Click to expand...
Click to collapse
What are your kernel and baseband versions?
I wouldn't recommend doing anything without an sbf for your carrier or at least one with the same baseband, as you might end up in a pickle.
That said, as long as the kernel you have is the same, I guess you can change the check_kernel script like I did and cm7 should flash with no problems. Just depends on how brave you are or how much you're willing to risk as the locked bootloader makes everything tricky.
Sent from my MilestoneX using XDA Premium App
Zaphod-Beeblebrox said:
You didn't say whether you used Droid X Bootstrap (or Droid 2)... but you aren't supposed to. It will brick your device (well, soft-brick) as it interrupts the 2nd-init process.
If you can successfully boot into CM, just long press the power button and select reboot ... you will then have an option to reboot into recovery.
If you did use bootstrap, you will likely need to SBF and start over.
Click to expand...
Click to collapse
I know this warning against using DX/D2 Bootstrapper with CM7/Nightlies comes from a good place, but it's completely false for my phone. In reality, since flashing off of build0 to nightly1-9, I am unable to permanently flash CMR 4.0.0.4/5. In fact, if I flash it within CM Rom Manager, my phone will hang on reboot at the froyo M. However, I can do a battery pull, reboot into CM7, and then use DX2 Bootstrapper to install 2.5.008, and reboot directly into recovery just as we would before CM7 came out for DX. If I flash the orange recovery from within recovery (even after a complete wipe and new Monster install), Orange will load but not survive a reboot. What's more, the phone successfully boots into the Bootstrapped recovery with the typical CM7 power-button reboot prompt into recovery.
If I really want CMR 4.0.0.5, I just soft-flash it in 2.5.0.8, although for whatever reason, no DX ROMs (even CM7 nightlies) are built for the new update-script style (orange recovery).
FYI, I never first install Bootstrapper first before attempting to lock-in Orange CMR, I've just learned through hard experience (and much wear to my case shell and battery door/pull tab) that Bootstrapper -- at least for my phone -- is the most reliable Recovery option, even for CM7.
Ipso facto, I think cvpcs changed the 2nd-init.d behavior between build0 and the nightlies, or my inability to flash Orange CMR 4x, and my ability to use bootstrapper wouldn't exist!
rynosaur said:
I know this warning against using DX/D2 Bootstrapper with CM7/Nightlies comes from a good place, but it's completely false for my phone. In reality, since flashing off of build0 to nightly1-9, I am unable to permanently flash CMR 4.0.0.4/5. In fact, if I flash it within CM Rom Manager, my phone will hang on reboot at the froyo M. However, I can do a battery pull, reboot into CM7, and then use DX2 Bootstrapper to install 2.5.008, and reboot directly into recovery just as we would before CM7 came out for DX. If I flash the orange recovery from within recovery (even after a complete wipe and new Monster install), Orange will load but not survive a reboot. What's more, the phone successfully boots into the Bootstrapped recovery with the typical CM7 power-button reboot prompt into recovery.
If I really want CMR 4.0.0.5, I just soft-flash it in 2.5.0.8, although for whatever reason, no DX ROMs (even CM7 nightlies) are built for the new update-script style (orange recovery).
FYI, I never first install Bootstrapper first before attempting to lock-in Orange CMR, I've just learned through hard experience (and much wear to my case shell and battery door/pull tab) that Bootstrapper -- at least for my phone -- is the most reliable Recovery option, even for CM7.
Ipso facto, I think cvpcs changed the 2nd-init.d behavior between build0 and the nightlies, or my inability to flash Orange CMR 4x, and my ability to use bootstrapper wouldn't exist!
Click to expand...
Click to collapse
I think you may be confusing ClockWorkMod Recovery (CWM) and DroidX/2Bootstrapper.
CWM 2.5.08 (Green) is just an older version. CWM 4.X(Orange) is just a newer version of the same thing.
Bootstrapper is the APK that you use to tell the phone to reboot into recovery (CWM). Bootstrapper works by hijacking logwrapper.bin and hijacks the init process.
I haven't tried to actually run DX bootstrapper with Cm7, but given that they both need to muck around with init, then I expect them to break each other.
I had the same problem with the new CWM at first, but I did get it to stick after a try or two. Although, I don't think it really matters at this point. Both work just fine.
Zaphod-Beeblebrox said:
I think you may be confusing ClockWorkMod Recovery (CWM) and DroidX/2Bootstrapper.
CWM 2.5.08 (Green) is just an older version. CWM 4.X(Orange) is just a newer version of the same thing.
Bootstrapper is the APK that you use to tell the phone to reboot into recovery (CWM). Bootstrapper works by hijacking logwrapper.bin and hijacks the init process.
I haven't tried to actually run DX bootstrapper with Cm7, but given that they both need to muck around with init, then I expect them to break each other.
I had the same problem with the new CWM at first, but I did get it to stick after a try or two. Although, I don't think it really matters at this point. Both work just fine.
Click to expand...
Click to collapse
I'm glad the "correct" way works for you, but it's not working for me. And no, I'm not getting Bootstrapper/CWM Recovery confused. This is not my first rodeo, this is my third Android model, and I've had CWM Recovery or JesusFreake-Amon-RA mods since back in the day. Apparently, injecting extra steps into the first or second init.d is not an exclusive process . . .
rynosaur said:
I'm glad the "correct" way works for you, but it's not working for me. And no, I'm not getting Bootstrapper/CWM Recovery confused. This is not my first rodeo, this is my third Android model, and I've had CWM Recovery or JesusFreake-Amon-RA mods since back in the day. Apparently, injecting extra steps into the first or second init.d is not an exclusive process . . .
Click to expand...
Click to collapse
Bootstrapper is fairly unique to the DX/D2. Since we have no access to the bootloader, we can't just replace the factory recovery with CWM (which is what is done on most phones.)
Not really trying to 'call you out' or anything, I just didn't hear you mention the whole Bootstrap process. You mentioned using the CM7 Power off/reboot recovery sequence, but not actually using Bootstrapper to get into recovery. That's why I keep going back to this.
abcleanonme said:
Success! I didn't run into any problems after changing the check_kernel script.
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
you want to tell me step by step how you did it haha,
I tried to change the script but the installation keeps aborting for some reason or it just hangs on the "installing" screen, help would be greatly appreciated!
SirPots said:
you want to tell me step by step how you did it haha,
I tried to change the script but the installation keeps aborting for some reason or it just hangs on the "installing" screen, help would be greatly appreciated!
Click to expand...
Click to collapse
Sure thing, I'll break it down when I get off work tonight
Sent from my MilestoneX using XDA Premium App
Related
I apologize in advanced to the moderators of the Droid X forum.
The Droid X forum is by far more difficult to follow than the Incredible forums. Why is it so hard to root this device? Because there are different downloads, instructions, procedures everywhere you turn for the Droid X. Is this device really that difficult for all parties to come together on a way to do what one can do with the Incredible?
My goal was to get to CM7 as I was with my Incredible. I really liked that ROM and what it did for the device.
Now, correct me if I am mislead but I though if I could get CM7 on my X it would work similar to the Incredible and I could have a similar operating environment with the bigger screen and such.
I chose to use the CM7 Wiki to root my X. I had no success (more on that shortly). Then, I tried Z4Root. I am running 2.2.1 and my radio ends in .07. This is after the SBF procedure. The phone boots and is usable. Here's what I've done:
First I Used RSD Lite to SBF from the factory installed ROM. It sent me back to Android version 2.2.1. The radio was set back to .07P.
Next I attempted to follow these instructions from the CyanogenMod Wiki:
Unzip rageinthecage-arm5 & the Superuser package to the same folder as adb (the /platform-tools folder within the Android SDK folder).
Connect the Motorola Droid X to the computer via USB.
On the computer, open terminal and run the following commands:
adb push rageagainstthecage-arm5.bin /data/local/tmp
adb shell
chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
/data/local/tmp/rageagainstthecage-arm5.bin
Once the exploit finishes, in terminal, run the following commands:
exit
adb kill-server
adb start-server
adb shell
NOTE: You should see a "#". If you see a "$", then the exploit didn't work, please repeat steps 4 & 5.
***
This is where I am stuck!
Every time I get to here the device is not recognized by the ADB DEVICES command.
So, I try the Z4Root. It runs. Reboots. Then I am back to the same state as I was before.
I try the procedure on the CyanogenMod Wiki page. Again I get stuck after I try to push the rageagainstthecage program.
I would like some help. If anyone knows where to point me it would be great. I am seeing different procedures on RootzWiki, CyanogenMod Wiki, and other various Droid forums.
I have been loyal to XDA throughout my work with my Incredible. I am not in a hurry to go elsewhere.
That being said,any help would be greatly appreciated.
Frustrated...
Here's what you need to do:
1. SBF to 2.2.1 (.340)
2. Root with Z4root and install Droid 2 bootatrapper.
3. Boot into ClockworkMod Recovery and install the CyanogenMod 7 zip file.
4. Flash Google Apps
5. (optional) install Razor's all-in-one fixes for Cm7 (highly recommended)
Now you can begin installing Nightlies! For every nightly you install you must perform steps 4 and 5.
Everything you need can be found here: http://www.rootzwiki.com/showthread.php?389-ROM-BETA-CyanogenMod-7-for-the-Droid-X
Sent from my DROIDX using XDA App
Update: Phone rebooting randomly
Thanks for the info infazzdar.
The file I used for SBF is 'C:\Program Files\Motorola\RSD Lite\VRZ_MB810_2.3.34_1FF_01.sbf'.
I tried what I stated above and now my device reboots randomly. The longest it has lasted thus far is about fifteen minutes.
Do I need to SBF again?
Side note:
I downloaded the MD5Checker from cnet. I can't (no matter how many times I download and unzip packages get any MD5 values to match).
Side note2:
I am done with Chrome. It hangs more than any browser in the history of browsers. Going back to Firefox, watching Bad News Bears (1976) to relax, going to bed, and trying again tomorrow.
Frustrated...
Definitely try a different browser and download the file from another mirror.
Be sure that the MD5sum matches up. Also, you might want to use Linux to SBF and check the MD5sum, it's loads easier.
Sent from my DROIDX using XDA App
What they said above:
SBF to .340
z4root, should come with an install of superuser as well. If not, then get from Market after rooted. Also, when running z4root, make sure USB Debugging is on (the newer versions should give you a prompt if its not, but I don't know which version you are using)
Droid X Bootstrap Recovery (The poster above put Droid 2, I've heard both work, but I'd go with the X version just to be safe)
Move cm7 zip file to root of sd card.
Open Bootstrap Recovery, top button FIRST (always forget this step after an SBF) then reboot recovery.
I can't remember from when I installed cm7 last, but you'll probably need to do a wipe/reset from within Bootstrap and then install cm7.
The best sbf experance I've had was with using linux, the customized linux flashing tool I find the best,
Here a link, hope this helps, androidforums.com/droid-x-all-things-root/346016-creating-bootable-linux-cd-soley-sbf-headache-free.html
DROID X running liberty GB V.8
Got it!
Thanks guys.
After SBF about seven times I finally got the sequence down. I read the blog on init2 as well. That helped me understand why the X is so much more difficult to work with than the HTC Incredible.
What worked for me was to follow "[OFFICIAL METHOD][HOW TO] Prepare Your Phone for CM4DX!" on RootzWiki.
<Make sure USB debugging and Unknown Sources is selected when you begin and after every time you wipe. >
Here are my notes to supplement the instructions on RootzWiki:
SBF (follow instructions)
Z4Root (install apk through command prompt)
Get zips for CM7 and Gapps and copy to root of SD card.
Bootstrap (install apk through command prompt)
Once in recovery check that zips are available before wiping again.
Install zips from SD card in recovery
All these are detailed in the thread referenced above.
I hope what I have experienced can help others who are new to the X.
I have since had some random reboots and force closes. I am now going for the Razor's all-in-one fixes for Cm7. Hopefully that works.
Okay. Kinda stuck again
I have successfully rooted. I have made Nandroid backups. I decided to go t o the Nightly release 42. The device seems to like to just power down or randomly reboot.
I am thinking I should SBF again with the Linux method. I have downloaded the image and burned it. Ready to go.
I am thinking there is something messed up in the init that is installed by Motorola or something of the sort. I am hearing folks have better luck with the Linux SBF.
Thoughts?
I've been on CM7 since a couple of days after RC0 was released.
I used basically the same process you mentioned above and I've not had any reboot/freeze up issues.
I've flashed many of the nightlies with only doing a Dalvik Wipe, and my phone has been near flawless. FYI, I'm currently using RevNumbers nightly builds since he includes the 'all-in-one' fixes. (www.revnumbers.info)
Going to try Liberty this morning.
Zaphod-Beeblebrox said:
I've been on CM7 since a couple of days after RC0 was released.
I used basically the same process you mentioned above and I've not had any reboot/freeze up issues.
I've flashed many of the nightlies with only doing a Dalvik Wipe, and my phone has been near flawless. FYI, I'm currently using RevNumbers nightly builds since he includes the 'all-in-one' fixes. (www.revnumbers.info)
Click to expand...
Click to collapse
Interesting. I wonder where I am going wrong. I even used the Linux method to SBF, then Z4root, then the bootstrapper application, boot into recovery, clear data and cache, then install CM7 Nightly 42 and Gapps. Same issues.
I had no success with the zip I had with Liberty. I think I had a corrupt download.
I SBF'd using the Linux method. I still had random reboots, freezes, and shutdowns on the downgraded ROM. I let it update with the OTA from Verizon. I am now on the stock Gingerbread and I have had only one reboot in three days.
I wonder if the latest iterations of the X have some code which works only with the latest OTA ROM release from Verizon. Maybe something in the kernel?
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.
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
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..
I installed BandroidX on my Bravo (running Cyanogenmod 7.2), hit the bootstrap button, and then hit reboot recovery. The phone shows the red M and then the following error: "Err:a5,70,39,00,21." Can anyone help?
Parcae said:
I installed BandroidX on my Bravo (running Cyanogenmod 7.2), hit the bootstrap button, and then hit reboot recovery. The phone shows the red M and then the following error: "Err:a5,70,39,00,21." Can anyone help?
Click to expand...
Click to collapse
BandroidX Recovery is INCOMPATIBLE with CYANOGENMOD.
You're gonna have to flash the sbf, root, enable non market apps, and install DEFY 2ND-INIT RECOVERY.
As far as I know, BandroidX is only compatible with Stock and BravoX Roms.
brandoix procedure should eliminate as many people make mistakes and also is obsolete
help with bravo
having problems with my bravo on the screen it has have CyanogenMod 7.2.0 using BandroidX recovery
bootloader
09.12
battery ok
ok to program
transfer mode:
usb
harv65 said:
having problems with my bravo on the screen it has have CyanogenMod 7.2.0 using BandroidX recovery
bootloader
09.12
battery ok
ok to program
transfer mode:
usb
Click to expand...
Click to collapse
Do not use BandroidX recovery for any rom except for BravoX (BravoX is a lightweight, deodexed stock rom). Use Defy 2nd-init -- Defy 2nd-init -- Defy 2nd-init.
Anyways, that's the screen to flash an sbf -- if its going there directly when you power up your phone and you're not pressing anything then your Bravo is in a semibrick state -- meaning the only fix is to flash the sbf and start over.
You just need to flash the sbf and install a proper recovery solution.
You only need to install Defy 2nd-init once (per sbf flash). Also, all custom roms on the Bravo come with Defy 2nd-init already installed so DO NOT INSTALL A CUSTOM RECOVERY ONCE YOU'RE RUNNING A CUSTOM ROM. Its pointless*.
*Unless you're testing some version of Touch recovery -- only recommended for advanced users.
Follow the directions in these two links and you'll be back in action in no time
Link to sbf thread
Link to Defy 2nd-init thread
Once you get the hang of it you'll be able to go from sbf to custom rom in under 10 minutes and lol at yourself for being stuck with a simple problem. On my first week of having a Bravo I was stuck on boot at the red M. Couldn't figure out what was wrong. Tried everything I knew and ended up low battery bricking myself. Managed to get a charge and accessed the screen with an ! in the triangle and an andriod -- didn't know what to do on that screen -- got lucky and happened to hit both volume buttons and access stock recovery (took me 3 days to figure out how to access stock recovery btw), did a factory reset there and my Bravo was fully working again. Problem was I didn't factory reset before flashing CM7 when coming from stock...Also, Bravo's 3g was my only internet at the time.
Wow, after looking back I just realized how much I've learned in my 1.5 years with a Bravo. Gotta love XDA for all the knowledge you can obtain here.
/the Bolded crap isn't necessarily directed at you, just bolding it so it sticks out and hopefully helps someone else out -- I've answered questions similar to this and the solution is always "Don't use BandroidX Recovery"
//Defy 2nd-init
skeevy420 said:
Do not use BandroidX recovery for any rom except for BravoX (BravoX is a lightweight, deodexed stock rom). Use Defy 2nd-init -- Defy 2nd-init -- Defy 2nd-init.
Anyways, that's the screen to flash an sbf -- if its going there directly when you power up your phone and you're not pressing anything then your Bravo is in a semibrick state -- meaning the only fix is to flash the sbf and start over.
You just need to flash the sbf and install a proper recovery solution.
You only need to install Defy 2nd-init once (per sbf flash). Also, all custom roms on the Bravo come with Defy 2nd-init already installed so DO NOT INSTALL A CUSTOM RECOVERY ONCE YOU'RE RUNNING A CUSTOM ROM. Its pointless*.
*Unless you're testing some version of Touch recovery -- only recommended for advanced users.
Follow the directions in these two links and you'll be back in action in no time
Link to sbf thread
Link to Defy 2nd-init thread
Once you get the hang of it you'll be able to go from sbf to custom rom in under 10 minutes and lol at yourself for being stuck with a simple problem. On my first week of having a Bravo I was stuck on boot at the red M. Couldn't figure out what was wrong. Tried everything I knew and ended up low battery bricking myself. Managed to get a charge and accessed the screen with an ! in the triangle and an andriod -- didn't know what to do on that screen -- got lucky and happened to hit both volume buttons and access stock recovery (took me 3 days to figure out how to access stock recovery btw), did a factory reset there and my Bravo was fully working again. Problem was I didn't factory reset before flashing CM7 when coming from stock...Also, Bravo's 3g was my only internet at the time.
Wow, after looking back I just realized how much I've learned in my 1.5 years with a Bravo. Gotta love XDA for all the knowledge you can obtain here.
/the Bolded crap isn't necessarily directed at you, just bolding it so it sticks out and hopefully helps someone else out -- I've answered questions similar to this and the solution is always "Don't use BandroidX Recovery"
//Defy 2nd-init
Click to expand...
Click to collapse
thanks for the help
brandoix works
harv65 said:
thanks for the help
Click to expand...
Click to collapse
I used 2initD firts ti me with stock ATT and then install brandoix Bravo recovery . Worcks great installing MIUI V4 (android update 4.0.3 and its fast!!!