Database Users

Help with screwed up clockwork recovery

In an effort to get back to stock I took things a step too far and now have a phone that won't power on. I had successfully rooted the phone and installed Rom Manager and flashed the clockwork recovery and immediately created a nandroid backup. Sometime later my phone started acting funny... usb connected/disconnected events when it was not plugged in, crashes, etc. I felt confident that this was a hardware issue (started after my daughter chewed on it when I wasn't looking). Anyway, I followed the instructions here in the dev forum (True Stock 2.1 firmware for vibrant) for the vibrant to get back to stock ( I apparently can't post the link because I'm new...) . So that I'd be able to try and get it replaced. I kept noticing that no matter how hard I tried clockwork was still installed... then I did the bad thing. I should have known better, but I made the rookie mistake and deleted the clockwork folder from the internal flash. I don't know what possessed me to do it, but I did. Since then the phone doesn't seem to boot. I can get it into download mode to flash images from odin (battery out, battery in, volume up + volume down, connect usb and download comes on). And after a successful download it seems to restart ok. But if it crashes (which it is now prone to do) or is powered off it won't boot after that. Worse I can't get to the stock recovery either.
I'm hoping that someone who has a nice rooted stock phone with clockwork installed can just help me get a copy of that folder back and everything will be fine... if not I may just have to see if playing dumb with tmobile will get the phone replaced as is...
Thanks in advance for any help.

Are you talking about stuff in /sdcard? If so, that won't effect the boot. You could delete everything in there and not change anything. Some apps might not work as you will have deleted their data, but if you're flashing a stock ROM with Odin, that's fine.
Enable debug mode in the settings and use "adb reboot recovery" at a command prompt. That should get you to the stock recovery. Try a factory reset from there, that might help. If not, delete anything in /sdcard that's not supposed to be there and swap with TMobile as it sounds a hardware issue at that point. Don't forget to keep your external SD card if you've replaced it.

Is USB debugging on?
When you get the phone up, can you connect to it via ADB and then adb reboot recovery or adb reboot download?

Thanks for the suggestions. I did get the sdk installed and used adb to reboot into normal recovery, so it's not completely boned. Since I could use adb for resets I went ahead and followed the rooting process again and reflashed clockwork. The phone still won't boot on it's own. I'm starting to think whatever was going south with the hardware has continued to get worse. I'm going to use odin to get back to "true stock" again and try to use adb to reboot into recovery and do a factory reset suggested above and see if that helps.
Thanks again.

I went back to stock with odin, ran the factory reset, and still can't power up normally or into recovery. I can get into download though, load with odin, come up normally after the reset. I'm going to try giving it back to Tmobile in it's refusing to power up state and see if I can get them to swap it. It's as stock as I can make it so the problem should not be mine.
Thanks again for the help.

FWIW - i just installed Rom manager this morning, the premium version, and today experienced 5 force closures, one on google maps
before this i've had maybe one FC some 2-3 weeks ago - and like you i did a clockworkrecovery backup or nandroid backup

[Q] BSOD + new computer without adb drivers = ermmm...

Ok this might seem strange, and just bare with me if I'm being thick...
I have had a nose around the forums and done a search but I couldn't find a solution to my problem.
I installed CM6 (by bumblebee) on my vega via CWM and instantly got BSOD - I didn't really think this was a problem because I knew the risk that it might happen and I had already done a backup etc.
However, all the parts for my new computer arrived the next day so I forget about my BSOD vega for a week as I started building my new computer and setting it up etc etc
I just got round to sorting my vega out when I realised I had completely wiped my old laptop with all the adb drivers on it etc (because I was going to sell it). Therefore, I cant get into recovery or flash anything to it because I cant use any adb commands :s (I cant reinstall the drivers - windows wont recognise the device as adb, only as a mobile device...).
Any suggestions? Am I being thick? Thank you for taking time to read through my rambling post anyway

You should be able to get into recovery and re-flash a stock rom. Make sure the device is plugged into the power and usb. Open device manager in win 7. Then hold down the back button for 2 secs then while still holding back hold power for 2 secs then release power but keep back button down for 2 more secs under universal serial bus controllers a new device should pop up. Point that at the usb drivers from the advent website. When the drivers have installed the screen on the vega will still be black but you should be able to flash the stock rom and start again.
Hope that helps

