I recently installed a gingerbread rom Lidroid. it was working ok till i realized i could not stand some bugs. I decided to try cyanogen that was released today. It looked like it installed fine but the phone is stuck trying to install clockwork recovey. it keeps going on and looping at the same screen. the last message it shows before it reboots off is "Replacing stock recovery with Clockworkmod" it just keeps looping doing the same thing. I have tried to get into download mode without success. I have been able to put my phone in download mode the past couple times i have run into trouble. Now i simply cant be able to do it. Any help?
I dont know how it happened but after trying for the past 5 hours, i have been able to get it to work. I took the battery out inserted it back in. I held the volume down button and the power button together. i immediately plugged the phone into USB cable while still holding Vol down and power button. After 10-15 seconds, it brought up the clockworkrecovery. I Wiped everything and the cache. I then tried to reinstall cyanogen(the one that brought all this in the first place) because it was the only one on my sd card. It installed and booted up and now i have CM 7. I can also successfully get into Download Mode
Am not sure what i did, but if anyone can run into such a problem you might try this.
Related
I recently installed JAC's kernel, and today I was getting force closes on nearly all of my apps. Even market would FC. So I did a nandroid (the nandroid was with the stock kernel), and now the phone won't boot past the Vibrant Samsung screen. Recovery menu works however. I'm guessing the issue is that I shouldn't have flashed a nandroid that was non-JAC kernel.
I have absolutely no idea what to do in this situation. Can anyone help? I really appreciate it, thanks.
UPDATE:
I flashed the Official T-Mo ODIN images, and got the phone working again. I'm not sure if there was some other way without wiping the phone, but this way worked.
I did a nandroid recovery last night of my stock image and it took about 5 minutes to get past the Vibrant Samsung screen, but it ultimately made it past it.
Hm, I must have been not paitient enough. I didn't count but it felt like I waited 4-5 minutes.
I can NOT get past this screen or into download or recovery mode... All I get is a spinning wheel... tried to downgrade from CM7.... I tried everything Ive read to try to get into download mode...any ideas?
l0stcaus3 said:
I can NOT get past this screen or into download or recovery mode... All I get is a spinning wheel... tried to downgrade from CM7.... I tried everything Ive read to try to get into download mode...any ideas?
Click to expand...
Click to collapse
I was finally able to get into download mode..... I spent hours getting my google on reading all the different was to get into download mode...Now my phone would not boot past the "Samsung Vibrant" screen and all the different button combos wouldnt work... Here is what what worked for me..
1 I ungluged the phone from the laptop and removed the battery to make sure the phone was off...
2 I held down BOTH vol+ AND vol-
3 While holding down BOTH vol keys I plugged in the USB and BAMM!!!!!! download mode.....
I hope this helps someone.....
didnt think nandroid backed up the kernel
so doing nandroid to get back to the kernel you were on before wouldnt have done anything
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Hi
I used the factory reset function on my tab a couple days ago to delete all apps and such and upon reboot it was stuck at the slowly flashing Samsung logo and would proceed no further. I left it for a good hour and a half in that state before I tried hard resetting it but no dice. I've had it do this before when I first rooted it, but unlike that time it doesn't replay the whole boot animation, just the logo part at the end of the animation. I managed to get it in clockwork mod or bootloader whatever that function is and cleared all the caches and did a reboot recovery (i believe thats what it was called) but upon reboot it did the same exact thing. So after that I gave up and went to bed, but the next day when I went back at it again it wouldn't even turn on. After messing around with the power button and volume button trying to get into recovery mode it finally turned on but went to the battery screen with no other actions. I've tried several times to get it into recovery mode but it either wont turn on or it just goes to the battery screen. I have it plugged into my pc at the moment and apparently it is in recovery mode or something because Odin recognizes it. Says [0:COM3] and the box is yellow, but the screen never turns on though when holding the power button and volume button while it's plugged into a pc, the pc recognizes something plugged into the USB slot. My pc is only recognizing it as a modem and will do nothing else with it.
I have the Starburst rom and the overclocked kernel installed and would like to either revert it to stock rom or perhaps the AOKP rom, milestone 6. Is there any way to do this if I can't boot it into a state where I can access the SD card on my pc? All the guides I've found always require I put files on the sd card to flash in clockwork recovery mod. Thanks for any assistance
Edit: Solved it myself, feel free to delete this post. Thanks!
I went from Shostock2 ICS to Shostock Gingerbread--flashed through recovery, everything seemed fine, rebooted a couple of hours later and the phone froze at the "Samsung Galaxy S II" screen. As of now I have NOT been able to get back into recovery though the volume rocker/power method ... Nothing happens at all. Half the time my phone wont boot, period, but if I pull the battery and put it back it will boot the first time into that same screen. Not at home so I can't connect it to my computer but if I can't boot into recovery not sure how I'm going to get my PC to recognize the phone .... (sigh.)
Please advise.
EDIT: Finally managed to get into recovery via volume rocker ... Don't know why it worked this time after failing over and over before. Have reflashed the Gingerbread zip ... Keeping my fingers crossed that it works out.
Haints said:
I went from Shostock2 ICS to Shostock Gingerbread--flashed through recovery, everything seemed fine, rebooted a couple of hours later and the phone froze at the "Samsung Galaxy S II" screen. As of now I have NOT been able to get back into recovery though the volume rocker/power method ... Nothing happens at all. Half the time my phone wont boot, period, but if I pull the battery and put it back it will boot the first time into that same screen. Not at home so I can't connect it to my computer but if I can't boot into recovery not sure how I'm going to get my PC to recognize the phone .... (sigh.)
Please advise.
EDIT: Finally managed to get into recovery via volume rocker ... Don't know why it worked this time after failing over and over before. Have reflashed the Gingerbread zip ... Keeping my fingers crossed that it works out.
Click to expand...
Click to collapse
Boot into recovery and wipe data/factory reset, that should get it to boot after you flash the GB zip!
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
moraha1287 said:
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
Click to expand...
Click to collapse
Seems like your hardware button could be broken, I would all do in this order:
Download Philz Touch Recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
Official Firmware from here: http://www.sammobile.com/firmwares/3/?download=28378
Flash Philz touch through Odin
Reboot to Recovery, selct "Clean to install a new rom"
Wipe cache and dalvik cache
Go to downoad mode and flash the md5.tar file through odin