Failed camera buttons have long since been a blight upon Droid X modders, disallowing the use of ClockworkMod Recovery for any activity that involves selecting something, which completely rules out the usefulness of said recovery. Now that all has changed.
The newest version Clockwork Recovery, v5.0.2.0, allows users to make selections with the power button instead of using the camera button; however, for some people, getting there can been a little tricky. Hopefully this guide will help someone.
1. (Stock Based Roms Only) Install Droid 2 Bootstrapper. Select 'Bootstrap Recovery'. Upon completion, select 'Reboot Recovery'. If the phone boots into recovery then pull your battery and continue to the next step. (This step is only necessary if you don't already have recovery installed)
2. Install ROM Manager from the market. Anyone who already has ROM Manager, make sure that it is up-to-date.
3. Open ROM Manager and tap 'Choose your device'. When the device selection screen appears select 'Droid X'.
NOTE: 2nd-init users select 'Droid X (2nd-init)'
4. When you get the message that ClockworkMod Recovery downloaded and installed correctly, select 'Reboot into Recovery' from within the ROM Manager application. It should then reboot you into the updated, blue, recovery.
5. Once you've rebooted in ClockworkMod Recovery v5.0.2.0 press the volume down button many times until it says 'Back Button Enabled'. At this point you will be able to use the volume buttons to navigate and the power button to make selections.
If this doesn't work for you, reply and list the step that you're stuck on.
Sent from my Transformer TF101 using Tapatalk
How can you tell if you are on 2nd-inti?
Sent from my HTC ThunderBolt using XDA Premium App
Roms such as CyanogenMod and MIUI are 2nd-init roms. Other roms, such as Liberty and Vortex, are stock based roms.
Sent from my Transformer TF101 using Tapatalk
Related
Im not getting any of the DX flashing and everything.
Currently I'm Rooted on the Official OTA 2.2 Froyo.
I removed some bloatware & im stilling Running that official Froyo.
I want to beable to flash a ROM like FlyX or something out there.
But my question is if I'm rooted but I'm the OTA version do i just use the Bootstrap App & ROM Manager to get to another ROM. Or Am i Missing something?
I looked at guides & tutorials but there all broken or jus dont collaberate to make sense To My Situation... Any Help Pleasee?
Find the rom you want to try and there should be instructions in that thread. You usually have to get to clockworkmod recovery by bootstrap recovery then reboot recovery, do some wipes,mount, and install zip from sdcard. Just make sure you follow the instructions or you can brick your Dx
Ok- I was also VERY confused by some of the Android terminology and specifically the DX terminology.
Like SysA said- each custom rom may not have the exact instructions for loading. Some files are built in such a way as to eliminate the need to "mount system" or "clear cache". That is why every thread I have seen has their own separate instructions.
Download the file from the link that is provided in the thread (I am hearing a lot of good things about the ApeX rom and AOSP rom). From your phone or computer (but obviously the file has to be on the sdcard (I always put it on the root of the sdcard)
I know for me the whole "Clockwork Mod" and "bootstrapper" thing was very confusing. So I will try and explain it (forgive me if you all ready got it figured out). There is an app in the market called "Droid X Bootstrapper". You need that. You don't have to have "Rom Manager". I have used it to download some things but I never use it for installation. I do all my installation from "Droid X Bootstrapper". So- get "Droid X Bootstrapper", get the rom you want to install. Open Droid X Bootstrapper, hit "Bootstrap Recovery" (you should get a 'Success' notification). Hit "Reboot Recovery". Your phone will reboot into recovery mode (duh). Don't start installing anything.
Before you do your installation make sure to make a backup of what you currently have in case something goes haywire. The volume rocker key is for up/down. The camera button is for enter. the back button is for back. I believe the back up is something simple like... Backup/Restore (enter). Backup (enter). I would go ahead and reboot before I continued with the installation- I am just crazy like that.
Then just start the process over, except you are already backed up so just follow the instructions from the Rom Developer.
It process will go something like this...
1. Open Droid X Bootstrapper.
2. Hit Bootstrap recovery (get success notice).
3. Hit Reboot Recovery.
4 The phone reboots into recovery.
5.Navigate to mounts and storage.
6. FORMAT system.
7.Format/wipe data.
8. Format/wipe cache.
9. mount /system <<<-- THIS IS A CRUCIAL STEP, (in roms that include this instruction) please don't miss it or you will have to SBF.
a. hint- the screen will say "Mount Sytem" already. You want to move the cursor down to that option and hit enter (the camera key) and it will now read, "Unmount System"
10. Return to previous menu (with the back button)
11. Install .zip from sd card
12. Choose ApeX
13. Install!
This is just an example. Not all installations are exactly like this. Some do not require the scary "Mount System" instructions. Hope that helps a little.
So i bricked my phone trying to deodex with 928 method as shown in the below steps.
B. DEODEXING:
1. Now that your phone is rooted, you can now download and install clockworkmod’s “Droid X Recovery Bootstrap” app in the app market. Do not use this program after installing just yet! There are a few more steps!
2. Download but DO NOT UNZIP 928’s BlackGlass Theme here: 928Droid Themes for the Droid X This program will automatically Deodex your Droid X and install the custom BlackGlass Theme. There is another option to manually deodex your phone but that’s a far more complicated option compared to this alternative.
3. Place your DROID X into “USB Mass Storage” mode (originally it was PC MODE but now we need to switch to USB Mass storage in order to access the SD Card storage).
4. Drag and drop the zipped 928 BlackGlass onto your sdcard. You can make a separate folder for this on your SD Card labeled “custom themes/roms” and place the file there. You will later access this file through Bootstrap Recovery in order to install the custom ROM/Theme (or any other ROM or theme hereinafter).
5. Open the Bootstrap app in your app drawer and press “Bootstrap Recovery”. Click “Allow” if the Superuser Permissions window pops up. Make sure to do this step before rebooting. Some users have been having issues with the phone not rebooting into recovery and it's usually because they skipped this step
6. Press “Reboot Recovery” and your phone will reboot into recovery mode.
7. Allow the recovery mod to boot (it will take less than a minute after the Motorola logo pops up). You should see a series of options in green font.
8. Use volume up/volume down buttons on the phone to control scrolling and use the red camera button to select a particular option. Use the phone’s back function (second button from right on front of phone) to move back to previous screen options. Scroll down to “Backup and restore” and backup your current stock froyo. This process takes a very long time so be patient with it. I recommend that you Backup the first time you try modifying your phone in any way because if you brick, you're going to lose everything! I’m personally skipping this step because I’ve done it before and the backup process takes a very long time.
9. Select “install zip from sdcard”
10. Select “choose zip from sdcard” and find “928DroidBlackGlassX-DroidX-OTA2315-DeOdexEERR-THEME.ZIP”
11. Confirm the install by scrolling down to “Yes-Install 928DroidBlackGlassX-DroidX-OTA2315-DeOdexEERR-THEME.ZIP”
12. If you’re watching the install process you will see various commands running such as “removing odex files” etc. etc.
13. Go back to the main screen and select “reboot system now” and wait for the phone to reboot. That’s it! Your Droid X is now fully deodexed and you have 928’s BlackGlass Theme installed!
14. You can go download “ROM Manager” from the app market and go download more custom ROMs or themes but make sure to only dl and install DEODEXED ROMs!!! If you install a ROM that is not compatible with a deodexed phone your Droid X will brick!
15. If you want to download and install different ROMs and Themes you can do this by following steps 2 through 11.
I was running 2.2.1 root. RSDLite keeps erroring out while trying to SBF
What error are you getting with rsd lite?
Sent from my DROIDX using XDA App
I was getting a error about downloading ram from the bootloader or something of the sort. I Finally got it to go through, then i tried the manual deodex method and it errored out on the SyncML.odex file. THen i realized there wasnt root anymore, or bootstrapper. I guess the SBF wipes that stuff out? So i re rooted, got recovery reinstalled. And im restoring my backup i did. I figure after the backup is up and running ill try the manual deodex again.
when i enter the recovery mode
i got into Android system recovery (2e)
then i choose apply sdcard:update.zip
then it forward me to ClockworkMod Recovery v2.5..
then i choose apply sdcard:update.zip again..
then it rebooted and back to system recovery (2e) again
what should i do to fix this ? i want to update my ROM
If your custom ROM can be flashed via cwm, go save it in your internal sd then use the install zip in sd card option in cwm.
I suggest you do a full nandroid back-up first just to be on the safe side...
thanks for reply..
i think i can't use cwm anymore to flash.. since it keeps looping between this two recovery mode.. i just flash it using odin, now i'm runnning original firmware 2.1
but i still see those two recovery mode.. how to remove one of them ?
When you get into Clockwork, don't press the "apply update.zip".
Select "install zip from sdcard" and locate your roms .zip and install it.
Read the instructions again and again until you understand it. It's obvious that you have no idea what you are doing.
Sent from my GT-I9000 using XDA App
If I understand your post correctly, you are having trouble getting into CWM after installing it. I had the same thing on my phone.
When going into recovery, you hold down the power button, the home button and the volume up button and release the home button when the Samsung screen appears. I tried releasing the power button when the Samsung screen appears and it goes into CWM recovery.
Ian
Hi, I have this ROM http://www.youtube.com/watch?v=wQvrEH74dgI, my question is how to install the google apps (2nd link). Thanks.
Boot into recovery (power on holding the Power and Volume Down button) and in the recovery screen, select "install zip from sd".
Select internal or external storage/sd and browse to the file, select it with the power button. It'll do its thing and after, I would clean the dalvik cache and reboot.
I assume you've got a custom recovery already installed, since you've got the custom rom already installed.
I did this
Before proceeding, please keep in mind that your handset will be wiped clean of all data so make a backup of your data. Also, the steps below require your handset to be rooted with a custom recovery installed. If your handset is not rooted, I’d recommend you not to flash this ROM since its not meant for amateurs.
Step 1: Download CM9 Alpha 4 for Epic 4G from here or here. Also download the supplementary Google Apps package from here.
Step 2: Boot into CWM Recovery, and select the ‘Wipe data/Factory Reset’ option. Then navigate to Mounts and Storage and select the ‘format /system’ option.
Step 3: After you have formatted all the partitions on your Epic 4G, select the ‘install zip from SD card’ option, and then select the CM9 Alpha 4 zip file. Once the CM9 file has been flashed, again select the ‘install zip from SD card’ option, and this time select the Google Apps zip file package.
When the flashing process is complete, simply reboot your phone and wait for it to boot into CM9. Keep in mind that the first boot might take sometime, so please be patient.
Do NOT restore your app data backup. Doing so can lead to instabilities, and other issues. Also, please don't complain about feature X or Y not working. The ROM is in Alpha for a particular reason.
Click to expand...
Click to collapse
But my phone is still stucked at its starting window for more than 20 minutes :?
My phone got stucked ! It stucks at the staring window, and doesnt want to load
define "starting window"
Like this, but instead of all the things it says, mine says just "Unlocked" in the upper left corner. I have tryed this http://www.youtube.com/watch?v=wQvrEH74dgI (rom + gapps), and this guide http://forum.xda-developers.com/showthread.php?t=1302423 + this for the apps http://knowmydroid.com/blog/install-android-4-ice-cream-sandwich-cm9-on-samsung-epic-4g.
Hi all,
I have a Nexus 7, rooted, running stock 4.1.1 rom, and just installed TWRP 2.1.1
I have been reading this thread, http://forum.xda-developers.com/showthread.php?t=1779092 , however I cannot post on the thread due to being a new/low post count member.
I read that, and it does happen, that each time I reboot, the stock recovery reinstalls itself.
I attempted to follow this....
NOTE: The stock ROM may automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced -> File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Click to expand...
Click to collapse
but it doesn't seem to work.
Firstly, when I go to the "Mount" menu, there is only 3 entries.....1 large button which says "Mount USB Storage", and 2 boxes which are selected with a cross in the box, "Unmount Data", and "Unmount Cache". If I do press Mount USB Storage I can only Unmount it to return to menu.
So regardless of that part, if I then go to the file manager, and browse to the system folder, the folder shows up empty, and the only thing showing is a Bin subfolder (also empty)
any ideas whats wrong?
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
TheBiles said:
Use the one-click root tool. Install TWRP via GooManager. Profit.
Sent from my Nexus 7
Click to expand...
Click to collapse
hi,
yeah I did use the tool, all is rooted fine. If you install TWRP from GooManager, and then press to reset to recovery, TWRP loads fine. Once you reboot again however, the stock roms overwriting the TWRP so it no longer works each time. The steps there were supposedly to stop this from happening, from within TWRP, however the options aren't even there. Sadly, I can't post in the TWRP thread due to having less than 10 posts
How r u booting into recovery? Do u power off then use button combo? I use quickboot from market. Its free and boots u into recovery without having to manually turn off the device. I had the same exact issue u drescribe when attempting to follow op instructions. I couldn't do it so I said what the hell, let me see if I boot into recovery using quickboot it overwrites. I was happy to discover that it didn't.
Sent from my EVO using Tapatalk 2
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Midnight Tboy said:
Hi.
I booted into recovery directly from the GooManager option which restarts it into it for me. After a reboot though choosing the same option gives the official recovery I presume (android robot with chest open and exclamation mark)....until I tell it to install the OpenRecoveryScript again
I'm not familiar with Quickboot - take it its just a button to press to get it into recovery the same way as the GooManager option of "Reboot Recovery"?
I'm looking at this TeamEOS nightly build at the moment, toying with the idea of whether to stick with stock rom or flash their custom rom over it.....hard call as its still early days for the roms I think, but if spend ages again installing my apps, will have to do it again afresh when do eventually change the rom
Click to expand...
Click to collapse
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
pathtologos said:
Yes quickboot is as u describe. I know what u mean about starting to flash. It's a bit early for me considering conditions of the roms ( early stages). I am getting tempted tho...lol. won't be long I'm sure.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
yup....just installed Quick Boot (Reboot),
chose Recovery, and again its rebooting back to the original recovery instead of the TWRP.
Guess I'll have to flash to a custom rom to get around it if want it sorting now....or wait till I have the minimum post count to post on the main TWRP thread
Not end of the world to reinstall apps and games I guess when the custom roms are more mature, so long as I remember to use Titanium Backup to save my games progress
you need to rename the recovery-restore.sh file in /system/etc/ (I forget the name offhand - if you look at the filenames there you'll figure it out). It restores the stock recovery at every reboot unless deleted or renamed. Then flash your 3rd party recovery.
Hi,
thats the trouble.....I use the file manager in TWRP, and I can't see that file anywhere.
The TWRP page says to go to /system......but when I go there its empty, only one subfolder, /system/bin, which also shows up empty