Hi. I looked throughout this cunk of the forum and couldn't find anything on the mater, so figured I'd ask.
I cannot get Recovery to work on my X2. Just got it yesterday (Love it so far, but I'd love to put the Atrix 4G on my phone.) I tried the boostrap method using the System Recovery app, and tried Clockwork Recovery. Reboot Into Recovery with System simply rebooted my phone, and the same with CWR. Manually pushing my phone into Recovery (power button and volume down at boot to select the option) Gives me an error. Any ideas?
Yes, I made sure my phone was rooted. lol
With the bootstrap you did hit install recovery first and then plugged into the wall Before hitting recovery mode, right?
Sent from my DROID X2 using Tapatalk
...Damnit, nope. It was plugged into my computer the entire time. I had it set to Charge Only, though.
Posted in wrong section...your issue seems to be resolved tho.
Related
I have tried everything. Holding volume up and power, down and power, both and power
Holding the whole time, letting go at the vibrant screen
I even did i factory reset and it wont work
Does anyone else have this issue?
It is going to ultimately force me to get a replacment device
I was wondering if there was somehing i missed
Sent from my SGH-T959 using XDA App
hold both volumes and power until you see the contact screen for the second time.
Sent from my SGH-T959 using XDA App
Same problem here. Spent a day trying to get it to work. Finally gave up and used the one click root method to get into recovery. This is my second Vibrant, so it's not that I haven't done this correctly before. Very strange, but one click worked for me.
Sent from my SGH-T959 using XDA App
The one click doesn't do anything
It puts the update.zip on my internal storage then doesn't reboot or anything
Would it still work through adb?
Sent from my SGH-T959 using XDA App
I've spent several hours trying to get into recovery and download mode via the buttons. I've tried everything I've found on the forums, and pretty much concluded that the US Vibrant is seeing the same issue that Bell Canada and Aus Optus is with some phones not having the power button reboot functional for whatever reason. I'm going to return mine tomorrow for one that works. Hopefully I don't get any static about trying them out till I find one that works properly.
ADB works fine for me to reboot to recovery and download. I personally would use TGA_Gunman's root.
Hey guys. I just bought a Vibrant today and am having this same issue. No matter how many times I hold either volume button independently (or even together), I can't get into Fastboot, or I guess Download mode as it's called here. I'm coming from a Nexus One where it works everytime, so this is kind of weird. Launching RomManager and selecting to boot into recovery does work, but I don't want to rely on that.
Is the smart thing to go swap the physical phone?
I am having the same problem with my Vibrant. Anyone figure out how to get it into recovery?
kas21 said:
I am having the same problem with my Vibrant. Anyone figure out how to get it into recovery?
Click to expand...
Click to collapse
As unpleasant as it may seem to do so, it really behooves you who are having those issues, (as am I with my 3rd replacement!!!) Vibrant, it is absolutely worth your while to set up ADB, for numerous reasons. It solves both of those issues and allows so many other options. Once you do the installation of the SDK on your PC and install the right drivers, it is not at all difficult to use it to do many important things much easier.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
just download quick boot from the app store and u can reboot, recovery, or bootloader ur phone with this app
rdunn20 said:
just download quick boot from the app store and u can reboot, recovery, or bootloader ur phone with this app
Click to expand...
Click to collapse
he means boot rom and hes right just download it from app store and click install clockrecovery and after that click reboot in recovery and your done.
The problem with relying on adb, Quick Boot, and Rom Manager is what are you going to do when you flash and your phone won't boot? You won't be able to get into download or recovery mode and you'll be hosed. Take the phone back while you can and get one that works.
Exactly. I'm curious if there's a way around this though. What is it
that actually causes the phone to boot into recovery with the hardware keys and is it something that can be fixed/flashed?
I already exchanged once within the thirty days and I don't think the 30 days gets reset. Think I'm past the return period now.
Sent from my SGH-T959 using XDA App
shootr said:
The problem with relying on adb, Quick Boot, and Rom Manager is what are you going to do when you flash and your phone won't boot? You won't be able to get into download or recovery mode and you'll be hosed. Take the phone back while you can and get one that works.
Click to expand...
Click to collapse
I'm so glad you wrote that. This is exactly my feeling. In ideal solutions, ADB or even installing a terminal emulator onto the phone is great. But for any dev who dabbles with modifying their phone in any way, having access to recovery directly from the phone is an absolute must.
Im having the same problem but let me ask could it be because Avatar is in the sd card?...I keep reading (NOW) that the Root zip files should be copy to a SD without Avatar....
Gusgom said:
Im having the same problem but let me ask could it be because Avatar is in the sd card?...I keep reading (NOW) that the Root zip files should be copy to a SD without Avatar....
Click to expand...
Click to collapse
There are two "SD" cards, an internal and external. The external one is the on that the user can swap. It also contains the Avatar movie (if it is the one that came with the phone).
The update.zip file should be copied to the internal SD card. The one WITHOUT the Avatar movie.
I also cannot get my phone to boot into recovery using the buttons. I rooted using one-click.
It seems to be an issue with new/replacement Vibrants. I have a thread about it here: http://forum.xda-developers.com/showthread.php?t=764360
If anyone has a device like this and can pull a dump file from it and upload it, that would be fantastic! I'm not sure if this is a physical limiter or a software based one, but I'm pretty sure it's software based on experience and manufacture dates. Once we get a dump, I'm sure someone will be able to figure it out.
And to back what the others said, I was able to adb download no problem, but when the Odin flash hung, there was no way to get back in to download mode and I ended up having to exchange the phone. As soon as my next one gets here, I'll test and post a dump if someone else hasn't already.
johnny12times said:
And to back what the others said, I was able to adb download no problem, but when the Odin flash hung, there was no way to get back in to download mode and I ended up having to exchange the phone.
Click to expand...
Click to collapse
I had the same issue on a replacement Vibrant and this works for me to get into download mode (even after Odin hung and it looked 100% dead):
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
dex1701 said:
I had the same issue on a replacement Vibrant and this works for me to get into download mode (even after Odin hung and it looked 100% dead):
1. Removed SD and SIM card
2. Removed battery
3. plugged the phone into USB
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
Excellent directions. Worked like a charm.
OMG! I seriously thought my Vibrant was trashed! Excellent directions for getting your Vibrant out of Boot loop and into Download mode:
1. pull everything out of phone (battery, SIM, SD card)
2. Plug in USB cable
3. Hold down both volume buttons
4. Insert battery while holding down volume buttons.
My phone went into Download mode easily at this point.
In my case, my phone got stuck in Boot loop while trying to use ROM Manager for a new ROM. Guess I used it wrong, I'll just stick with installing ROM's by way of Recovery mode. Anyway, my phone stayed in Download mode until I flashed it with ODIN. I just flashed it back to stock and started over. Here's the link:
http://forum.xda-developers.com/showthread.php?t=734475
I'm so glad I didn't have to exchange my phone, I feel bad for those that had to exchange thier phones, this is a nice workaround.
i try it went into downloading screen. Odin did not see my phone. What can i do now? Can anyone help.
Recently i flashed the CM9 rom onto my Droid X2. Followed the instructions and everything installed correctly. Since it has been a couple of days and I have installed all my programs and got everything where i wanted it, i wanted to make a backup.
Soon i discovered that I didnt have System Recovery installed. SO i began looking into my SD card and i have two files,MOTODX2_Bootstrap_signed.apk. So i decided to install it, everything went fine but now my phone is stuck in a boot loop. It wont even boot into CM9.
Is there another BSR that i should be flashing instead of this one. Maybe the ReRecovery one? i know theres a [patched] BSR to install but i gave me the same problems.
Thanks EHB
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
Here's the link to the patched CM7 Recovery. Pulled straight from the CM7 thread
http://www.mediafire.com/?pzz4413k6wggcao
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Thanks for the information.
I knew basically everything you said except for the "wipe cache partition". Why is this necessary? I know that it doesn't delete personal information but what does it wipe/delete?
Im going wait to do this tomorrow - my day off. Im just worried that its going do the same thing and ill have to reflash and start all over again.
Thanks again EHB
Wiping the cache partition clears any/all application data and common app components. It does not wipe apps themselves, rather the files that the app generates when used.
Wiping it is necessary because when core system components are changed, the resources used by the apps also (could) change. Having stale app data after a system change or tweak can cause problems, which is why it is best to clear it. It gets rebuilt as apps are used.
RoyJ said:
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
Click to expand...
Click to collapse
I'm afraid I'm in the same boat and am going through these steps to hopefully get back on the right track. When you say the battery charging icon can take several minutes... are you suggesting 3-5 minutes, or up to 30 minutes? Because... I'm at about 35 minutes right now and am getting pretty nervous.
just skip to this part, if you can
remove charger and battery
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
Click to expand...
Click to collapse
Patched BSR, please help!!
RoyJ said:
Hi, for Cyanogenmod9 use the CM7 PATCHED BSR. It works just fine for me everyday. I'm kind of addicted to flashing ROMs for some reason and usually am on different ones multiple times a day. Always in BSR either restoring or backing up. The patched BSR for CM7 works just fine for me. For reference, in the app drawer it should say "CM7 System Recovery" not just System Recovery.
I'm not sure if it has been looked into by dev's yet or not, but the day CM9 was released I actually did flash the CM7 ReRecovery zip and I was able to boot to BSR from a powered off state just by plugging in. I wasn't sure if it was okay to use, so I installed a fresh CM9 without it. I don't know if this is 100% safe or if there would be any issues from using the ReRecovery zip. I would recommend just installing the patched CM7 apk and trying to use that.
***^That BSR is an application. You download, install and run it on your phone. The ReRecovery is a flashable zip you can install once already inside of BSR allowing you to get into custom recovery say for example, if you're boot looping. ***
================================================
If you're still having bootloop issues, try this;
-Grab your ECOMOTO charger, plug into A/C power, pull battery, replace & plug into wall.
- Wait for the Motorola logo to disappear and the battery charging icon to appear (this can take several minutes)
-When you see the battery charging icon, unplug your phone and pull your battery.
-Reinstall the battery and hold the VOLUME DOWN key while powering on the device. Release the VOLUME DOWN button when it turns on.
You should now see "FASTBOOT" in white text above the Motorola logo.
-Press the volume down key several times until you see ANDROID RECOVERY.
-With ANDROID RECOVERY now showing where fasboot was, press the VOLUME UP button. It will tell you that it is starting android recovery mode.
This will take you to a screen that shows a picture of an android next to a triangle with an exclamation mark (!) inside of it.
-From that screen press both the VOLUME UP and VOLUME DOWN keys at the same time.
If you made it this far, you're now in the stock android recovery. Using the volume buttons, key down to Wipe Cache Partition then press the power button to select. You will be taken to a confirmation screen. Key down and select Yes. Wait for it to complete. After you wipe the cache try rebooting back into CM9. This will take slightly longer than usual as your cache has to rebuild itself. If you can boot back up successfully, click the link above. Download the patched CM7 Bootstrap Recovery and install it. If you don't know what to do from there, open the application "CM7 System Recovery" and click "Install Recovery" -- You will now be prompted to grant or deny it superuser permissions. Allow them. You will receive a message saying the install was a success! Click OK. Now plug your phone back into the wall outlet and hit "Recovery Mode" and your phone will boot into BSR! From there just go to backup and save it to your external SD card. You can find your backups later via the file explorer of your choice under /mnt/sdcard/clockworkmod/backup. Note: You can rename the file so you know which ROM is which, just don't add spaces to the file name or it will ruin your backup and you will not be able to restore it. NO SPACES!!!
FYI you will still see the Motorola logo immediately after it turns back on. It takes a minute or two to boot into custom recovery.
I've been through a lot of trial and error with the X2 and these steps have helped me plenty of times. Hopefully they do the same for you....Good luck.
Cyanogenmod all day
Click to expand...
Click to collapse
I am having a similar but different problem with the patched BSR. I had it running fine while using CM9 on my Droid X2, but now I am running MIUI, and when I install and attempt to get into the custom recovery, it seems like it attempts to load it, but does not. What I get is a jumbled screen that has the colors of the custom recovery, so I can tell it is attempting to come up, but something is going wrong. It shows that jumbled screen for a few seconds, then goes black and eventually just shuts down. I have tried EVERYTHING I can think of to fix this. I have tried a fresh download of the patched BSR, and even did a fresh SBF and reinstall of MIUI, but nothing fixes it. Any advice you have would be greatly appreciated. Thanks!
I would re flash sbf
if you have been using ezSBF
use rsd lite, vise versa, or try a different sbf version like 2.3.3 and take ota update
or see if someone could upload a nandroid backup
Sent from my MB870 using xda premium
The odd thing is, if I restore to CM7 or CM9, then the patched BSR will work again. It seems it only goes bad with MIUI. Could the ROM somehow affect the BSR installation and/or function? I wouldn't think this is the case, as other are using the patched BSR with MIUI without trouble.
Sent from my MB870 using xda app-developers app
So, I installed safestrap and rebooted. Everything was fine, I let it boot normally and then rebooted again to get into recovery. In the recovery menu I tried installing a zip, and it told me I had to enable the safe system, so I did so. Now when I reboot the phone, I get a pure black screen and the phone is completely non-responsive. Trying to power it on does nothing, what should I do?
edit: OK, if I hold down power & the volume key, the screen will flash. If I hold down power again I can get back into recovery. I'm trying to disable safe system now, hopefully that'll work.
edit 2: Yep, that worked
Just curious in the safe side, did you actually flash any custom ROM?
Sent from my DROID RAZR using xda app-developers app
Hi,
I'm new to rooting and modifying and I'm sure I really screwed things up. My main issue is that my Razr is stuck in a bootloop and when I go to use Safestrap to recover it, the utility won't work. I'll try and detail everything I did that led up to this.
Yesterday, I rooted my stock ICS Verizon Razr xt912 using pedrotorresfilho's method. It worked without a hitch. I installed ROM Manager and then Safestrap 2.01. I used Safestrap to install CWM Touch Only Recovery. Part of the directions had me use the SuperSU to set Safestrap to denied after all was said and done. Safestrap created a restore file which I placed in my external sd. After that everything worked like it was supposed to.
Today, I decided to flash a custom ROM, but first I wanted to update to the latest version of Safestrap. I couldn't access it to uninstall the previous version because I had set it to denied. I re-granted its permission. Before I went to uninstall it I decided to go all the way back to stock thinking I probably screwed things up. I never set it back to denied. I rebooted my phone and it went into the startup screen for Safestrap. I hit the menu key, the screen went black as if it was going into the main menu and instead it starts to boot and gets stuck in a bootloop. Every time I hit volume down + power button and reboot the phone it keeps on doing this. I cannot get Safestrap to work so I can recover my phone.
I tried to use the default recovery but that won't work either. Hitting the right combination of buttons only brings me back to the Safestrap menu. I have been looking all over the forums here and elsewhere and nothing is helping. The utilities I have seen won't work for me. I don't care if I have to revert back to factory settings.
I'm sure other people will be more help, but I'll throw something out there. Hold volume down and power until it shuts off then immediately hold both volume and power. It should bout into the bootloader. Select AP fastboot and use mats utility to restore to factory.
Also, don't kill the battery if this doesn't work wake fire me knowable help.
Sent from my DROID RAZR using xda app-developers app
Thanks for the response. I was finally able to get into the bootloader using the instructions you gave me and selected the AP fastboot. Unfortunately, the power button + volume key method wouldn't work and now the battery is dead. I have since plugged it in but now it won't charge and the utility says the battery is too low to run it. Whenever I pull the cable out it gives me the battery symbol with a question mark inside. I'll leave it plugged in over night and hopefully it gives me something.
Moosiah said:
Thanks for the response. I was finally able to get into the bootloader using the instructions you gave me and selected the AP fastboot. Unfortunately, the power button + volume key method wouldn't work and now the battery is dead. I have since plugged it in but now it won't charge and the utility says the battery is too low to run it. Whenever I pull the cable out it gives me the battery symbol with a question mark inside. I'll leave it plugged in over night and hopefully it gives me something.
Click to expand...
Click to collapse
I don't think that's gonna work, you might want to check this out. I think you're going to need it.
http://forum.xda-developers.com/showthread.php?p=20521609
There is also an alternative method, but I couldn't find it.
Sent from my DROID RAZR using xda app-developers app
I saw this method earlier and was hoping I didn't have to go this route. But, it looks like this is my only option short of calling customer service, bs'ing them on why my phone is acting up, and hopefully not get charged full price for a replacement.
Thank you for the help. Next time I'm going to take the time and read up on everything I need to know before I start modifying.
No problem, let me know how it turns out
Sent from my DROID RAZR using xda app-developers app
Update:
I had tried to make my own Motorola Factory Cable but my skills with soldering and such are sub-par so I decided to order a pre-made cable from a Chinese company on Ebay. After a month I finally got the cable today and it works like it should. After going through the steps my Razr boots into AP Fastboot mode. It tells me the battery is okay and is ready for programming. I downloaded the ICS fastboot file and RSD Lite 5.7. When I go through the steps with RSD it loads the files but it won't recognize my device. I repeatedly hit the buttons but nothing shows up. I re-installed it but the same problems persists. If I understood the directions correctly I need the Motorola Device Manager in order to get the USB drivers on a pc (using a friends comp, don't have one of my own atm). I installed it from Motorola's page but when I plug in my Razr nothing pops up. I've tried to find the drivers online but all the links I have found direct me back to the Motorola page. Is there a way to get the drivers without connecting my phone to a computer?
Did I follow the directions right? Is there something I am completely missing?
For a recap. I fubar'd my Razr, it won't charge that is why I needed the "factory cable", battery is okay, but when I connect with either this cable or a normal micro-usb cable the comp won't even see that it is there.
Edit: I was finally able to download the USB drivers from Matt's Razr Utility 1.7 and then RSD was able to recognize my phone. I was able to flash ICS back onto the phone and now I have a fully functioning RAZR. Curious though, I was made to understand that when I flashed the OS that everything would be erased and I would start over. When my phone turned on it brought me back to the state I had it before it bricked. It was still rooted.
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
I'm special
bdpope88 said:
Hello,
I'm rooting/installing a custom rom on a friends phone. I'm on 2.3.5, .418. I successfully rooted using the self-extracting method. I've been trying to flash CWM/bootstrap to no avail. I was wondering if anyone had any ideas on what to do?
I've tried droid2bootstrap v1.0.5 and This .apk method. Neither seem to work. When I tell the phone to boot into recovery via the application is just reboots normally, if I select booting into recovery via vol- + pwr once I select android recovery it goes into a screen similar to that of cwm recovery, but there are no options and I have to perform a battery pull to reboot the phone.
Any help/ideas would be fantastic.
Thanks!
Click to expand...
Click to collapse
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
bdpope88 said:
Well, found out what the issue was. The .apk method linked above asked that you plug in your phone to an AC outlet. I thought this was a, to ensure that your battery is high enough. With the battery at 100%, I ignored the warning. Going over the issue one last time, I tried plugging in the phone and it worked like a charm.
I'll leave this up just in case someone in the future is as special as I am.
Click to expand...
Click to collapse
LOL. Well done sir.