Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Jason Farnon said:
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Click to expand...
Click to collapse
1. you obviously flashed a kernel WITH CWM via Odin.
2. Rom Manager should not be used.
Flash a rooted stock ROM via ODIN.
read around in the stickies of the i777 forum, and get acquainted with things.
Boot into CWM correctly, and go about flashing whatever you want knowing what you just learned by reading the correct stuff.
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Actually the problem is most likely the fact that he is probably using an old version of cwm where the home button selects stuff. And rom manager.
Sent from team Pirate! Using Tapatalk 2
karate104 said:
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Click to expand...
Click to collapse
Thanks, that did it. I'd actually read the stickies, I just didn't think I could get into download mode because the phone was stuck in that auto-reboot loop.
For anyone else stuck in that loop cwm recovery loop, the download mode entry method (press both volume keys and insert usb) needs to be timed just so, since you usually perform the sequence when the phone is powered down (in stable way) but in this situation you only have a moment before it restarts. After powering down, just as it restarts automatically you can see the capacitative buttons blink for an instant, and that's when I started the sequence. Took me about half a dozen times but I eventually caught it. Am I the only one struggling with how hard these captchas are getting over the years? there's probably a sticky for that too I guess nvm.
If I'm not mistaken you can get into download mode without having a battery plugged in, so no need for trying to time it. Just hold volume buttons and plug in USB. For future reference; glad you got it worked out. Make sure to read the second guide thoroughly so you know how to safely flash stuff, and hit my thanks button if i helped you out.
Sent from my SGH-I777
Related
I followed the steps for easy rooting and finished with one click root. Phone was fine then I flashed clockwork from rom manager because I couldnt get it to go into clockwork. Now the phone is in a constant clockwork recovery. the up and down arrows work but the power button that normally works like enter just shuts the screen off and shows a rom manager logo in the middle of the screen. How do I fix? even when I pull the battery and power up it immediately goes to clockwork again.
Home button for enter on this phone.
try the home button to enter. power button does not work with our model
forgot to mention that I can get it into download mode so I tried to go back and reflash in Odin like before and start over but it failed on the initial read and I didn't want to try again
You shouldn't have used ROM Manager, it causes problems like this. If you are able to, try just reflashing the stock kernal then CWM again. Using ROM Manager messes up our phones for some reason.
Sent from my SAMSUNG-SGH-I777 using xda premium
I'm a total noob. I just assumed that the power button was enter key like my old captivate. Thank you
nossman
I had the same problem (stock on clockwork mode with Rom Manager Logo). I have read lots of posts and crossed Heimdall. When installed it I ran it and received MSVCP100.dll error. Read README file on Heimdall and installed Microsoft Visual C++ 2010 and.....that didn't help. Absolutely accidently instead of pressing PWR button in the phone to chose a command I pressed (!!!) HOME button (soft key) and IT WORKED!!! Hope it will help someone and thanks to those who contributed their time and posted various answers
This is why you read the sticky that explains not to use ROM Manager and if you read it do not ignore it. This phone is truly easy to root and flash roms on if you pay attention and don't skip info and steps.
This issue seriously comes up WAY too much.
/rant
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Dont bump old threads that were garbage to begin with... and dont use Rom Manager.
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Sparr159 said:
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Click to expand...
Click to collapse
PDS does not affect volume buttons.
And what happens when you boot? Boot loop is not very specific...
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Sparr159 said:
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Click to expand...
Click to collapse
I would tell you to flash touch recovery however I don't think you can and how it would help you recover from this situation.
Sent from my MB860 running Jokersax's CM9
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Sparr159 said:
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Click to expand...
Click to collapse
You mean 5.8.1.8? If so then yes. And if touch is not working in touch recovery then it does sorta confirm you need the PDS fix...
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Sparr159 said:
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Click to expand...
Click to collapse
Can you point me to the thread where it says volumer rocker is linked to pds because i searched and cant find it.
How are you booting...i mean with what key combination? Im assuming your booting normally(only power button) and end up going into recovery. Try booting with power button and volume down.
Sorry I'm not quoting anybody, first off.
Second, I can't find the link. I spent around an hour searching and found it through duckduckgo, but now I can't remember the search term I used. If I find it, I'll post it.
And yes, I'm booting only with power button, because the volume down key isn't working. That is where the pds problem comes in: I can't use the volume down or up key because the keys don't work.
My friend told me that I could use adb to manually boot it into fastboot mode. That works fine, but I don't know how to flash anything other than the recovery/pds partitions. I know fastboot has a "flashall" command, but I don't know how to use that or if it is even going to help. **Essentially** I can boot into fastboot mode, but I want to know if it is even possible to just flash a rom through that. Messy, of course, but if I can just get even a basic ROM working, I can go on from there.
I think you have 2 options:
1. if you can get to fastboot you can reflash everything using uncle cemka's method: http://forum.xda-developers.com/showthread.php?t=1501532
you basically take an .sbf unpack it and flash each part separately.
2. buy a atrix audio jack/camera flex cable from ebay and install it yourself, be especially careful when installing because the very small flex/ribbon that goes to your volume buttons stress fractures very easily if bent very much when installing, hence your volume buttons stop working.
I'm using cemka's method now. I'm waiting for the stock ROM to download, the one from his post. When I finish the whole process, I'll let you guys know how it worked out.
UPDATE: Thank you to whoever referred me to uncle cemka's method, I was able to use it to flash stock ROM. I have functionality back, can boot, and won't waste around $90 on a paperweight.
However, the first problem is still there: The volume keys still don't work. I still need to fix those before everything is %100 percent, so this issue is still open... Sorry guys
Hey guys,
I've been dealing with a few unrelated problems that lead to try flashing a different bootloader onto my phone. Now that I've done this, I cannot get into download mode at all. The usual button presses do nothing and I even tried the AIO Vibrant Toolbox, but selecting the option for download mode simply reboots the phone and does nothing.
At this point, I simply want to go back to stock, but I'm not sure how to do that without being able to go into download mode and using odin. I am currently able to boot up into my rom and even boot the recovery manager as well. Is there anything I can do at this point?
Just for starters, I'm sure this is silly of me to ask. But just for verification, you know that GB boot loader has a diff button combo to get to download mode right?
Press and hold volume up + power button. This would give you yellow download icon. Then you'd plug in USB cable.
Actually, it seems I asked the foolish question, as you were exactly right!
I've been mistaken about my BL for a long time it seems, I thought that the this method was the old way, not the new one.
In any case, thank you so much.
Glad I could help.
wow thank u guys, i made the same dumb mistake and was trying all these complicated forms of fixing it. Passed up simplicity.
Alright guys. I hardly post on here because I know many questions have been answered. I searched and was unlucky.
I had my phone rooted last year, but went completely back to stock because I was tired of the battery drain. Recently, maybe a month or 2 ago? I updated to 4.0.4. That's when my power button stopped working. All of a sudden, about a week after, it started working again. So I was happy. A week ago, it stopped again. Using my phone everyday, it got really frustrating. I was dumb and didn't search for a fix, which I later found a temporary fix.
So I decided to root again. Well, when I plug my phone into my laptop, it tells me "USB device not recognized" so I looked for a way to root using mobile. Found a few videos on YouTube with links with an .apk and did it that way. I had CWM backed up in Titanium Backup, so I restored it and opened it. I wanted to flash a ROM on my phone, but I didn't think before I went into CWM. Stupid, I know lol.
Now I'm stuck in CWM, without a working power button. I tried taking the battery out, and putting it back in. It still boots into CWM. I tried taking the battery out, plugging in my phone, and putting the battery back in, and still CWM. I've also tried taking the battery out and leaving it out for a while then putting it back in. And also, taking the battery out and leaving it out for a while, plugging in my phone, then putting the battery back in. Still in CWM. I've also tried hitting the Home button (does nothing). Nothing happens when I hit the Search or Back buttons either. I hit the Menu button, and it hides the menu, then I hit it again and the menu comes back.
Luckily, I'm due for an upgrade next month so recently I've been using my super old "Krzr" flip phone. I miss having a Smartphone though!
Any help would be appreciated!! Please don't flame me lol
118 views, any suggestions??
Why don't you try repairing the power key. I strongly believe It may be a hardware problem
Sent from my SGH-I777 using xda premium
If you have USB debugging enabled you could connect through ADB and force a standard restart.
If that's not an option and you can't get out of recovery (Had a very similar issue with my wife's phone when her power button went) you can use an odin 1 click downloader to revert it to stock and it will then restart normally. I then used the odin 1 click downloader to install a rooted stock rom. After that I took a touch enabled kernel (like Siyah) and installed that through Android Terminal emulator. Now you can boot into CWM and be able to use the touch screen to navigate. It's a pain and it requires a full wife and reversion to stock but it does work. Then you flash a rom that allows for holding the volume down to wake the screen or a kernel like AJK that allows for swiping across the screen to wake the phone.
I'm sure your power button failed so as the previous poster suggested you can look into getting it repaired. I don't have the link on me but there was a place listed here on the forums before that were like $40 to do the hardware replacement.
duttysrez said:
Why don't you try repairing the power key. I strongly believe It may be a hardware problem
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
KeiranSolaris said:
If you have USB debugging enabled you could connect through ADB and force a standard restart.
If that's not an option and you can't get out of recovery (Had a very similar issue with my wife's phone when her power button went) you can use an odin 1 click downloader to revert it to stock and it will then restart normally. I then used the odin 1 click downloader to install a rooted stock rom. After that I took a touch enabled kernel (like Siyah) and installed that through Android Terminal emulator. Now you can boot into CWM and be able to use the touch screen to navigate. It's a pain and it requires a full wife and reversion to stock but it does work. Then you flash a rom that allows for holding the volume down to wake the screen or a kernel like AJK that allows for swiping across the screen to wake the phone.
I'm sure your power button failed so as the previous poster suggested you can look into getting it repaired. I don't have the link on me but there was a place listed here on the forums before that were like $40 to do the hardware replacement.
Click to expand...
Click to collapse
Thanks for the info. Late last night I pressed the power button while "reboot" was highlighted in CWM and it finally worked. But it only worked that once, at least it got me out of CWM. My phone reboots a LOT. At one point, it rebooted at least 3 times in a row; getting to the AT&T screen and rebooting then.
I've decided to just deal with it lol I'm probably going to see if AT&T can kindly let me upgrade this week instead of waiting until June 1st.
Again, I appreciate the info!!
Do a clean flash
Ok since you are saying your phone's power button started being flaky after a ROM flash, I'm thinking most likely it is not a hardware issue.
Bad flashes, loading different bootloaders, or kernel flashes and then panics happen for various reasons.
You need a clean flash, reset to factory (erase data/cache multiple times) and reboot.
Back up first (like right now), then gather your operation tools.
1-Download I777 usb drivers from Samsung itself, uninstall the current ones, and install the new drivers (Do this plz)
2-Download the stock ROM from [INDEX]AT&T I777 GSll {Root/ROM's/Tools} thread by t3chn0s1s in AT&T Samsung Galaxy S II Android Development (http://forum.xda-developers.com/showthread.php?t=1301682)
3-from that thread get: A) Odin B) UCLE5 ROM
4-Run Odin and try connecting your phone to see if it stays in the Download mode successfully (phone off, Odin loaded on your PC, plug in your phone to your PC while holding down both volume keys, release the keys once your COM connection port lights up) sometime holding down the volume down only button works instead of both depending on what you flashed before.
5-load up the stock .tar UCLE5 file in the PDA section, leave all the Odin default check marks on and add the flash bootloaders check mark too(DO NOT check the repartition option)
6- once a clean flash finally happened (doesn't matter if the phones boots up all the way or not yet) pull the battery, and get to recovery and reset / factory reset and let the newly flashed ROM boot up
7-let it settle for 10-15 minutes and then reboot it.
Good luck,
I727-CM10.1
Guys,
I'm rooted, with MDK base, and THOUGHT I had a working version of CWM (maybe 6.0.2.3?)
I was in the process of getting ready to try out a new ROM; going through the usual motions, formatting system, data, cache, and for good measure, I finished with a Wipe Data/Factory Reset (which I believe just does the same things again).
The phone suddenly rebooted and froze at the samsung custom screen. When I try to get back to recovery, I can't (hold down up-vol and power; blue message appears and disappears quickly in upper left, and back to Samsung custom lock screen.
I'm stuck. In the past, I always got into recovery by rebooting with ROM Manager, so I haven't really had to use the power-on/ vol up method (thus it may never have worked).
I can get into download mode. So I'm thinking - assuming - that the first thing I should try is to Odin CWM. But I'm admittedly confused, because all of the posts that relate to installing CWM seem to be in the context of the rooting process, and assume you have the ability to place certain files in rooted directories (like loki), which I obviously can't b/c I can't boot.
1) Is re-flashing CWM the right approach ? If so, is there a .TAR file somewhere with just CWM? I can't find an Odin-flashable .tar. EDIT: I found one, but it's designated for i9505. Same thing?
2) If that's not the right approach (or I'm just an idiot and don't know how to get into a working recovery), please advise
Thanks!
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
I've found that sometimes continuing to hold the power button will cancel the call for recovery boot. Not sure why.
You can always Odin if that doesn't work.
And I don't know of an Odin package for vzw recovery.
sent from my GE gs4
Dubbsy said:
Turn the phone off.
Hold volume up and press the power button until it vibrates.
When it vibrates let go of the power and stay holding volume up until you see the recovery splash.
Click to expand...
Click to collapse
O - M - G !? Unbelievable. Thanks a BILLION! You just saved me a ton of time.
EDIT: Cr*p. Not out of the woods yet. Now, when choosing 'Install from SD Card' I'm getting 'E: Can't mount /sdcard/'
I'll post this issue in a separate Q.