Related
These are the steps to boot your Droid 2 phone into Recovery Mode should you need to.
1. Turn Droid 2 Off
2. Press 'X' on the physical keyboard and then Press and HOLD Power button until the Exclamation Point/Android picture shows(after motorola symbol).
3. To access menu options Press the "Search" button depicted by the Magnifying glass on the Keyboard and the menu items will show up.
4. Browse options with the Volume Up and Volume Down keys and select option with the Camera button all on side.
5. Select first option of "Reboot phone" or risk messing up your brand new Droid 2!
I can add a picture if someone requests it (any ideas of how to best take said picture?) I'm new the the forum so if this post is in the wrong place and/or someone else had provided the info just let me know. (I looked but you can never be too sure.)
-newk8600
Thanks for this info, it's very helpful... I also learned that to get into bootloader manually, power on the phone and hold the Keyboard UP key.
Nice to know.
Also, 'Safe Mode' (for killing third party apps stuck in force close loop at start up) is Power On and hold the Soft "Menu" (the four squares).
Another little tip.
newk8600 said:
These are the steps to boot your Droid 2 phone into Recovery Mode should you need to.
1. Turn Droid 2 Off
2. Press 'X' on the physical keyboard and then Press and HOLD Power button until the Exclamation Point/Android picture shows(after motorola symbol).
3. To access menu options Press the "Search" button depicted by the Magnifying glass on the Keyboard and the menu items will show up.
4. Browse options with the Volume Up and Volume Down keys and select option with the Camera button all on side.
5. Select first option of "Reboot phone" or risk messing up your brand new Droid 2!
I can add a picture if someone requests it (any ideas of how to best take said picture?) I'm new the the forum so if this post is in the wrong place and/or someone else had provided the info just let me know. (I looked but you can never be too sure.)
-newk8600
Click to expand...
Click to collapse
I am assuming that if you have clockwork recovery it will boot into that correct?
I can only assume that also, I'm new to android hacking so from what I've read I think so but I'm not sure.
I'm sure a more experienced member could confirm.
This doesn't boot into clockwork at least on the D2. I tried it with koush's bootstrap installed and it just boots into the stock recovery. I might try to do it again just to confirm.
Sent from my DROID2 using XDA App
i have found to boot into boorstrap recovery is pull the battery out for a few seconds then power the phone on. I realized that whenever my phone died and i charged it and turned it back on it would always boot to clockwork
jerseyh22accord said:
i have found to boot into boorstrap recovery is pull the battery out for a few seconds then power the phone on. I realized that whenever my phone died and i charged it and turned it back on it would always boot to clockwork
Click to expand...
Click to collapse
I don't know if it does it every time but when i hold my volume down rocker and the power button it boots into clockwork, give it a try
Sorry for the stupid question, but why do I need to do this? I'm new to Droid. Also, will this delete my data?
You don't really /need/ to do this it's just some information I thought would be helpful to put out there. Most people will never need to boot into the stock recovery.
If you decide to root your droid 2 then you will use koush's bootstrap to boot into clockwork recovery and make backups and install ROMs if you so choose.
Sent from my DROID2 using XDA App
Ok, thanks. Sorry for the noobish type of question.
1454 said:
Ok, thanks. Sorry for the noobish type of question.
Click to expand...
Click to collapse
It's cool. I'm still a semi-noob in some aspects, everybody needs a little info every now and then.
Sent from my DROID2 using XDA App
I have been able to get into the android system recovery but am now getting message on main screen of recover "E:Can't open /cache/recovery/command" Is this a cause for concern.
Don't worry about the error - it's normal.
I accidentally,... . unknowingly wiped the RED "system" button in Safestrap 3.12 on my Droid RAZR M today. (I was suppose to be wiping the cash and dalvik, but missed) I'm a retard I know. :crying:
Now I cant get into AP Fastboot to restore the phone from this hard brick!
When I press the power button along with the volume buttons, the only thing that happens is the red Motorola 'M" appears for a few seconds then the safe strap screen appears with the little sad robot, but that's it no AP Fastboot. Pressing the on screen buttons to enter Safestrap Recover do not respond. Oh boy I'm afraid I really did it this time. Its on the charger but i don't know if its even charging with out as OS?
Battery power was at 60% before i bricked it (i think). RSD Lite or my PC for that matter don't even see the phone when its plugged in.
Can this be saved? Or do I need to take a trip down to the Verizon Wireless store?
Droid RAZR M
4.1.2 OTA
Rooted
Locked Bootloader
Safestrap 3.12
Partitioned 64GB SD card utilizing Linked2SD
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Really? Well I hope your right. It gives me some hope. lol So do you have any idea of what alternative key combo i might have to use? Thank you for the reply.
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! You were right! was able to get into AP Fastboot with a different button combo like u said. :victory:
shane1 said:
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
Click to expand...
Click to collapse
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
It worked! I utilized the NEWER version of Mat's utility and it did it!!! Woo Hoo!! Thank you so very much. Thank you all for all the speedy help.
SARM1084 said:
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
Click to expand...
Click to collapse
hey no prob! i try to help as much as i can !
bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Halp
This thread saved my life, then killed me. The suggestion about the different keys was spot on, i got into fast boot mode, then ran that utility. It totally failed me, I must have killed my phone pretty dead, and now there are no more key combos (the suggested one worked at first but now its just making the screen go blank) to try to get back into fast boot to try again. any more suggestions? on the up side verizon just pushed that update so i figure i can blame that to attempt an exchange
Did you take the update before using that utility? If you did, which version did you use? If you were already updated, then you needed to run 1.20. If you ran the wrong utility, that will cause issues. Now, since you can't boot, it sounds like your battery is dead. When you get to the blank screen, plug it in and leave it to charge for a while.
I'm no expert by any means but I'll try to help as best i can. If not me I'm confident someone else will. Now, I apologize because I didn't understand your original post.
Could you elaborate a little more please?
1. What were you trying to do with your phone prior to things going wrong, if they went wrong at all.
2. you mentioned AP Fastboot. So IM going to assume that at least you can access it. (not the same problem that I was having) that's a good thing! lol
3. Are you utilizing a utility like the one by Matt? Or are you doing something else? Like flashing firmware etc.
4. What were you in Fastboot for? What were your intentions?
I hope this doesn't come over a condescending. Just trying to get a Clearer understand of your issue so we can help.
Sent from my XT907 using xda app-developers app
Sorry double post
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Look at my previous post
Sent from my XT907 using xda app-developers app
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
PartyOnINSANE said:
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No problems brother. Glad to see your up and running.
Sent from my XT907 using xda app-developers app
Stuck in a Boot Loop
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
gjhkl said:
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
Click to expand...
Click to collapse
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
RikRong said:
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
Click to expand...
Click to collapse
I have done your steps and I get the menu up, but when I try to scroll down with the volume down button, it doesn't move. It just stays on "normal powerup". How can I fix this?
I'm having some crazy times with my new phone. I can't seem to get it into Download mode. I've tried several button combos - but no dice. They all take me to "Factory Mode" - wehre I can test the individual components of the phone.
I can get ADB working - but when I type "adb reboot download" - the phone just cycles back to the regular OS. When I type "adb reboot recovery" - I get the android + red exclamation mark.
Any advice? I'm really confused as to what's going on. I can't do anything with Odin without getting it into download mode...
Have you ever got it to download mode before?
May I know on whch phne u r trying
Sent from my Micromax A50 using Tapatalk 2
I just got the phone today from Craigslist. It is the 9500.
Did you try just holding the power + volume down only for like 5 seconds ?
Don't hold the home button.... Just hold volume down + power
-------------------------------------
If I have helped you, please hit the "Thanks" button
-Sent from one of my Obsessions
Questions go in Q&A
Please read the Forum Rules.
Thread moved.
glensta said:
Did you try just holding the power + volume down only for like 5 seconds ?
Don't hold the home button.... Just hold volume down + power
-------------------------------------
If I have helped you, please hit the "Thanks" button
-Sent from one of my Obsessions
Click to expand...
Click to collapse
I tried this - and I get the android with a red exlimation mark.
On that screen, I can press the menu to get to following options:
Reboot
Apply update from sdcard1 (and 2 and cache)
Wipe data
Wipe cache
Backup user data
Restore user data
hospadam said:
I tried this - and I get the android with a red exlimation mark.
On that screen, I can press the menu to get to following options:
Reboot
Apply update from sdcard1 (and 2 and cache)
Wipe data
Wipe cache
Backup user data
Restore user data
Click to expand...
Click to collapse
I don't think you're doing it right. You must be pressing volume + power, and sounds like you're in stock recovery only.
Pull battery out, put back in, then again Try , volume down + power for at least 5 seconds or until you see the downloading screen appear, then you'll have to press volume up to confirm. At that point you should be in download mode
hospadam said:
I'm having some crazy times with my new phone. I can't seem to get it into Download mode. I've tried several button combos - but no dice. They all take me to "Factory Mode" - wehre I can test the individual components of the phone.
I can get ADB working - but when I type "adb reboot download" - the phone just cycles back to the regular OS. When I type "adb reboot recovery" - I get the android + red exclamation mark.
Any advice? I'm really confused as to what's going on. I can't do anything with Odin without getting it into download mode...
Click to expand...
Click to collapse
Power off - volume dawn , home buttun , power buttun and you will go in dawnliad
Sent from my GT-I9505 using xda premium
Thank you everyone for your help so far. I'm pretty sure the guy who had it before me must have put a custom ROM on it... and now I'm dealing with the consequences. Here's what I know: the phone (and box) physically say it's a i9500 - but when I go to "About Phone" when the phone is on - it says it's a i9505.
I promise I'm doing the following right...
Volume Up + Power = "Factory Mode"
Volume Down + Power = Red Triangle Exclamation mark
Volume Down, Home Button, Power Button = Red Triangle Exclamation mark
I've tested to see if root is still enabled on the phone - it isn't.
Is there anything else I can try? Can I push something via adb to reset this all? I tried "adb reboot download" - but it just reboots normally. Thanks!
hospadam said:
Thank you everyone for your help so far. I'm pretty sure the guy who had it before me must have put a custom ROM on it... and now I'm dealing with the consequences. Here's what I know: the phone (and box) physically say it's a i9500 - but when I go to "About Phone" when the phone is on - it says it's a i9505.
I promise I'm doing the following right...
Volume Up + Power = "Factory Mode"
Volume Down + Power = Red Triangle Exclamation mark
Volume Down, Home Button, Power Button = Red Triangle Exclamation mark
I've tested to see if root is still enabled on the phone - it isn't.
Is there anything else I can try? Can I push something via adb to reset this all? I tried "adb reboot download" - but it just reboots normally. Thanks!
Click to expand...
Click to collapse
First power off the phone
Sent from my GT-I9505 using xda premium
I have powered off the phone. In fact, I've been pulling the battery just to ensure its totally off.
Maybe i could help
hospadam said:
I have powered off the phone. In fact, I've been pulling the battery just to ensure its totally off.
Click to expand...
Click to collapse
It's a totally different device but it happened on my Nexus 10 because i got rid of the custom recovery and deleted the Rom with data (Don't ask why) FOLLOW! - Power off + Volume down, Once it's in "Volume Down + Power = Red Triangle Exclamation mark" Press and Hold all the button except Home button until it restarts the Bootloader and Hopefully it shows all the options like - Start, Recovery & What ever else
If you can see the options then You are in Luck! Now all you need to do is get the Stock Rom and Flash it through Odin and It should work!
Please let me know if it works, Add me on Skype, If you are confused (Skype - ExjeetzZ)
:silly:
ExjeetzZ said:
It's a totally different device but it happened on my Nexus 10 because i got rid of the custom recovery and deleted the Rom with data (Don't ask why) FOLLOW! - Power off + Volume down, Once it's in "Volume Down + Power = Red Triangle Exclamation mark" Press and Hold all the button except Home button until it restarts the Bootloader and Hopefully it shows all the options like - Start, Recovery & What ever else
If you can see the options then You are in Luck! Now all you need to do is get the Stock Rom and Flash it through Odin and It should work!
Please let me know if it works, Add me on Skype, If you are confused (Skype - ExjeetzZ)
:silly:
Click to expand...
Click to collapse
I was so hopeful this would work... But no dice. It never leaves the red triangle screen. I held it for like 20 seconds.
A little tired right now, so hopefully I didn't miss any simple solution.
If you have no luck....
I have tried my USB jig used with my ex-I9100. It was used to force download mode from power off condition and reset the custom flash counter.
I have tried it on my I9500 and will force download mode (no reset).
You can buy them on eBay for a couple dollars or make them yourself from and old male micro USB connector and some resistors. Guides are found on XDA or Google.
Sent from my GT-I9500 using xda premium
I'm not sure if this is any help...
But I'm pretty sure the previous owner really messed up the ROM. The IMEI number on the back of the phone does not match the one that is being reported by the OS. When I checked the one that is being reported by the OS, it comes up as a Galaxy S3.
Any options besides the jig to reset everything?
hospadam said:
I'm not sure if this is any help...
But I'm pretty sure the previous owner really messed up the ROM. The IMEI number on the back of the phone does not match the one that is being reported by the OS. When I checked the one that is being reported by the OS, it comes up as a Galaxy S3.
Any options besides the jig to reset everything?
Click to expand...
Click to collapse
Only option return it for a refund ... if your imei doesn't match something isn't right
Sent from my GT-I9505 using xda premium
hospadam said:
I'm not sure if this is any help...
But I'm pretty sure the previous owner really messed up the ROM. The IMEI number on the back of the phone does not match the one that is being reported by the OS. When I checked the one that is being reported by the OS, it comes up as a Galaxy S3.
Any options besides the jig to reset everything?
Click to expand...
Click to collapse
Looks like an engineering unit to me, possibly a prototype. A dump would have been nice, assuming the software allows it.
Sent from my GT-I9505 using xda premium
For the the original galaxy s gti 9000 there was a plug to insert in the micro usb port, that would force the devuce to boot into download mode... there was an issue with some devices, and that was the solution... it also worked in case of a brick. I got one for my s1... 2 dollars on ebay. Could it work?
Sent from my GT-I9505 using xda premium
rlrmineiro said:
For the the original galaxy s gti 9000 there was a plug to insert in the micro usb port, that would force the devuce to boot into download mode... there was an issue with some devices, and that was the solution... it also worked in case of a brick. I got one for my s1... 2 dollars on ebay. Could it work?
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Already suggested, Read my previous post
Sent from my GT-I9500 using xda premium
Yes I lost manual recovery. I've tried many many times; with the power off I hold the volume up and the power button at the same time. As soon as I see the "little blue letters" on the left upper corner I let go. I've also tried volume up + home + power... However the cel vibrates again and does a normal system reboot.
I Odin it back to stock, factory reset...same deal.
I can reboot to recovery with Goomanager, but I can't understand why it won't manually.
Any help will be appreciated!
EDIT: Problem solved by scott14719. Here it is: As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them.
You mentioned GooManager so I'm guessing TWRP? Hold the home and vol up buttons just a little bit longer (few seconds) before you let them go.
If nothing else works try to flash OUDHS (CWM). Make sure you read the thread and follow the directions. Of course, anything you do to your phone has risk and it is your responsibility.
scott14719 said:
You mentioned GooManager so I'm guessing TWRP? Hold the home and vol up buttons just a little bit longer (few seconds) before you let them go.
If nothing else works try to flash OUDHS (CWM). Make sure you read the thread and follow the directions. Of course, anything you do to your phone has risk and it is your responsibility.
Click to expand...
Click to collapse
thanx...I tried holding the buttons a little longer but it will do a normal launch.
I already tried solving the issue by installing cwm, nice rainbows btw. It installed well but in order to use cwm I had to reboot recovery thru goo...
The manual download works though....
Sent from my SAMSUNG-SGH-I337 using xda premium
Edit
I have thus problem too. I'm just using goo manager right now.
You really need to wipe and start from scratch.
Odin stock rom, then boot to the rom, do complete device reset. Root, then load the recovery of your choice...15min procedure. Or keep trying things, and waste time. Can do this with my eyes closed as I have done this many times. Good luck.
TheAxman said:
You really need to wipe and start from scratch.
Odin stock rom, then boot to the rom, do complete device reset. Root, then load the recovery of your choice...15min procedure. Or keep trying things, and waste time. Can do this with my eyes closed as I have done this many times. Good luck.
Click to expand...
Click to collapse
I did... no dice. Thanx for your time, I appreciate it.
Sent from my SAMSUNG-SGH-I337 using xda premium
irl9000 said:
It prolly got revoked cuz u reneged on bounty?? gotta feed the gods??
sent le skyblu duex
Click to expand...
Click to collapse
Ouch!
---------- Post added at 08:54 PM ---------- Previous post was at 08:52 PM ----------
paleman27 said:
I did... no dice. Thanx for your time, I appreciate it.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Are you giving up? Because maybe you missed a step..because it WILL work.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
paleman27 said:
thanx...I tried holding the buttons a little longer but it will do a normal launch.
I already tried solving the issue by installing cwm, nice rainbows btw. It installed well but in order to use cwm I had to reboot recovery thru goo...
The manual download works though....
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I am telling you the boot partition is corupt. It has bs from both recoveries. Oh well. Might want to read up on odin and use the partition tools. Major sh$$ happening here. Just throwing ideas at you. I love these challenges. Wish I had the problem. Serious. I maybe wrong.
I'm wondering if there is something going on now. Normally 99.9% of these types of troubles are user error, but I've seen several people now (in the AT&T S4 forums) claiming they can not manually enter into recovery. Now I am assuming CWM hasn't been updated since the auto-loki version and I know it works correctly. So I am wondering (if there is a problem) if the problem might be with a change that was recently made to TWRP or maybe one of the new installation methods that have been developed to install CWM /TWRP? Even the people that are having the same trouble with CWM seem to have had TWRP installed first.
So, people that are having trouble please list the recovery you are using, the version, when it was flashed, and which method you used to flash it.
Or maybe it is still just all user error.
---------- Post added at 11:19 PM ---------- Previous post was at 11:08 PM ----------
paleman27 said:
thanx...I tried holding the buttons a little longer but it will do a normal launch.
I already tried solving the issue by installing cwm, nice rainbows btw. It installed well but in order to use cwm I had to reboot recovery thru goo...
The manual download works though....
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
So what recovery are you on now? I have a feeling you might be holding the power button a little to long. As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them. This is from someone that had the same problem as you (from another thread):
krypticsoul said:
I just figured it out...its still the vol up+power. I just pressed the buttons too long, so it just reboot everytime.
So basically, as soon as i see the message "recovery bootin....", i let go the buttons right away.
Click to expand...
Click to collapse
Give it a try, maybe it will work for you as well.
paleman27 said:
Yes I lost manual recovery. I've tried many many times; with the power off I hold the volume up and the power button at the same time. As soon as I see the "little blue letters" on the left upper corner I let go. I've also tried volume up + home + power... However the cel vibrates again and does a normal system reboot.
I Odin it back to stock, factory reset...same deal.
I can reboot to recovery with Goomanager, but I can't understand why it won't manually.
Any help will be appreciated!
Click to expand...
Click to collapse
Have you tried a normal reset while holding volume and home. This is what I do since I am to lazy to take the extra steps and use Goo. Been working on extended power menu for odex'd rom but I am doing something wrong and can't get it to work.
Tapped from the Shear Galaxy Near You!
I used motochopper and running the latest version of twrp. I can boot just fine using goo manager and once I'm in I have no problem at all flashing files or making a back ups. So I believe it may be something wrong with twrp recovery.
waternut13134 said:
I used motochopper and running the latest version of twrp. I can boot just fine using goo manager and once I'm in I have no problem at all flashing files or making a back ups. So I believe it may be something wrong with twrp recovery.
Click to expand...
Click to collapse
When you try to manually boot into recovery are you holding the "power", "volume up", and 'home key' until you first feel the phone vibrate and then immediately release the "power" button but continue to hold the other button until the first splash screen and then let them go. I think a lot of people are holding the power button too long or the other buttons not long enough.
scott14719 said:
When you try to manually boot into recovery are you holding the "power", "volume up", and 'home key' until you first feel the phone vibrate and then immediately release the "power" button but continue to hold the other button until the first splash screen and then let them go. I think a lot of people are holding the power button too long or the other buttons not long enough.
Click to expand...
Click to collapse
You sir are correct! I just tried it and it works. Kinda feel stupid now. Thank you so much!
seems so complicated... try just volume up.
For mine (ATT 1337, on OUDHS Recovery (cwm))
if your phone is on and while the screen is on, just hold power and select reboot. as soon as it vibrates, press and hold volume up (just volume up, nothing else, maybe wait till custom firmware padlock screen shows up), and wait for the blue text at the top left of the screen... let go vol up.
if for some reason u r frozen. press power (just keep holding) til it forces reboot, then after vibrate (or maybe padlock if its too soon), press n hold just the volume up.
I would restore via KIES instead of using ODIN,
It will reset everything, just like from factory.
I've had this happen to me several times while playing around with flashing. Basically (without fail in my experience), hold power+volume up+home as you'd normally do until you see the booting recovery message and let go. It will do one of two things - boot into recovery- or - restart and vibrate-. If it restarts and vibrates, immediately hold power+volume up+home until the booting recovery message pops up again and let go. It should then boot into recovery and you shouldn't have trouble in subsequent attempts.
It took me a while to figure this out and I actually thought I had permanently bricked my phone as the phone wouldn't boot and I couldn't get into recovery. Hope this helps.
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
scott14719 said:
I'm wondering if there is something going on now. Normally 99.9% of these types of troubles are user error, but I've seen several people now (in the AT&T S4 forums) claiming they can not manually enter into recovery. Now I am assuming CWM hasn't been updated since the auto-loki version and I know it works correctly. So I am wondering (if there is a problem) if the problem might be with a change that was recently made to TWRP or maybe one of the new installation methods that have been developed to install CWM /TWRP? Even the people that are having the same trouble with CWM seem to have had TWRP installed first.
So, people that are having trouble please list the recovery you are using, the version, when it was flashed, and which method you used to flash it.
Or maybe it is still just all user error.
---------- Post added at 11:19 PM ---------- Previous post was at 11:08 PM ----------
So what recovery are you on now? I have a feeling you might be holding the power button a little to long. As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots, then let go of them. This is from someone that had the same problem as you (from another thread):
Give it a try, maybe it will work for you as well.
Click to expand...
Click to collapse
YAY!!!!!!! BINGO!!!! "As soon as you feel the phone vibrate, immediately let go of the power button but continue to hold the other buttons until the recovery boots".
A world of thanx!
kennyglass123 said:
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Thank you for moving the thread; I have had much better response here! I even got my problem solved! :good:
EDIT. Thanx for getting rid of that clown.
Okay so I have the cyanogen mod flashed on my s4. But for some reason now it won't boot into cwm recovery. Any ideas?
Sent from my SGH-I337 using xda app-developers app
bboyimpact33 said:
Okay so I have the cyanogen mod flashed on my s4. But for some reason now it won't boot into cwm recovery. Any ideas?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
In Developer options, enable the Advanced Reboot.
The 3 button combo will work, it's just a matter of timing. Remove and replace the battery, hold vol up + home, then power, holding all three, and when it vibrates, let go of power only.
You could also hook up in USB Debugging mode and issue the command:
adb reboot recovery
And if you don't have a developer option go into about phone and tap build number 7 times.
<=LongJohnSilver=> said:
In Developer options, enable the Advanced Reboot.
The 3 button combo will work, it's just a matter of timing. Remove and replace the battery, hold vol up + home, then power, holding all three, and when it vibrates, let go of power only.
You could also hook up in USB Debugging mode and issue the command:
adb reboot recovery
Click to expand...
Click to collapse
Some people, including myself, cannot get it to work with the standard procedure...the solution is to basically do it twice. Here's a copy/paste of the instructions:
Long press the power button and choose "power off". Give your phone a few seconds to turn off completely. Once it's off, press and hold these 3 buttons at the same time: POWER+VOLUME UP+HOME. Look at the top left of the screen - as soon as you see little blue text saying entering recovery, let go of all buttons immediately...but be ready...if your phone vibrates (it might be trying to reboot normally again), press and hold those same buttons again until you see the blue text again...then let go immediately. Now you will see your recovery!
jeffreii said:
Some people, including myself, cannot get it to work with the standard procedure...the solution is to basically do it twice. Here's a copy/paste of the instructions:
Long press the power button and choose "power off". Give your phone a few seconds to turn off completely. Once it's off, press and hold these 3 buttons at the same time: POWER+VOLUME UP+HOME. Look at the top left of the screen - as soon as you see little blue text saying entering recovery, let go of all buttons immediately...but be ready...if your phone vibrates (it might be trying to reboot normally again), press and hold those same buttons again until you see the blue text again...then let go immediately. Now you will see your recovery!
Click to expand...
Click to collapse
Cool
CWM recovery only requires you to push the volume up key and then press the power key until the phone vibrates and then let go of the power button only. When the blue lettering appears, let go of the volume up. The home button should only be required with TWRP.
scott14719 said:
CWM recovery only requires you to push the volume up key and then press the power key until the phone vibrates and then let go of the power button only. When the blue lettering appears, let go of the volume up. The home button should only be required with TWRP.
Click to expand...
Click to collapse
Whatever the reason, that is not the case with my phone and many others. I've read several threads of people having the same issue. I'm not sure if it's an issue with the OUDHS CWM w/ auto-loki or what.
I've never heard of letting go of the power button only while still pressing volume up, but I gave it a try just to see...it did get me into CWM recovery but only after doing it twice, similar to the method I wrote above.
I have tried letting go of both volume up and power (no pressing home at all) and never found a way to get into recovery.
Anyways, it seems there's no harm in pressing the home button either way and it's probably easier than letting go of the power button and still holding volume up...and easier to explain too lol.
jeffreii said:
Whatever the reason, that is not the case with my phone and many others. I've read several threads of people having the same issue. I'm not sure if it's an issue with the OUDHS CWM w/ auto-loki or what.
I've never heard of letting go of the power button only while still pressing volume up, but I gave it a try just to see...it did get me into CWM recovery but only after doing it twice, similar to the method I wrote above.
I have tried letting go of both volume up and power (no pressing home at all) and never found a way to get into recovery.
Anyways, it seems there's no harm in pressing the home button either way and it's probably easier than letting go of the power button and still holding volume up...and easier to explain too lol.
Click to expand...
Click to collapse
I'm having the same problem.
Have you found an answer or work around solution yet?
GS4 AT&T
Base version: I337UCUAMF3
Kernel: 3.4.0-812098
CWM Recovery: 6.0.3.6
rooted with SD format
Never been able to flash the rom successfully
cariboucar said:
I'm having the same problem.
Have you found an answer or work around solution yet?
GS4 AT&T
Base version: I337UCUAMF3
Kernel: 3.4.0-812098
CWM Recovery: 6.0.3.6
rooted with SD format
Never been able to flash the rom successfully
Click to expand...
Click to collapse
You need to read... Seriously, you are going to brick your phone. Do not try to install any custom recovery or ROM of any kind on MF3.
Why can't people read?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
bboyimpact33 said:
Okay so I have the cyanogen mod flashed on my s4. But for some reason now it won't boot into cwm recovery. Any ideas?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
My minor issue is that when I boot to recovery (twrp) it get to the twrp splash screen then freeze. Takes me another reboot or two before recovery really launches.
Tried reinstalling recovery and fixing permission, etc.. but same deal. Anyone have thoughts on this?
I boot into recovery all the time but I have to hold volume up and home button.
Bump!
I'm having the same issue. What I did was that I had the CWM recovery installed and tried to reset the flash counter. Now the phone won't boot into the recovery, it just boots up as usual when I press vol up+home+power up. I appreciate any help! :/
metalfr33ak said:
Bump!
I'm having the same issue. What I did was that I had the CWM recovery installed and tried to reset the flash counter. Now the phone won't boot into the recovery, it just boots up as usual when I press vol up+home+power up. I appreciate any help! :/
Click to expand...
Click to collapse
Can you get the blue text in the upper left corner of the screen to appear at any time?
In my case, trying to get into recovery via the 3 buttons is a matter of very precise timing if I try pressing all 3 buttons at the same time. The instant I see the blue text I let go of everything and it works. Hold it for even a fraction of a second longer and the blue disappears and it goes into a normal boot. It works much better if I press Vol Up, then add Power, then add Home. I'm doing that sequence fairly quickly but the point is I'm not trying to press 3 buttons at the exact same time.
But I'm using CWM so I don't need the 3rd button...
From a powered-down state I hold Vol Up then Power and hold both through the vibration until the blue text appears and it goes into CWM recovery just fine. There seems to be a bit more leeway in terms of how fast you need to let go this way although I just tested and holding about a half second too long caused it to bounce out of recovery and do a normal boot. Let go immediately when you see the blue.
Phone won't boot..
So after using CASUAL, my phone rebooted, and got stuck on the splash screen with RECOVERY BOOTING.. in the top left corner. I pull the battery, try to do a normal reboot; takes me to the same screen. Trying the 3 button combo for recovery; same thing. Any suggestions?? I am NOT on MF3 Firmware.
**EDIT** Should have looked into it more before posting, but Found my solution returning to STOCK
im having the same problem.. i rebooted using ROM MANAGER and the android with red exclamation mark appeared... when i hold de buttons, there are blue letters, but the recovery mode dont work, just the android recovery...
edgarzin said:
im having the same problem.. i rebooted using ROM MANAGER and the android with red exclamation mark appeared... when i hold de buttons, there are blue letters, but the recovery mode dont work, just the android recovery...
Click to expand...
Click to collapse
What is the baseband version on your phone?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
guitarpunk8403 said:
What is the baseband version on your phone?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
hey man.. thanks for replying, baseband is MDL.. since CWM wasnt working, i installed TWRP and it is working. It offers the same results right? Im want to flash a 4.4.2 rom...
thanks.
It should....I'm stuck on safestrap, but I always used TWRP on my S3
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Locoman_ said:
My minor issue is that when I boot to recovery (twrp) it get to the twrp splash screen then freeze. Takes me another reboot or two before recovery really launches.
Tried reinstalling recovery and fixing permission, etc.. but same deal. Anyone have thoughts on this?
Click to expand...
Click to collapse
Same with my gionne ctrl v4s lollipop stock ,when i flash cwm made by mirchifood convertor but then i flash that stock recovery it works
But i really want cwm ir twrp to installl supersu and do backups