Database Info

Is it Bricked?

Well i was just out and about running CM7 RC2, CWM 3.0.6 and i went to pull my phone out and it wouldn't boot. went into clock work and got errors
somthing like "error can't open recovery log" or somthing along those lines tryed restoring a backup. flashed a new ROM and the install fails.
I did the PD105IMG thing and i get Fail-pu on all of then besides TP witch says Bypass, Radio_v2 gets stuck on updating...
Any help?

OShocke said:
Well i was just out and about running CM7 RC2, CWM 3.0.6 and i went to pull my phone out and it wouldn't boot. went into clock work and got errors
somthing like "error can't open recovery log" or somthing along those lines tryed restoring a backup. flashed a new ROM and the install fails.
I did the PD105IMG thing and i get Fail-pu on all of then besides TP witch says Bypass, Radio_v2 gets stuck on updating...
Any help?
Click to expand...
Click to collapse
Fail-PU means failed partition update. Now depending on the severity it can mean soft brick as I myself reverted back from failed pu few days ago.
Now lets work on your problem since you still have samething as PD15IMG didn't go though. What were you doing before you got error on recovery?

XDA-WTF said:
Fail-PU means failed partition update. Now depending on the severity it can mean soft brick as I myself reverted back from failed pu few days ago.
Now lets work on your problem since you still have samething as PD15IMG didn't go though. What were you doing before you got error on recovery?
Click to expand...
Click to collapse
Nothing... It was just in my pocket. and it started boot looping

So you just flashed CM7RC2 using CWMR3.0.0.6 and it was working fine? Then you pulled it out and saw it dead? So you turned it back on and from then on it stuck at the bootloop?

XDA-WTF said:
So you just flashed CM7RC2 using CWMR3.0.0.6 and it was working fine? Then you pulled it out and saw it dead? So you turned it back on and from then on it stuck at the bootloop?
Click to expand...
Click to collapse
Yes sir.. Got stuck at eh CM screen.. Went into clockwork and i get these errors at the bottom of the screen.
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log

OShocke said:
Yes sir.. Got stuck at eh CM screen.. Went into clockwork and i get these errors at the bottom of the screen.
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Now did you see this errors before you try to roll PD15IMG? or did you see after? This is very important as if you enabled security while trying to revert back. Check your hboot and tell me if you see S=OFF/S=ON? Based on that we can proceed. It took me 2days to work though issue before I could get my device to work from fail-pu.

XDA-WTF said:
Now did you see this errors before you try to roll PD15IMG? or did you see after? This is very important as if you enabled security while trying to revert back. Check your hboot and tell me if you see S=OFF/S=ON? Based on that we can proceed. It took me 2days to work though issue before I could get my device to work from fail-pu.
Click to expand...
Click to collapse
It was before and after.
and yes i'm rooted so its S=OFF

[Q] CM7 to Mezmerize Stock issues

So I flashed CM7 to my phone a while back. It worked. Fantastic.
There were some drawbacks to having a pre-nightly rom so I wanted out. I looked at the dev forums and saw the instructions to flash the full stock rom to the phone. A genuine factory reset. I followed the instructions, hoping it would work (and before anyone asks, yes, I did turn off the lagfix in voodoo).
Odin continually fails to flash the stock rom onto my phone and now I can only get to the bootloader on my phone. I can't mount USB storage, I can't get anything onto my phone to flash with CWM, and I now have a phone I cannot use until I get this fixed.
Obviously I did something wrong, but I'm having trouble retracing my steps to find out what that wrong move was. If anyone knows what I did wrong just by reading this, awesome, please help me out.
Also, when I try to mount usb storage from CWM, I get an error saying
E:Unable to open ums lunfile (No such file or directory)
Click to expand...
Click to collapse
and on loading the bootloader I get
ClockworkMod Recovery v4.0.1.0
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse

Don't know if you're still having an issue, but flash ec10 or ee19 through Odin, and make sure to check re-partition. You can either stay there or go to the gingerbread based EH09, which is the official firmware. Before you flash that in Odin, uncheck re-partition. It might say that it failed. If it does, disconnect the phone, put the battery back in and power it up. If it works, and it should, you're golden. Hope this helped
Sent from my SCH-I500 using XDA App

I had the same scenario w/ my Showcase. I did everything "correctly", and I never could get GB to load back on there after loading CM7.1. I tried multiple versions of 2.2 through Odin, I constantly got FC's. Then I tried reloading GB, I got stuck in boot loop. I had to send it in to Samsung... under warranty.

