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?

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.

Soft Bricked wit Rom Toolbox

My wife was trying to change her font with the Rom Toolbox and it froze then boot looped. Has this happened to anyone else? Its a stock froyo with overstock and cwr. I would not go into recovery and odin would not recognize it. I finally got into recovery while trying to get into download mode for odin. In the excitement I re-flashed cm7 because it was still on her sd card. Her phone works now but I will try to get odin to work on it tomorrow. She really needs the GPS to work and cm7 just doesn't do it for her. Plus the whole thing about 911 being iffy. It's 1am here and I'm tired.

Hey man just flash a 2.2 rom like project v or bionix 1.3.1 or something.
Vibrant + ICS

It wont let me go from cm7 to bionix. i tried it.
Sent from my SGH-T959 using xda premium

Flash the JFD using odin.
Sent from my SGH-T959 using XDA App

Craven. Once you get it back to non-CM7, use this method to change your fonts. Much easier and you have total control, unlike Fontchanger which kicks me into a bootloop every single time I used it.

Trying Odin again. It doesnt seem to be working.

Odin can not see the phone. I'm downloading a different version now.

If you are not getting into download mode, try this: http://forum.xda-developers.com/showthread.php?t=1133987

i finally found a combination of cord and plug in that works. Everthing is good now and my wife is happily running deranged 9. Thanks everyone for the support. I hope you found my siries of unfortunate events as funny as i did.
Sent from my SGH-T959 using xda premium

Stuck in a bootloop

I am having bootloop problem with my galaxy note n7000
I had stock LP8 version of ICS before. I rooted it using cf-root cwm v5.5. I took a nandroid backup of my rom. And then used triangle away app to remove the triangle. It went to special boot mode and resetted my counter.
I tried formatting my phone from clockwork recovery but failed to do so as it seemed to stuck there for long. I switched it on and restarted it went into bootloop showing galaxy note again and again.
I went ahead and flashed LP8 rom via odin. It didnt seemed to help as it was stuck again in bootloop. Tried factory wipe from stock recovery and cache wipe. Still no respite.
I thought rom was buggy and went ahead and flashed gb KK1 rom via odin. But still it didnt helped and i am stuck in the bootloop.
Please help me. Also it shows custom count as 'no' and binary as
'Samsung official'. Does it means I can claim warranty?
Sorry for the long post, but it was my first post and wanted to put all details. Please help me.
Sent from my GT-I9100 using xda app-developers app

aziz981 said:
I am having bootloop problem with my galaxy note n7000
I had stock LP8 version of ICS before. I rooted it using cf-root cwm v5.5. I took a nandroid backup of my rom. And then used triangle away app to remove the triangle. It went to special boot mode and resetted my counter.
I tried formatting my phone from clockwork recovery but failed to do so as it seemed to stuck there for long. I switched it on and restarted it went into bootloop showing galaxy note again and again.
I went ahead and flashed LP8 rom via odin. It didnt seemed to help as it was stuck again in bootloop. Tried factory wipe from stock recovery and cache wipe. Still no respite.
phone now , whats showing on the screen
I thought rom was buggy and went ahead and flashed gb KK1 rom via odin. But still it didnt helped and i am stuck in the bootloop.
Please help me. Also it shows custom count as 'no' and binary as
'Samsung official'. Does it means I can claim warranty?
Sorry for the long post, but it was my first post and wanted to put all details. Please help me.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
pretty sure cf-root v5.6 has the possible fix , 5.5 doesnt , so you have more than likely bricked your phone ( did you read any of the warnings before you started flashing...there are several of them) what is the situation with your phone now , whats showing on the screen? can you go into download mode , also there is an app for checking your emmc condition see if it passes that first http://forum.xda-developers.com/showthread.php?t=1709054

Flash stock Gingerbread firmware then factory reset from recovery
DO NOT perform factory reset on stock ICS kernel or CF-Root 5.5
----
If it is not yet superbricked phone won't stuck at flashing firmware.

My phone is still able to go into stock recovery and downloading mode. And flashing via odin, it completes normally and reboots. But then bootloops. About you suggesting emmc phase check, will search abou it. Thanks for advice.
Sent from my GT-I9100 using xda app-developers app

Boy124 said:
Flash stock Gingerbread firmware then factory reset from recovery
DO NOT perform factory reset on stock ICS kernel or CF-Root 5.5
----
If it is not yet superbricked phone won't stuck at flashing firmware.
Click to expand...
Click to collapse
I think i made that mistake before. I was on ICS kernel and cwm 5.5. And i did a factory reset. I never thought it would be a problem. Should have researched more. But please help me. Is there a workaround for this?
And flashing via odin completes normally.
Sent from my GT-I9100 using xda app-developers app

aziz981 said:
My phone is still able to go into stock recovery and downloading mode. And flashing via odin, it completes normally and reboots. But then bootloops. About you suggesting emmc phase check, will search abou it. Thanks for advice.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
If flashing succeeds, then do not worry.
As I said flash stock gingerbread rom then factory reset from recovery.
And use only safe kernels on ICS.
Safe kernels:
CF-Root 5.6 Safe but do not use it to flash roms
Franco kernel R3 and above
SpeedMod kernel
Goku kernel
NoteCore Kernel
DAFUQ kernel

Boy124 said:
If flashing succeeds, then do not worry.
As I said flash stock gingerbread rom then factory reset from recovery.
And use only safe kernels on ICS.
Safe kernels:
CF-Root 5.6 Safe but do not use it to flash roms
Franco kernel R3 and above
SpeedMod kernel
Goku kernel
NoteCore Kernel
DAFUQ kernel
Click to expand...
Click to collapse
I did flash my regional stock kernel xxkk1 via odin and did factory reset too from stock recovery. But still bootloops. Do i have to flash any of the kernel above seperately? The question might seem stupid, but tell me if i got it right.. 1. Flash stock kernel 2. Factory reset 3. Flash one of the above said kernels
Sent from my GT-I9100 using xda app-developers app

Flash stock gingerbread rom with pc odin.
If it succeeds, boot into recovery (volume up + home key + power button)
then select factory reset.
then reboot.
----
The kernels I mentioned in the previous post are ICS kernels. Do not use those on gingernread.

Boy124 said:
Flash stock gingerbread rom with pc odin.
If it succeeds, boot into recovery (volume up + home key + power button)
then select factory reset.
then reboot.
----
The kernels I mentioned in the previous post are ICS kernels. Do not use those on gingernread.
Click to expand...
Click to collapse
I already did as u said word to word. I flashed stock gb rom, succeeds in flashing, wiped factory data reset goes into bootloop. The galaxy note logo keeps appearing. Not once i flashed that twice. With same steps.
Sent from my GT-I9100 using xda app-developers app

aziz981 said:
I already did as u said word to word. I flashed stock gb rom, succeeds in flashing, wiped factory data reset goes into bootloop. The galaxy note logo keeps appearing. Not once i flashed that twice. With same steps.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I am sorry. I really do not know what is wrong.
It does not sound like superbrick though.
Wait till experts help you with this problem, good luck.

I read this post http://forum.xda-developers.com/showthread.php?t=1633943
and have realized that i have bricked my phone.
Because i attempted a factory wipe on unsafe official kernel and recovery cwm 5.5.
It corrupted a drive and is hardbricked.
However is there any workaround? My recovery and downloading mode both are working.
Again summarizing
1. on official kernel rooted with cf-5.5
2. Attempted factory wipe from recovery - stuck and restarting stuck in bootloop
3. Flashed the official ics kernel again - no boot up, went to recovery wiped, still stuck at logo
4. Flashed an old gb official kernel, still stuck at logo.
Is there anything i can do? Or my SGN is as good as dead?

aziz981 said:
I read this post http://forum.xda-developers.com/showthread.php?t=1633943
and have realized that i have bricked my phone.
Because i attempted a factory wipe on unsafe official kernel and recovery cwm 5.5.
It corrupted a drive and is hardbricked.
However is there any workaround? My recovery and downloading mode both are working.
Again summarizing
1. on official kernel rooted with cf-5.5
2. Attempted factory wipe from recovery - stuck and restarting stuck in bootloop
3. Flashed the official ics kernel again - no boot up, went to recovery wiped, still stuck at logo
4. Flashed an old gb official kernel, still stuck at logo.
Is there anything i can do? Or my SGN is as good as dead?
Click to expand...
Click to collapse
There are threads on getting it working again with the use of pit files and partitioning etc but you may end up with hardly any storage left and might still not be usable.either take it in to Samsung service center or send it in and tell them you had an ota update and it never rebooted or say you did a factory reset as your phone was acting up..Don't tell them any thing about rooting or roms... it was on stock .you get me! They will change your mobo for free then mate

@denny said:
There are threads on getting it working again with the use of pit files and partitioning etc but you may end up with hardly any storage left and might still not be usable.either take it in to Samsung service center or send it in and tell them you had an ota update and it never rebooted or say you did a factory reset as your phone was acting up..Don't tell them any thing about rooting or roms... it was on stock .you get me! They will change your mobo for free then mate
Click to expand...
Click to collapse
Yes, thanks for the tip mate.
I was planning to do the same and that too today. Also the counter says no and binary as samsung official on the downloading mode. This means they can never know if it was rooted? Am i correct? Just this last question. Thanks for your replies. They were helpful..
Sent from my GT-I9100 using xda app-developers app

aziz981 said:
Yes, thanks for the tip mate.
I was planning to do the same and that too today. Also the counter says no and binary as samsung official on the downloading mode. This means they can never know if it was rooted? Am i correct? Just this last question. Thanks for your replies. They were helpful..
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
No yellow triangle, counter is zero, custom binary says NO, can't boot up => there's no way to check if it was rooted.