I will give that a try thanks for your help

Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.

willk22 said:
Ok this is strange :S
EDIT: Drivers updated! But:
It only stays in APX mode for a couple of seconds before turning itself off - I know there is enough battery because I have booted it and left it for at least 10 minutes hanging in BSOD...
EDIT2: Ok, things have got worse:
- manged to flash stock image, booted in to 1.08
- flashed clockworkmod
- got into CWM and preceded to restore
- restore froze whilst restoring dalvik cache...
- left for an hour, no change
- decided best thing to do was to turn off device and boot again
- device boots, hangs
- used adb to reboot
- now wont even get to the 'booting...' screen, adb and pc wont detec device anymore
- tried to get to apx mode, works but my pc wont detect it so cant flash stock image again...
Sounds bricked anyone got any ideas? I know it was probably a stupid idea to switch it off whilst it was restoring but it was definitely frozen.
Click to expand...
Click to collapse
Keep trying to put it into recovery mode. At times it gets picky and you have to time it just right. Took me several attempts before it worked correctly again, so keep at it
Also, be sure to keep the USB plugged in while you are attempting to get it into recovery-mode and your sound turned up so you hear the infamous hardware-connected sound. Once you hear it, immediately plug in the power and start the recovery-flash. Do not wait too long or you'll have to start from scratch again
Keep at it, you're almost there.

Got there in the end thanks for your help!

[Q] Boot-loop and now there is no IMEI and Mac is wrong

