Database Users

Can not restore my phone

I want to preface this by saying I have spent 4 hours trying to recover my phone and I have tried all the things suggested in the treads, including what worked for me last time.
I installed a kernal for using the buttons backlighting for notifications which apparently works on the Fascinate. My phone never rebooted from that. I tried to install Clockwork and install an update.zip or an old restore file and it would not read off my SD properly/was not effective. I then tried using Odin to flash over the system, kernal, and recovery. Still no dice. I formatted my sd and tried to install clockwork again and everytime I try to access it through installing update.zip it says that signature verification failed and the installation is aborted and does not even reach clockwork.
I hope someone can help me. I have tried everything I can think of and have had zero luck.
PS: Currently my phone will show SAMSUNG but keep looping

Did you have voodoo on your phone before you flashed the kernel?
Sent from my SCH-I500 using XDA App

ktez said:
Did you have voodoo on your phone before you flashed the kernel?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
No, I was running a deoxed .4 rom

Are you installing clockwork through Odin? I have had problems with getting clockwork to work if I installed it any other way. It should work through Odin tho - also was the kernel you flashed with the backlight notification the voodoo one or non-voodoo?
Sent from my SCH-I500 using XDA App

Also did you try wiping data? Even if you can't get into clockwork you can do it from the Samsung recovery. I would try that and then do all the Odin recovery stuff again and see if that helps - but if you flashed the voodoo kernel you will have to go thru the post on completely removing voodoo.
Sent from my SCH-I500 using XDA App

ktez said:
Are you installing clockwork through Odin? I have had problems with getting clockwork to work if I installed it any other way. It should work through Odin tho - also was the kernel you flashed with the backlight notification the voodoo one or non-voodoo?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I am installing through Odin. I don't know any other way to do it. I installed the non-voodoo one.
I installed this one since I heard it worked on our phone as well...
forumDOTxda-developersDOTcom/showthreadDOTphp?t=772672
"i9000_BacklightNotification_v1.6.zip"

ktez said:
Also did you try wiping data? Even if you can't get into clockwork you can do it from the Samsung recovery. I would try that and then do all the Odin recovery stuff again and see if that helps - but if you flashed the voodoo kernel you will have to go thru the post on completely removing voodoo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I have wiped every data thing you can think of several times. And do you think it would hurt for me to try to remove voodoo even if I don't think I flashed that kernal

I'm hoping someone more experienced than me will take this one - I'm not sure if that backlight notification you flashed is compatible with the fascinate. That could be your problem. Can anybody else jump in here?
Sent from my SCH-I500 using XDA App

You flashed a i9000 kernel onto your Fascinate. Ay caramba.
DON'T FLASH NON-FASCINATE ROMS ONTO YOUR FASCINATE
Anyway, I can't think of anything except trying to flash the Fascinate CWM kernel back onto your phone again with Odin.
edit -- FYI, the only BLN kernels any Fascinate owner should be flashing are the ones from jt1134, available only via ROM Manager

s44 said:
You flashed a i9000 kernel onto your Fascinate. Ay caramba.
DON'T FLASH NON-FASCINATE ROMS ONTO YOUR FASCINATE
Anyway, I can't think of anything except trying to flash the Fascinate CWM kernel back onto your phone again with Odin.
edit -- FYI, the only BLN kernels any Fascinate owner should be flashing are the ones from jt1134, available only via ROM Manager
Click to expand...
Click to collapse
Figured as much... I read it worked and that is why I installed. Hopefully I can get a fix. Maybe I should do adb?

Wifi stuck in an Infinite loop

So i went from Syndicate rom on EB13 and flashed over it with the new Frankenstein rom, when i got the rom working my wifi stopped working. Figureing this was just an issue with the rom its self i flashed the whole phone back to EB13 Stock. This didnt work so i re-flashed all the way back to DG27 using odin and my Wifi still isn't connecting to my network. It will see the network, then it will just hang saying Obtaining address. Some times it will get past obtaining adress and it will stop working by just saying out of range. I dont know what else to do. Anyone know what i should do?? I refuse to believe this is a hardware problem due to how fast it was messed up after tinkering with the software. Is there anything i can do to completely reset everything on the phone?

did u flash with odin? Did u wipe cache/data/delvick between each flash? I had this happen to my phone. I reinstalled original os (di18) with odin and it worked fine.
Sent from my SPH-D700 using XDA Premium App

I always Wipe everything before i flash anything onto my phone so yes...
I guess i could try takinng it all the way back to di18 rather than DG27

I figured just didn't want to assume. Try flashing back to original os with odin. Outside of that idk what else to tell ya. Good luck. If I come across anything I will pass it on to ya.
Sent from my SPH-D700 using XDA Premium App

Can't use SMS all of a sudden

My wife received a text this morning and then her phone froze. I pulled the battery and rebooted. When I open handcent (and the stock SMS app) I get a popup error that flashes for half a second then disappears and the app doesn't run. Any suggestions?

un-install handscent, reboot, retry ?

daddymikey1975 said:
un-install handscent, reboot, retry ?
Click to expand...
Click to collapse
I have several times and still nothing.

Which ROM is she using, out of curiosity?

Syndicate Rom Frozen 1.1.0 with Twilight Zone Kernel. I am using the same Rom and I don't have any issues. She has been running this Rom for a couple weeks now.

I had the same problem after using wireless tether. Wiping and reflashing was the only way i got it to work
Sent from my SPH-D700 using XDA Premium App