kopitalk said:
No yellow triangle, counter is zero, custom binary says NO, can't boot up => there's no way to check if it was rooted.
Click to expand...
Click to collapse
Yup all true. Puts asides my worries...
Sent from my GT-I9100 using xda app-developers app

I've done something similar to my note, despite flashing stock gb etc through odin (which goes through with no errors etc..) i'm still stuck at the galaxy note startup screen. If i try an ICS stock rom it'll go a little further to the samsung startup logo/jingle and then sits there.
is there nothing that can be done at this point?
my binary count is 4 now so i'm guessing i will have to pay samsung to get it resolved if it is indeed bricked, does anyone know who much this is likely to cost?
also, is there a way of determining for sure if my phone is bricked/caught he emmc bug?.
thanks all in advance, i spent hours and hours trying to get my phone back so i'm pretty deperate now.

aziz981 said:
Yup all true. Puts asides my worries...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
that what happen to my note as well .... i did not read carefully and preform the full wipe and superbrick my note and use the same excuse saying OTA update to 4.0 and after it reboot i got my phone brick
samsung refuse to give me warranty on it as in my recovery screen i have a something like a "phone . . yellow exclamation . . monitor" and stated firmware upgrade encountered an issue. please select recover mode in kies & try again "

You had a binary counter and the custom firmware yellow triangle it seems :-(. That explains it, it is an indicator that you flashed unofficial firmware to your phone and voided the warranty
Sent from my GT-N7000 using Xparent ICS Tapatalk 2

Markuzy said:
You had a binary counter and the custom firmware yellow triangle it seems :-(. That explains it, it is an indicator that you flashed unofficial firmware to your phone and voided the warranty
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
in download mode ... my binary counter is zero and no yellow triangle ...

Russc73 said:
I've done something similar to my note, despite flashing stock gb etc through odin (which goes through with no errors etc..) i'm still stuck at the galaxy note startup screen. If i try an ICS stock rom it'll go a little further to the samsung startup logo/jingle and then sits there.
is there nothing that can be done at this point?
my binary count is 4 now so i'm guessing i will have to pay samsung to get it resolved if it is indeed bricked, does anyone know who much this is likely to cost?
also, is there a way of determining for sure if my phone is bricked/caught he emmc bug?.
thanks all in advance, i spent hours and hours trying to get my phone back so i'm pretty deperate now.
Click to expand...
Click to collapse
Ur note is pretty much hosed. U had the exact same issue that i had. But samsung replaced my motherboard for free as counter was zero. Now they can replace the mobo.. and the associted cost with it.
Are u sure it is hardbricked, have u tried jtag usb jig to recover it back? It may not work..but worth a try
Sent from my GT-I9100 using xda app-developers app

And the third Lil piggys house was made of BRICKS!!

Can anyone explain to me why everytime I do a factory reset/ wipe of my device (vibrant 3g).. and I reboot, it gets stuck on the Samsung vibrant screen, can't get into cwm with buttons or stock recovery, and have to Odin myself out of brick mode..
Also.. I realized that I don't have the stock navigation on my phone and Google maps takes foreverrrrrrrr to lock on..in fact it hasn't locked on once since I had the phone.
Rooted, and CWM on 2.1 eclair stock.
TIA
Sent from my SGH-T959 using xda app-developers app

lsmrfydgaf said:
Can anyone explain to me why everytime I do a factory reset/ wipe of my device (vibrant 3g).. and I reboot, it gets stuck on the Samsung vibrant screen, can't get into cwm with buttons or stock recovery, and have to Odin myself out of brick mode..
Also.. I realized that I don't have the stock navigation on my phone and Google maps takes foreverrrrrrrr to lock on..in fact it hasn't locked on once since I had the phone.
Rooted, and CWM on 2.1 eclair stock.
TIA
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
I don't know why it would brick. Are you factory resetting from cwm or while the phone is on under settings. Also the vibrant has extremely crappy GPS. The newer ROMs have files that help it lock on better but the vibrant just still has crappy gpd
Sent from my SGH-T959 using xda app-developers app

When I bought the phone (used for 50 buxx) guy I bought it from said he did a fact data wipe while phone was on under settings.. the phone was on the vibrant screen when he handed it to me. After he left, still stuck on vibrant screen. I decided after realizing phone was bricked that I would Odin myself out...which I did, then rooted and flashed cwm. Tried flashing a custom rom so I data wiped and restored from cwm before installing rom. After rom loaded bam stuck on vibrant again.. even after reflashing rom twice. Odin'd out again :/
Now I reluctantly tried again with cm7 but decided I would try just wiping cache/dalvik from cwm and BAM! bootlooped at cyan7 screen, reflashed cm7 and wazambamboozle! Now running cm7 flawlessly.
Sent from my SGH-T959 using xda app-developers app

To tell you the truth I have no idea why its doing that. But if you want a clean flash every time you could just Odin back then wipe dalvik and cache then just flash over it
Sent from my SGH-T959 using xda app-developers app

Yea idk why either all I know is so far so good on cm7.. just gonna leave it alone lol
sent from my t959 on cm7 and a cracked screen