[Q] Infuse Stuck in Boot Loop & Can't Flash

Okay so I really need some help. I was installing CWM 10 and decided to try another one when the home key didn't work, and tried to go with Slim Bean. The phone has been stuck in boot loop ever since. I can however get into recovery but no luck there. None of the backup zips will flash and I am in CWM 5.0.2.7. I normally will just flash back to stock in an instance like this but now Odin wont even come up with a COM when i plug it in. I also have tried Heimdall to no avail. All it says under Recovery is
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/reovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any ideas, I am willing to try anything

cwm 5.x is CM9.
CM10/JB has cmw 6.x
it's hard to tell how you got from jb cmw 6 to ics cmw 5 .
it's possible your partitions are also messed up.
you may need to start over with a return to stock package via Odin or Heimdall.

qkster said:
cwm 5.x is CM9.
CM10/JB has cmw 6.x
it's hard to tell how you got from jb cmw 6 to ics cmw 5 .
it's possible your partitions are also messed up.
you may need to start over with a return to stock package via Odin or Heimdall.
Click to expand...
Click to collapse
I read somewhere about trying a jig since I can't get into download mode, I just ordered one online, hopefully that will help me to return to stock. Thank you!

valcat22 said:
I read somewhere about trying a jig since I can't get into download mode, I just ordered one online, hopefully that will help me to return to stock. Thank you!
Click to expand...
Click to collapse
np..if you are stuck in a constant samsung boot loop and cant get into download mode, it may be your power button.
look in the q/a threads if you think it may be your pwer button.
without power button issue, you should be able to get to DL mode..

getting
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/reovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
though i can get back to stock via odin to 2.3 and it boots fine.
really confused ????

HELP!! Half-Bricked Phone

I did something stupid and installed rom manager, it corrupted my recovery. I restored to stock rom i found online using odin but it says you need to wipe factory settings to make it boot. The recovery is now the stock one but it displays error messages and when I choosed a command it does nothing. What should I do?
EDIT: I flashed another stock rom this time i could boot into the phone. Some of my apps went missing and superuser went missing. It was a little weird. The recovery still shows errors and no command. It says
"can't access to '/system/csc/VAU/system". I don't think I can root it again and install a custom rom. I dont know what is the right thing to do now. I just want to root it and install a rom
EDIT2: I installed another recovery called Amon-RA recovery and I still get errors. I am thinking maybe the recovery partition is corrupted. I get these errors.
E: Can't mount CACHE:recovery/command
E: Can't mount /dev/block/stl14
(invalid argument)
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
E: Can't mount /dev/block/stl14
(invalid argument)

turntaker said:
I did something stupid and installed rom manager, it corrupted my recovery. I restored to stock rom i found online using odin but it says you need to wipe factory settings to make it boot. The recovery is now the stock one but it displays error messages and when I choosed a command it does nothing. What should I do?
EDIT: I flashed another stock rom this time i could boot into the phone. Some of my apps went missing and superuser went missing. It was a little weird. The recovery still shows errors and no command. It says
"can't access to '/system/csc/VAU/system". I don't think I can root it again and install a custom rom. I dont know what is the right thing to do now. I just want to root it and install a rom
EDIT2: I installed another recovery called Amon-RA recovery and I still get errors. I am thinking maybe the recovery partition is corrupted. I get these errors.
could you please download below files and install with odin.also you need samsung usb driver
S5670XWKTI_S5670DBTKT1_DBT
Odin_GT-S5670 (odin 4.38)
Click to expand...
Click to collapse

I downloaded it and flashed it..AND I REALIZED THAT I WAS STUPID....
YOU DONT PRESS THE POWER BUTTON TO SELECT YOU PRESS HOME BUTTON.... LOL

[Q] N8010 Stuck on Boot. Problem with Recovery

Hi guys, I really hope u can help me, cause i admit i did my share of research and got no solution
My N8010 was using GNABO 6.5 and Boeffla Kernel. While using it the other morning, the tablet suddenly rebooted and got stuck on the Galaxy Note screen. It stays on it a few seconds then reboot to the same screen in a loop.
I can access the recovery menu (CWM 6.0.3.6 ) but my options there are pretty limited, cant wipe and cant install zip files. At the botton of the recovery i have the following logs:
Warning: no file_contexts
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/log
E: Can´t open /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
I read somewhere that the problem should be solved if i could install a new recovery through Fastboot. Problem is fastboot cant find my device when on bootloader (but i can find it through ADB).
Using ADB sideload to install new recovery or new ROM gave me error on CWM.
Please, save my Tabye. :crying: