Related
I might not have got enough sleep last night, so please excuse me if I missed this out right in the how to.. but I was up to 5 am last night putting Preware on my HP Touchpad and CM 2.1. The installing of Apps and playing in both ensued into the wee hours..
In my excitment I woke the wife.. and not thinking straight I thought I could get to the CWM via the same method as I used to building it. I pressed Vol Up and Power and it went back to USB bootie mode, and I couldnt get it out of that mode.. eventually I just reran the Acme installer. thewife went back to bed unimpressed.
So here is my question, I know how to boot from CM how via reboot into recovery mode, and then I can choose to boot to WebOS or CM. But from WebOS, how do I boot into Android? Or how do boot back into the Clock work menu so I can choose again ?
Thanks,
SorrowsTyr
.
There is an application in Preware called Cyboot that allows for what you want.
Or
You can install the patch that adds new buttons to the drop down power menu
Or
You can go to "Device Info" > "Reset Options" > Reboot
Yes! That us exactly what I want. Installed cyboot and Adv. Reset Options.
Thanjs!
Sent from my LG-P999 using XDA App
sorry for hijacking the thread,
but if i am stuck on the white usb screen, how do i get out of it?
Like for my phone, if i am in download mode i just take out the battery and restart my phone...but i dont we can remove battery in the Touchpad....
If you followed the instructions in the Dev section you should have installed Moboot, which give you the option to choose your OS when booting/rebooting.
viny2cool said:
sorry for hijacking the thread,
but if i am stuck on the white usb screen, how do i get out of it?
Like for my phone, if i am in download mode i just take out the battery and restart my phone...but i dont we can remove battery in the Touchpad....
Click to expand...
Click to collapse
Hold down power and home for about 30 sec.
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
I'm absolutely new to the custom rom scene and I figured I would root my phone and install the rom from here:
http://forum.xda-developers.com/showthread.php?t=1759642
It went perfectly fine and I started the like the idea of being to install what I want onto a phone, so I decided to make the jump to install CM10.
I ran a nandroid + TB backup and copied the backup to my computer. Then I dragged my CM10 rom (from http://www.droidhive.com/forums/index.php?/topic/1470-cm10-unofficial-for-d2vzw/) to the root directory of my phone. Then I ran rom manager to install cm10. The phone reboots into recovery but gets stuck on recovery. It will constantly reboot and once it reaches recovery, the loading bar with the picture of the green android robot in the background loads about 20-25% of the way, and then the phone vibrates and acts as though I just boot it up (and this process cycles).
I can't get it to ever get past this 20-25% mark and it isn't recognized by my computer to flash it back to stock and I can't do a nandroid restore since I can't get past this state.
Is my phone bricked and if so/not so, what should I do?
redxv said:
I'm absolutely new to the custom rom scene and I figured I would root my phone and install the rom from here:
http://forum.xda-developers.com/showthread.php?t=1759642
It went perfectly fine and I started the like the idea of being to install what I want onto a phone, so I decided to make the jump to install CM10.
I ran a nandroid + TB backup and copied the backup to my computer. Then I dragged my CM10 rom (from http://www.droidhive.com/forums/index.php?/topic/1470-cm10-unofficial-for-d2vzw/) to the root directory of my phone. Then I ran rom manager to install cm10. The phone reboots into recovery but gets stuck on recovery. It will constantly reboot and once it reaches recovery, the loading bar with the picture of the green android robot in the background loads about 20-25% of the way, and then the phone vibrates and acts as though I just boot it up (and this process cycles).
I can't get it to ever get past this 20-25% mark and it isn't recognized by my computer to flash it back to stock and I can't do a nandroid restore since I can't get past this state.
Is my phone bricked and if so/not so, what should I do?
Click to expand...
Click to collapse
Hmm honestly the easiest way out of this is just to flash the stock rom of your carrier through odin (download mode and flash), easy fix. You could try messing around with the recovery and whatnot, ie try flashing a new recovery through adb somehow, but easiest and the most least painful way seems to be to just odin back to stock and try again. and also, i dont get why people use rom manager, heard too many horror brick stories about that. Just adb the recovery to the phone and flash the zip. Why even bother with rom manager.
good luck, hope i helped :good:
I can't get my computer to recognize my phone to use odin / adb.
redxv said:
I can't get my computer to recognize my phone to use odin / adb.
Click to expand...
Click to collapse
Did you put your phone in download mode? turn off, and then hold home vol down and power at same time.
Never mind..
I was asking same thing like Unleashed12
unleashed12 said:
Did you put your phone in download mode? turn off, and then hold home vol down and power at same time.
Click to expand...
Click to collapse
Like I said, when I book into recovery/download mode, it just boot cycles.
That is: phone turns on. Samsung boot screen, then android robot screen, loading bar goes about 1/4 of the way, then phone goes black, and starts at samsung boot screen again.
redxv said:
Like I said, when I book into recovery/download mode, it just boot cycles.
That is: phone turns on. Samsung boot screen, then android robot screen, loading bar goes about 1/4 of the way, then phone goes black, and starts at samsung boot screen again.
Click to expand...
Click to collapse
Sounds like you haven't actually entered the download mode... power off> hold at same time power, home and vol down... keep holding until the phone turns back on. you should enter download then.
I personally feel like you just have a dirty install without knowing more. Once you enter recovery I'd just data reset, cache reset, dalvik reset and reflash same rom... or a backup
Yeah, my bad. I didn't hold it down long enough. I'm such a noob.
Don't forget to hit thanks for those who helped you...
Sent from my SAMSUNG Captivate™ Glide i927
Aquethys said:
Don't forget to hit thanks for those who helped you...
Sent from my SAMSUNG Captivate™ Glide i927
Click to expand...
Click to collapse
haha Thanks for that!
Installed CARBON-UNOFFICIAL-20130923-dlx-CDMA-M7.zip followed by gapps-jb-20130813-signed.zip and booted the phone. I restored my apps with ROM Toolbox Pro and then tried to restore phone data (I selected Bluetooth pairings, Wifi, Wallpaper, and messages). It then suggested I reboot the phone to apply the settings. The phone then went into a loop showing the Carbon splash screen followed by a brief look at the lock screen, followed by a prompt "com.android.system has stopped unexpectedly" followed by the Carbon splash screen and so on. After many, many attempts, I finally was able to reboot into recovery by quickly unlocking the phone, selecting the boot options menu, selecting "recovery", and pressing "ok" in about 2 seconds or less. I then restored my nandroid and am back to stock/rooted. I do have a suggestion. If possible, the power button/down volume should always be available by default to get back to recovery and/or the bootloader menu. I understand the risky nature of choosing to use these ROMs but if that fail safe were always provided, it would make it a lot less risky. After a brief look at the ROM, I would like to go back to it but I am a little gun shy at the moment.
Note: I would have posted this in the Droid DNA developer area but apparently I haven't made enough posts because it would not let me.
brucefan42 said:
Installed CARBON-UNOFFICIAL-20130923-dlx-CDMA-M7.zip followed by gapps-jb-20130813-signed.zip and booted the phone. I restored my apps with ROM Toolbox Pro and then tried to restore phone data (I selected Bluetooth pairings, Wifi, Wallpaper, and messages). It then suggested I reboot the phone to apply the settings. The phone then went into a loop showing the Carbon splash screen followed by a brief look at the lock screen, followed by a prompt "com.android.system has stopped unexpectedly" followed by the Carbon splash screen and so on. After many, many attempts, I finally was able to reboot into recovery by quickly unlocking the phone, selecting the boot options menu, selecting "recovery", and pressing "ok" in about 2 seconds or less. I then restored my nandroid and am back to stock/rooted. I do have a suggestion. If possible, the power button/down volume should always be available by default to get back to recovery and/or the bootloader menu. I understand the risky nature of choosing to use these ROMs but if that fail safe were always provided, it would make it a lot less risky. After a brief look at the ROM, I would like to go back to it but I am a little gun shy at the moment.
Note: I would have posted this in the Droid DNA developer area but apparently I haven't made enough posts because it would not let me.
Click to expand...
Click to collapse
Its not removed, it still works. If you can't get it to fire then try holding power until the key lights blink, then when they stop and the screen blanks, let go and hold volume down, this always works for me and I'm sure I flash more broken stuff then you do
Also, stop restoring settings between Roms, that's why it broke. For a first flash of a new ROM always do it fresh and don't restore anything, it'll go so much smoother.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
Its not removed, it still works. If you can't get it to fire then try holding power until the key lights blink, then when they stop and the screen blanks, let go and hold volume down, this always works for me and I'm sure I flash more broken stuff then you do
Also, stop restoring settings between Roms, that's why it broke. For a first flash of a new ROM always do it fresh and don't restore anything, it'll go so much smoother.
Tapatalked from my HTC DNA - Akakaze
Click to expand...
Click to collapse
Thanks.
The phone seems to be stuck in an infinite battery loop.
1) With the battery in, not using the charger.
It first boots into a grey battery for a couple of seconds and then it gets to a green charging battery. I can hear a short vibration, and it boots again into the grey battery and then into the green one. The phone is stuck into that loop until the battery drains.
2) With the battery in and the USB cable plugged in.
The phone boots into the grey battery and then into the green one. It stays there forever. No vibration sound and no rebooting. It keeps charging until hitting the 100% message.
Now, a few days ago I was able to hold the power button down and the phone would reboot normally. I could use the phone for a few hours until, all of a sudden, it would turn off and boot again into the battery loop. Holding the power button and rebooting normally would ONLY work with the USB cable in. If I unplugged the USB cable, the phone would be stuck in the battery loop.
A couple of days ago, I noticed that when I managed to reboot normally and pressed the power button, the phone would ask me if I wanted to restart, and a couple of seconds after that it would reboot into the battery loop.
Now holding the power button down with the USB cable in won't do the trick anymore. It is as if the power button is disabled or something.
Is there a fix for this? If I hold the volume button down I can get to the download mode (Odin Mode). THe info I get is as follows:
Product name: SGH-i777
Custom Binary Download: Yes (1 counts)
Current Binary: Samsung Official
The only way to get out of the download mode is by removing the battery.
Any ideas as to what's going on here?
thanks!
Looks like the culprit is the power button.
I flashed the newest Samsung firmware using Odin in download mode, and I could reboot normally after flashing. I'm using Auto Screen On/Off to wake up the phone, and it does a good job. The Power Off Button apps didn't seem to work, though.
Thing is, if I power off the phone or restart it, it goes into the battery loop again, and the only way to reboot normally that I know is by flashing the stock firmware again.
Is there any easier, faster way to reboot normally with a broken power button?
thanks!
cirerita said:
Is there any easier, faster way to reboot normally with a broken power button?
Click to expand...
Click to collapse
You could try this (it's another power button app https://play.google.com/store/apps/details?id=com.painless.pc). I've used it in the past with great success.
If it doesn't work for you you're currently not rooted - I know your stats show you've downloaded a custom binary, so you shouldn't have any problems.
Post back if you do, and also give us more information regarding which rom you're on.
Thanks, that app is really useful.
I used a custom rom a while ago but then I switched back to stock. I'm using the latest one from Kies (4.1.2, I think to recall). I use Framaroot to root the phone so I can use some apps I like.
Phone still reboots randomly. Maybe I need to clean the cache. Is there an app for doing that while running Android?
Alternatively, is there a kernel/rom that allows me to reboot normally, bypassing the battery loop? The Odin download mode takes too long because I have to flash the stock firmware, and the stock Recovery mode is useless to me because my power button is broken.
IS it possible to access Recovery mode with a broken power button?
thanks!
Sure, but the app I linked allows you to boot to recovery also.
A good custom kernel for a rooted 4.1.2 would be AJK 4.9, the No Swap version I believe. You'd be better off reading the op in the AJK thread.
Thanks, I'll take a good look at the AJK thread. Is it any better than the Siyah kernel?
Problem is, if the phone reboots randomly, then I'm stuck in the battery loop again and I need to flash the stock firmware yet again to be able to reboot normally and bypass the battery loop. I would need some sort of custom boot which I could access pressing the volume button, and which would allow me to reboot bypassing the battery loop.
SteveMurphy said:
Sure, but the app I linked allows you to boot to recovery also.
A good custom kernel for a rooted 4.1.2 would be AJK 4.9, the No Swap version I believe. You'd be better off reading the op in the AJK thread.
Click to expand...
Click to collapse
Just flashed AJK 4.9 and no more random rebootings as of now... Plus, if I reboot manually, it does not get into the dreaded battery loop. So far so good. Thanks a lot for the tip.
cirerita said:
Thanks, I'll take a good look at the AJK thread. Is it any better than the Siyah kernel?
Problem is, if the phone reboots randomly, then I'm stuck in the battery loop again and I need to flash the stock firmware yet again to be able to reboot normally and bypass the battery loop. I would need some sort of custom boot which I could access pressing the volume button, and which would allow me to reboot bypassing the battery loop.
Click to expand...
Click to collapse
AJK's Kernel is based off Siyah.