Im new to the rooting scene but did my research. I did a clean install of the MOAR rom and i have been rooted and had been using teamwin recovery and it has worked fine. The moar rom is new but was working all day today till now. I used the reboot into recovery feature from the power menu and now its stuck. IT tries to boot to recovery and i see the teamwin splash page and then it fails and just flashes the splash page. I take out the battery after a couple minutes and hope to boot normally but it tries and boot to recovery straight off. I dont know what to do at this point im just hoping theres a way to fix
Fixed it. I did a little more searching and someone had a similar problem and soeone offered how to boot straight into downlaod mode which is.
1. Take the battery out of the phone and unplug it from USB power.
2. Plug in USB power.
3. While holding down the volume-down button and the Home button, insert the battery
You have to install the tar file via Odin
Related
Here's the long and short of it. This phone is a pain in the ass to get into boot recovery. I can flash it with Odin like there's no tomorrow but when I put an update.zip into the root of the phone and then try to get the boot screen using power button and volum up and down at the same time, I can litterally hold them for 10 minutes and it just keeps flashing the AT&T Worldphone screen and will not go into recovery mode. It has but it is very random. My original Captivate would boot into recovery on demand, not this one. I flashed back to stock using Odin earlier today, then I ran Designgear's SRE V1.2.1a which is amazing, it took me 1 hr to get the phone into recovery mode. Now I have put Fightspot's battery indicator in an update.zip of it in the root of the phone and it won't boot into recovery.
I am a nooob and don't know how to open an ADB shell on my computer to get it into recovery. I don't know any ADB commands. Can anyone help? Is there another way to boot into recovery.
Thanks
Rhiannon224 said:
Here's the long and short of it. This phone is a pain in the ass to get into boot recovery. I can flash it with Odin like there's no tomorrow but when I put an update.zip into the root of the phone and then try to get the boot screen using power button and volum up and down at the same time, I can litterally hold them for 10 minutes and it just keeps flashing the AT&T Worldphone screen and will not go into recovery mode. It has but it is very random. My original Captivate would boot into recovery on demand, not this one. I flashed back to stock using Odin earlier today, then I ran Designgear's SRE V1.2.1a which is amazing, it took me 1 hr to get the phone into recovery mode. Now I have put Fightspot's battery indicator in an update.zip of it in the root of the phone and it won't boot into recovery.
I am a nooob and don't know how to open an ADB shell on my computer to get it into recovery. I don't know any ADB commands. Can anyone help? Is there another way to boot into recovery.
Thanks
Click to expand...
Click to collapse
Search for Quickboot in the market...It should do what you want..
Rhiannon224 said:
Here's the long and short of it. This phone is a pain in the ass to get into boot recovery. I can flash it with Odin like there's no tomorrow but when I put an update.zip into the root of the phone and then try to get the boot screen using power button and volum up and down at the same time, I can litterally hold them for 10 minutes and it just keeps flashing the AT&T Worldphone screen and will not go into recovery mode. It has but it is very random. My original Captivate would boot into recovery on demand, not this one. I flashed back to stock using Odin earlier today, then I ran Designgear's SRE V1.2.1a which is amazing, it took me 1 hr to get the phone into recovery mode. Now I have put Fightspot's battery indicator in an update.zip of it in the root of the phone and it won't boot into recovery.
I am a nooob and don't know how to open an ADB shell on my computer to get it into recovery. I don't know any ADB commands. Can anyone help? Is there another way to boot into recovery.
Thanks
Click to expand...
Click to collapse
Just throwing it out there. Are you holding all three buttons continually? Because once the ATT screen comes up, you only need to keep holding Vol up and Vol Down.
Turn phone off
Hold Vol up + Vol down + Power
ATT screen comes up
Release power, but keep holding Vol up + vol down
Yeah I did that. It just turned on once I let go of the power button. I used Terminal Emulator and got into boot screen. Worked great. Thanks for the suggestion, this phone has only one issue and that's the issue. As long as I can use Terminal Emulator I'm fine. I have managed to get it into recovery using the buttons 3 times. Weird.
You have to hold all three buttons until the att screen goes away. Then let go of the power button.
smokestack76 said:
You have to hold all three buttons until the att screen goes away. Then let go of the power button.
Click to expand...
Click to collapse
I know. It worked fine on my first Captivate, not this one.
just turn off the power and hold both vol buttons down while pluggin in the usb on to the phone and it will do the trick
plug the phone into your computer. Download the Android SDK
Then... command window -> browse to sdk/tools directory -> adb reboot recovery.
My phone is currently sitting with a "S/W upgrade" screen after a series of stupid events. I flashed recovery using ROM Manager before I had read that it fake flashed. I rebooted into recovery and installed CM7 nightly. Rebooted and it's stuck in a boot loop. So I finally see all the warnings against that so I figure I need to get a real recovery so I use the awesome guide from TGA_Gunnman. I follow all the instructions and it appears from the log on my PC that the CM recovery flashed successfully. I pull the cord, reinsert my battery and my phone just sits in the S/W upgrade screen. It's been like that for 30 minutes now.
What do I do?
I thought I'd done something wrong with my G2x because that happened to me too. Remove your battery and USB. Then insert your battery again. When you turn it on, make sure to hold both the power button and the volume down button until you see text that says android. If you, like me, thought you just had to hold the volume down and tap the power button (like my Nexus One), that might be your issue.
Sent from my Nexus One using Tapatalk
just disconnect usb, and go to recovery Power+vol down...
.....and congrats !
yep, I thought I bricked it too.. When you were done at the green screen where it said press any button, thats where you press whatever you want and then unplug the cord. Then, put the battery back in and hold down vol then power, don't let go until "android" pops up.. You did it man, just missing your last step..
Moved to proper forum
I can get to the Recovery screen, but I cant select any of the options....volume lets me scroll, but cant find anything to select any of the options....kinda new at this
power button to 'action' your selection... at least it works for me.
usajlh said:
My phone is currently sitting with a "S/W upgrade" screen after a series of stupid events. I flashed recovery using ROM Manager before I had read that it fake flashed. I rebooted into recovery and installed CM7 nightly. Rebooted and it's stuck in a boot loop. So I finally see all the warnings against that so I figure I need to get a real recovery so I use the awesome guide from TGA_Gunnman. I follow all the instructions and it appears from the log on my PC that the CM recovery flashed successfully. I pull the cord, reinsert my battery and my phone just sits in the S/W upgrade screen. It's been like that for 30 minutes now.
What do I do?
Click to expand...
Click to collapse
The "S/W upgrade" stays on, that's normal. See if your terminal window has completed whatever stuff it is doing. If you get a completed message, you are good to go and can safely pull out the USB chord even if your phone still says "S/W upgrade". Put back your battery and hold Power+Vol DOWN button and see if you get into cmw recovery.
so im trying to fix my friends phone and this is weird..
im able to go to cwm, wipe it all and flash a new rom.. it flashess successfully but when i reboot it goes back to the s/w update screen..it happens with any rom i flash.. its been sitting there for a while.. how long should i wait?
Once you flash the ROM you shouldn't be getting that screen...Does your friend has the G2x or 2x and which ROM did you flash?
Sounds like you screwed up the boot image. Go into APX mode again and reflash the recovery package making sure it completes, you hit a key to close the terminal window, and you hold the volume buttons the entire time. Then go into recovery and factory reset and clear the Dalvik cache. Then if you still get the S/W update screen you are going to need to go to the thread about fixing bricked phones and use the KDZ method to reflash the entire GB OTA package. There is also a new method to reinstall the entire OTA package using NVFlash but you have to hold the volume buttons down for about ten to fifteen minutes while everything flashes.
Ok so, I was going to flash CM 9 v1 on my device, and when i was in clockworkmod recovery I noticed that the power button wasn't working at all.
I took out the battery and put it back and then it reboot itself and got stuck on the unlocked padlock screen.
Then i managed to boot it by pressing vol up and down at the same time and putting the battery in when plugged on the computer with the usb cable. This is the only way i can boot it. And after it runs a while it crashes and reboot into the unlocked padlock again. And this over and over.
Then I tried to go to recovery to reflash with the soft sensitive buttons and the fastboot screen doesn't do anything at all. If I press vol up or down to move around it gets stuck.
Got it to work a while and reverted back to stock rom with rom manager to see if fastboot worked again but nothing happened.
I need help to fix this.
I try to go to download mode but it doesn't work either. ADB works tho
Any suggestion??
(sorry fot the bad english)
Ok so today my triumph stopped responding so i restarted it (took out the battery). then rebooted. upon reboot phone shuts down and now will hang at the motorola logo for about 10 min before boots but will shut back down due to the battery being dead(but had full charge when this started). Dont know what happened. So i try to get into clockworkmod to flash backup. cant get into it. the only thing i can do is get to the recovery.img file(pressing power+volume down). Other than that nothing.
also tried to boot with power pluged in. it stayed on but would not respond to any touches or button press except the lock button.
I have cwm 5.0.2.6 installed and tickerguy's cm7.
never had this problem till today. Any help would be appreciated.
a new development has occurred. now when i try to access recovery, the phone will just vibrate without stopping.
and i believe its stuck in a boot loop but without recovery i dont know anyway to exit the loop.
Are you able to get into download mode (power off then simultaneously press power button & vol- (should show polling))
Sent from my Triumph using xda premium
Yes i am able to get to download mode
Well after some tinkering (replacing the recovery image, assuming something corrupted it) i can now get to recovery, still takes 10 min to load it though. But i am unable to do anything in recovery because i have to press the menu button to confirm selection but the buttons wont respond. Some help would be appreciated.
i have a Galaxy Tab 2 7.0 p3113.
i used heimdall to flash CWM into the tablet.
after what seemed like a succesful flash, my tablet rebooted. but for some reason, it would only go as far as showing the galaxy tab logo. it seems stuck there. i could not turn the unit off. i would hold the power button to force shutdown, but it always starts right back up. it seemed like i could only shut it down if it was connected to my mac while holding down the power button. i can however, boot into download mode.
after consulting google, it seems like the appropriate step was to restore the unit to stock. problem is, i can't seem to boot into recovery. i'm being told by the internet that to boot into recovery, i need to hold [power] and [volume down] until it turns on and then release [power] but keep on holding [volume down] and CWM will load. but nothing happens.
i know this is a total noob post, but i've been scouring the web for two days. i'm at my wits end. any help would be greatly appreciated.
I think recovery mode accessed via volume up+power if you could not so use download mode to flash stock or so to return to normal operation
Sent from my GT-I9100 using xda app-developers app
I press the power and UP ( button next to the power button) I normally hold BOTH buttons down at once and let the boot cycle process twice just to make sure i am going into recovery .....so i see the white samsung text twice i mean. It may take around 10 seconds to complete the process. Then release BOTH keys at once.
The battery needs a good charge for it to work.. Try charging over night before you try it via the mains supply.
Holding the power button and down will bring you into download mode and thats what you use for an odin/heimdall flash.
Hope that works for you
Let us know how you get on .....
Thanks. The battery of the gtab2 drained overnight, so i've got it charging back up now. Will definitely post my results when i have something.
Thank you guys. I'm able to boot into recovery now.
But unfortunately, i still need a little guidance on my original problem. And that problem being that my gtab2 will not startup. After rebooting, it gets stuck on the logo screen. It also plays a startup audio clip. But after that, it just displays the startup logo screen. It does not go into the animation screen and start.
I should also mention that when i plug my gtab2 into my computer, no drives show up.
My question now is, if i were to select [wipe data/factory reset] in CWM, would this restore my gtab2 to it's original factory state? Or would I need to flash a ROM for this? And if i need to flash a ROM, could i place a ROM on a microsd card and flash from there?
*********UPDATE*************
Everything is fine (so far).
I went poking around CWM and realized that I had put a cyanogenmod 9 update.zip in the root of the internal sd card before all this happened. So i went back to cyanogenmods wiki on how to install it on my gtab2 and followed the rest of the instructions on flashing it and VOILA!! I have my gtab2 back.
you should use ODIN instead CWM.
CWM is not designed specifically for Gtab2.