Hello,
I got a problem started this morning and keeps going ridicilously.
I'm gonna start from the begining. I plug my phone to my computer last night for charging. In the morning i took it and see that it was stuck so i unplugged the battery and try to boot it. Reboot Loop occours. It shows Ideos for 5-6 seconds and then resets. So i tried lotsa things (they are not that important at that point).
At the end i copied Estonian B138 dload folder and give a fresh install to stock rom from bootloader.
It installed very well, didnt give any errors or else. But there wasn't signal at all... I figured that there is NO IMEI number in the about page. It shows 0.
And there is a MAC address of wifi which isn't mine (Mine is 20:xx: its 46:xx i looked back side of telephone).
- I tried to install stock rom again and again. It doesnt work.
- I tried to change AMSS files (dzo's and some of my old backups) that doesnt work either.
- Tried to activate pin code and deactivate it. Only once it shows there is a simlocklock and it disappears right after. Never showed up again.
Now i can't make any calls else Emergency. What would be problem and how can i solve this?

Galaxy Tab is restarting forever (not flashed)

I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing

I'm having the same issue. It sounds like a fastboot -w is required to wipe out userdata and cache.
Unfortunately I can't seem to get my PC to recognize my tablet in fastboot mode. I might have to send my tablet back to Samsung to get reflashed.

kolor9 said:
I didnt reflash galaxy tab, was probably installing some software from the market. Now the battery has died, i restarted it and it keeps restarting after the logo... help, i dont know any recovery options :S Kies has nothing
Click to expand...
Click to collapse
That has happened to me when I was having battery issues. I was able to keep connecting and disconnecting the charger cable until I got my tab to work again.

yeah might be that as well, i noticed strange behavior for last weeks, suddenly it started draining battery very fast or shutting down in the middle of the battery. running very slow and freezing.
when connected to pc it always goes: connect/disconnect/connect/... (hearing windows sounds for that)
i fully charged that yesterday, will try to boot today.
HOWEVER i was able to get into recovery menu, wipe/delete cache, sdcard, factory reset, etc.
might be that firmware/rom/bootstrap has been fuked up when battery died suddenly?

sharing experience
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.

You may need to open up your tab and do the battery disconnect procedure. I finally had enough with my tab and opened it up. So far I am happy again.

i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again

Thanks for the suggestion but it did not work for me...I experienced same problem you mentioned below except I had gone on vacation and my tab battery died and when I was able to recharge it, it just recycles through the Samsung logo!
Tried all the suggestions on this site and no luck so far...I'm guessing it might be time to take it in to Tmobile and see what they have to say, probably not much!
I'm not ever going to get a Samsung tablet again...Asus from here on out!!!
cx5 said:
Hi guys
I didn't install new apps, no updates, no battery weak problem, no connect/disconnect problem, had DiP7's 2.3.3 rom since 10th July, very stable & solid. Not a single problem.
But my SGT GSM suddenly reboot-loop. I was just reading emails, reviewing photos.
Solutions: -
Enter recovery mode, Wipe date/Factory reset without wiping dalvik/battery stats etc. It just works and could run Titanium Backup to restore if I needed.
But ............................. Alternatives??? (New Life???): -
Tried HC_RC1, was good, but not daily driver yet, finally jumped to BOCA's 2.3.7, still playing around.
Click to expand...
Click to collapse

ceperz said:
i have some issue to
anyone can resolve it?
always reboot , and if i want to open keyboard, it restarting again
Click to expand...
Click to collapse
if its gsm go to overcome restocking method

Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium

It's been few days since ur post. But I'll give it a shot for trying to suggest.
Try holding power button for 8 seconds to properly power off. Then charge it for a good hour before starting the unit.
Else just keep charging it. Standard times are 4 hours to get zero to 100%.
Once my power used till zero and no response what so ever even after charge 5 mins. Finally let it charge 1 good hour & it came back to life.
Good luck.
Regards cx5, on the move via xda tapatalk.

fabricatedhero said:
Just go into recovery mode by holding volume down+power button.
Wipe everything then do a hard reset in recover screen.
If not do this.
Go here and download gbsafe_v5. Zip. It has everything you need including drivers and odin files
http://forum.xda-developers.com/showthread.php?t=1317384
Also download overcome-kernel_4. 0.tar file as well.
Once you downloaded these two files plug in your tab to usb and wait for that phone and pc screen or download mode screen.
Go here and follow steps up to 10.
magrathearoms.weebly.com/install.html
Your phone is now stock'ish GB with OC'ed kernel including custom clockwork recovery. This version also comes with phone capabilities unlocked so you can use it like a real phone. All you have to do is load tmobile. Modem file. If not then use as wifi only.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Dont see a thanks buttom i appreciate it MAN !!!

If it really happened after installing bad apps it will only wipe recovery mode

[Q] Soft bricked my phone, what can I do?

Hi all. Earlier I installed what I thought was a Rom suited for my device, but I believe it was the wrong rom. Now the device wont get past the splash screen, TWRP recovery is hit or miss and the only thing that opens without issue is download mode. Here is what I have already tried to do
installing stock rom via odin (application stops responding as soon as I pick the file under PDA)
install a backup (failed)
installing a new rom via recovery
fix permissions
factory reset
Is there anything else I can try? ODIN doesn't have an issue recognizing my phone, but it freezes up as soon as I try to install the stock rom. Somehow I managed to get a message in the recovery saying I don't have root (???) and when I try installing it, it reboots and get stuck at the splash screen. Also, I don't remember what it said exactly, but it was something about an md5 failure? There is an option to check md5 but it just fails. Whenever I try to install a rom via recovery it fails also. I can install kernels without a problem, however. Is there anything I can do at this point or am I out of a phone?

Be patient with ODIN, after selecting the file for the PDA slot it may seem to stop responding, just give it a minute or 2 and it should come back to life. :good:

Happens every time until it freezes up my computer or it force closes itself. pic

Drumrocker said:
Be patient with ODIN, after selecting the file for the PDA slot it may seem to stop responding, just give it a minute or 2 and it should come back to life. :good:
Click to expand...
Click to collapse
Actually you are right. It's making progress. I'l let you know what happens when its done doing its thing.

fro453 said:
Actually you are right. It's making progress. I'l let you know what happens when its done doing its thing.
Click to expand...
Click to collapse
After seeing the pic make sure only auto reboot is checked nothing else no F. Reset Time.
Sent from my SPH-L720

right after you flash with ODIN (GREEN PASS), immediately pull your battery, then pull your plug. then start up in recovery mode. sometimes the phone turns on automatically once you put the battery in but keep holding the 3 buttons until you see the blue text on the top left.

I prefer to let it do a full auto-reboot over the battery pull as previously suggested. Let it do it's full reboot before anything, then do a proper shut down, go into recovery & so on.