_-Jay-_ said:
Syndicate Rom Frozen 1.1.0 with Twilight Zone Kernel. I am using the same Rom and I don't have any issues. She has been running this Rom for a couple weeks now.
Click to expand...
Click to collapse
lots of members have had problems w/ SRF 1.1.0 and lots of members have had good luck.
Seems as if it plays nice w/ some devices and not others.
Time for a different ROM ? wipe data and reset ?

I wiped data and reflashed the Rom. Seems to have worked. Thanks for the help.

After u get ur apps reinstalled and everything back in place id do a backup just in case it happens again
Sent from my SPH-D700 using XDA Premium App

You have corrupted your data. The ROM has journaling off, so as soon as you pull your battery anything that isn't saved will be lost/corrupted

Not so random reboots

I updated to EI22, stock w/OTA update. I then rooted and things were working great. Then about 1 week ago, I did a CWM backup and when I restarted the phone just kept automatically rebooting approx. every 3 -4 minutes. I could not stop it no matter what I did. Then I restored the backup and it worked fine. A few days later, I turned the power off to put in a my extra battery, and when I turned it on, the same thing happened. I had to restore twice fir it to stop this time. Then this morning, I did a reboot to see what would happen, and again it happened. Mind you it was working flawless before I restarted it. I have tried everything from removing programs, turning off the wifi, leaving the battery out for a half hour, but nothing. Sometimes after it reboots, I leave it alone for 15 minutes and then when I hit the power button, it just restarts.
Any ideas before I put back froyo??

Sounds like a bad flash. I would Odin all the way to Stock EC05 then root then flash a Gingerbread ROM. Your error is either in the kernel or recovery to happen immediately after boot. It could even be a flaky partition table.
Sent from my SPH-D700 using XDA App

OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.

mszach said:
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
Click to expand...
Click to collapse
I figured that but the problem may lie in the rooting which required you to flash a kernel or in your recovery module.
Sent from my SPH-D700 using XDA App

mszach said:
Any ideas before I put back froyo??
Click to expand...
Click to collapse
Your not alone on this issue. I am also considering going back to froyo
ADW was nice enough to bring up a crash report that I emailed myself. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's happening.

See also this related post

So I flashed to the ACS ICS rom and so far no problems. What a great ROM!! Many thanks to Marcusant and ACS.
Sent from my SPH-D700 using XDA App

don't use the OTA.
just root ec05, flash CWM 5, flash modem update ec05 to EI22, flash a rom of your choosing. it's that simple. i don't see why people go the OTA route. it just causes problems with the recovery.
EDIT: also if you want Rom manager, check the kernel(or rom) for compatibility.

Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium

robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm lazy sometimes and like to use a GUI...
Sent from my SPH-D700 using XDA App

robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
It was not supported for the Epic before but with the new CWM5 it is. It is much faster to boot into recovery from ROM Manager rather than powering down and 3 fingering into it. Plus ROM Manager supports renaming your backups when you are doing them. Also ROM Manager will continuously update your CWM if new versions come out. There is also OTA updates available if the developer supports it on their ROM.

did something dumb. help?

I had encounter ICS, which was great, but isn't ready to be a daily rom, so I use koush's app to reboot into recovery.
then I got stuck at the boot animation, so I decided to open up the stock recovery, and wiped data/factory reset like an idiot. So now all i have is stuck at the M logo, or stock recovery.
Am I going to have to use an official update.zip to flash, then root my phone again?

You are going to have to sbf.
Sent from my DROID2 using xda premium

okay, so I sbf'd back to stock froyo (only GB sbf I can find around the net is a megaupload link, which is obviously not very helpful nowadays) and let it do an OTA update to GB.
I then root, just like i have before, using the motorola one click root program on my computer.
I get root, install koush's bootstrap, and reboot into recovery. I then try to install libertyv3 2.0, which seems to go well...
until i reboot. once i reboot my phone, I'm stuck back at the bootloader, and can't do anything except SBF all over again.
seriously, what's going on? maybe this liberty .zip is broken or something? (i had to find a mirror, because A team gummy's site seems to be down, and B the only other official mirror is megaupload)
I'm going to try another rom, probably encounter ICS because i already have it on my SD card.

this time, I actually read the instructions and tried to install Liberty with clockwork recovery instead of koush.
still. effing. happening.
I reboot after flashing the zip and I can't get past the bootloader screen.
Code:
Bootloader
D2.37
Err:A5,69,35,00,23
Battery OK
OK to Program
Connect USB
Data Cable
I'm seriously at wit's end here. I just got this phone but a couple days ago after I lost my original. it's an insurance replacement. I rooted with the moto one click root, and used koush to install encounter ICS. after not knowing about encounter's wonky way of activation the custom bootloader, I mistakenly wiped the phone with the stock bootloader. I SBf'd back to stock froyo, then OTA updated to gingerbread.
That is my entire history with this phone. what the hell could possibly be wrong with it?

Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium

Albinoman said:
Do you wipe data/cache/dalvic once before you flash and twice after? Liberty is dead use ICS.
Sent from my DROID2 ICS using xda premium
Click to expand...
Click to collapse
I did certainly wipe before flashing, but have never not once heard of wiping twice after flashing. wouldn't that undo the flash? what's the point of that? And like I said, I would use encounter ICS, but it's nowhere near stable enough for daily use.

When you wipe after its just to make sure everything is stock. As long as you don't wipe /system the rom will still be there. Actually if you can live without a camera EncounterICS is an amazing daily driver. Also never use bootstrap unless you're on stock gb.
Sent from my DROID2 ICS using xda premium

I can live without a camera, but google music barely works, which is something I can't live without. I'm thinking about going back to Apex until encounter gets really good (had apex for months up until i lost my original phone)

Google music is working fine for me. Good idea apex is great.
Sent from my DROID2 using xda premium