Okay, so here's the deal -
The phone was previously running stock rooted 2.2. I backed up the stock kernel, then used SGS Kernel Flasher to flash the Voodoo kernel. I decided to go back to the backed up stock kernel and used SGS Kernel Flasher to do that, and that's where everything went to hell. Now the phone will go through the T-Mobile and Galaxy S boot animations, but after that finishes, it'll just move straight to a black screen. The capacitive buttons light up and respond to the touch, but other than that, nothing happens.
I'm still able to get the phone into both download mode and the stock 3e recovery. However, when I boot into 3e recovery, I get a bunch of errors that say the following:
-- movi_checking done! . . .
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:recovery/command
update media, please wait
E:Can't mount /dev/block/stl10
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
copy default media content failed.
E:Can't mount /dev/block/stl11
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(Invalid argument)
I've tried to used Odin to re-flash the stock firmware several times using several different methods, (this included), but Odin almost immediately gives me a big giant FAIL! every time I try. I've also tried it with the re-partition button checked, and when I do that it seems to start working, but then gets stuck on set-partition.
So, any ideas? Thanks in advance.
TL;DR: Phone goes through usual boot animations, then gets stuck at black screen but capacitive buttons light up and respond to touch. Using Odin to reflash stock firmware not working. Plz halp.
Okay, well, just in case anyone happens to find themselves in the same position I was in, here's how I fixed it:
Opened up Odin, and tried to reflash the Voodoo kernel. It failed and sent me to that pc ! phone screen. Kept Odin open and just hit start again and it went through. Got a voice that said something about insufficient internal storage I think? Then the phone just booted up and all is back to normal.
Next time disable voodoo lagfix from recovery before going back to stock kernel.
Sent from my SGH-T959 using Tapatalk 2
Alex9090 said:
Next time disable voodoo lagfix from recovery before going back to stock kernel.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, I realized that was the problem after.
Question - so now the phone still has voodoo lagfix, but it's back on the stock recovery. Is there any way to get Clockwork back? I already tried reflashing the Voodoo kernel, but for whatever reason, it didn't flash CWM with it.
What do you mean it still has voodoo? Check what kernel version you have on your phone by going into settings. If you have stock recovery then most likely your using stock kernel now. You might be talking about voodoo folder on your sdcard, well it stays there until you delete it.
I'm 90% certain I still have Voodoo lagfix enabled because the last thing I flashed before it started working again was this kernel in Odin. But, like I said, it didn't flash CWM with it for whatever reason. I haven't flashed anything since.
In the settings menu, it says 2.6.32.9 under Kernel version. The phone's running the stock KA6 build at the moment.
Thanks for the help, by the way.
Okay, so I managed to get Red CWM back. I used Voodoo Toggle Reboot to disable it, reflashed the Voodoo kernel, and it put Red CWM back on there.
So, now I guess my only question is, can I use Red CWM to flash other roms? I'll make sure to disable Voodoo Lagfix before I do this time.
Computar said:
Okay, so I managed to get Red CWM back. I used Voodoo Toggle Reboot to disable it, reflashed the Voodoo kernel, and it put Red CWM back on there.
So, now I guess my only question is, can I use Red CWM to flash other roms? I'll make sure to disable Voodoo Lagfix before I do this time.
Click to expand...
Click to collapse
Yes, you can. Make sure when you disable voodoo, let the phone reboot so it can convert the partition back to rfs.
Got everything up and running and put CM7 RC2 on there. Thanks!
Related
So just when i think my phone is inbrickable and i have flashed like 7 roms. All types of kernels and im running macnut r13 with the ulf which i love by they way. All is well i have a **** load of nandroid backups and roms and kernels on my sd. Then i tried to flash a theme the black froyo theme which is not compatible atleast not with mine anyway. I flashed it and my phone would just boot into a black screen so i booted into recovery tried to flash a backup and nope nothing happens. Then i try to flash another rom and no go i forget what is was saying but noting is working. I tried a factory reset from ulf recovery and nothing there either. Anyone got any ideas or am i stuck using odin to head back to stock also is flashing back to stock going to wipe my sd internal or external.
When i try to restore it says restoring system fine then is says data.img not found skipping restore then it says android_secure.img not found skipping sd.ext not found skipping. Then is says cant open /cache/recovery/log and cant open CACHE:recovery/log any help would be great.
and when i try to install another rom it goes through the process then says failure at line 12: copy_dir package:data DATA: installation aborted.
Time to break out Odin. Just load up JFD, get your phone into download mode and let Odin do it's thing. This way you get a fresh start. From there reroot and install anything you wish.
so the title says it all,
a couple of days ago i flashed the kl1 rom from samfirmware, after i didnt like it at all for different reasons, i decided to flash back to kk2 and all went fine,
no wafter a couple of days being on stock rom, i wanted to get root back + cwm
so i flashed cordeworkx's cwm 5.0.2.3 thourgh odin-> PDA
the phoen rebooted but hanged at the Yellow triangle, i reboot back and try recovery, and cwm recovery tells me this
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
also wiping dalvik cache wont work, when i select it, just nothing happens
when wiping normal cache.. i get E"format_volume: make_etf4fs failed on dev/block/mmcblk0p7
can i get some help here ?
grtz
1. Flash stock rom again.
2. Then use CF-Root to get root and CWM.
I don't know if the method you descriped is the right one. The method above will work.
Lennyz1988 said:
1. Flash stock rom again.
2. Then use CF-Root to get root and CWM.
I don't know if the method you descriped is the right one. The method above will work.
Click to expand...
Click to collapse
going to try that, ill report back, bedankt
got it back working again, i guess the cwm recovery from codeworkx doesnt work with kk2 and maybe kk5 ? maybe samsung changed something,,,
Cf root works, but i cant flash any rom, well, i can flash it allright but then it bootloops @ the yellow triangle again, no way to get into clockworkmod, download mode works fine
Clean Slate for those that balls up the firmware .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Still problems use usb jig to set rom counter to zero .
Return to service centre .
jje
Hi peeps
(I've tried looking for related posts but nothing comes up with my stuff)
I have downloaded Rom Manager Premium and also downloaded clockwork recovery, how ever every time I reboot into recovery to install i get this
E:failed to verify whole-file signature
E:signature verification failed
I have flashed the file before using Odin but i get other stuff saying E: cant mount (random stuff)
My phone is rooted
What am i doing wrong?
Rom Manager & CWRecovery don't work together on the SGS2. It's one or the other. For example, if you have CWRecovery installed (as a result of rooting your phone with a CFRoot kernel, for example), using Rom Manager has a tendency to break CWRecovery and/or put your phone into a bootloop.
So you're going to have to decide what you want to use.
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Depends what you used/did to flash the new rom. If you flashed it in CWRecovery, then that's unusual for it to be broken purely by flashing a custom rom meant for a I9100/T. Not completely unheard of mind you, but not usual.
If you used Rom Manager to flash the rom when you already had CWRecovery installed, then as per my previous post, it's obvious CWRecovery was broken by Rom Manager.
Again as per my previous post, one or t'other. Up to you. But use both at your peril.
olster said:
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Click to expand...
Click to collapse
So would you recommend that I remove ROM manager and just flash CW Recovery?
I wouldn't recommend you do anything/use one over the other. I'm just saying that you run the risk of having major problems (bootloop/broken CWRecovery) if you have both on your phone/try to use both.
Personally speaking, I've never had a problem rebooting my phone into CWRecovery every/any time I want to flash a rom/kernel/backup/restore.
Up to you which you use.
olster said:
So would you recommend that I remove ROM manager and just flash CW Recovery?
Click to expand...
Click to collapse
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Also when I use clockwork recovery
Anything I try to do i get this
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
What rom/kernel are you running and how did you root your phone ?
You could try flashing a CFRoot kernel from here, if that doesn't work you should probably get your stock firmware from here and flash that in Odin. After that you can use a CFRoot kernel to root your phone.
That will give you a clean slate with CWRecovery working.
Edit to add - Yes, you're getting that in CWRecovery because Rom Manager obviously broke it as I've already said.
olster said:
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Click to expand...
Click to collapse
I am using 2.3.6 XWKK5 ROM with the CF-Root-SGS2_XW_OXA_KK5-v5.0-CWM5.tar
Then try my suggestions in my previous post.
Right, I have managed to start again and got it working again.
Thanks your help
NP. Glad you got it working
olster said:
Right, I have managed to start again and got it working again.
Thanks your help
Click to expand...
Click to collapse
I have a GT-I9100M from Bell in Canada. My phone is broke and I've spent the last 24 hours trying to fix it with no avail
I was running the stock ICS rom from Bell. I rooted the phone and removed all the Bell bloatware and that was it.
Yesterday I came across a Rom that had the S3 version of Touchwiz so I decided to try it out - Salman ICS ROM for Galaxy S2 i9100! [TouchWiz UX][S Voice][GS3 ROM]
The rom installed perfectly and when it restarted, it stopped at the Samsung Galaxy boot screen. I attempted to go into recovery mode and it couldn't.
It would go into download mode. So I tried to flash the stock bell ICS rom - I9100MUGLD3_I9100MBMCLD3_BMC_www.samsdroid.com. It flashed with no issues but when it rebooted - back to the boot screen I go.
I flashed a CF kernal so that I could get into CWM and attempt to wipe it. It kept hanging on formatting /data.
I came across this guide - http://forum.xda-developers.com/showthread.php?t=1449771 and followed the steps and got no where.
Is my phone completely dead and if it is not - how do I get it back in working condition?
Help!!:crying:
When you flashed Bell's stock ROM from the guide thread, could you reach the recovery mode screen? I had the same problem and I simply did a factory reset after I flashed the stock ROM.
After I tried to flash my stock firmware with ODIN
I get stuck at Android System Recovery <3e>
and get these errors:
E: failed to mount /cache (no such file or directory)
E: Cant mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Cant open /cache/recovery/recovery_kernel_log
E:failed to mount /efs (No such file or Directory)
E:failed to mount /cache (no such file or directory)
E:cant mount /cache/recovery log
E:cant open /cache/recovery log
and as you can imagine the list goes on..... and when I hit reboot system now - it just freezes at the Samsung i9100 boot screen.
AAARRGGG
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
kmacsouris said:
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
Click to expand...
Click to collapse
looks like you have hit the eMMC brick, you could try to flash a pit file, and flashing it with repartition activated... This its the only thing you could try, before sending it off for repair
Best regards
Sendt fra min GT-I9300 med Tapatalk2
try to find a Stock ICS which does a full wipe. Usually the first edition of stock ICS
of each region does that.
Dear friend i understand your fear and i wan t to share with you my research, my trouble came for downgrading from ics to GB and now i have the red letters with the e cant mount **** , so i found that installing this rom (XXKH3) with the Phone Bootloader Update filed checked could fix it.
The original post is in spanish so if you need it it is here.
Scroll down until ERROR: E: Can't mount cache
http://www.taringa.net/posts/celulares/14623579/samsung-galaxy-S2---downgrade-ICS-a-Gingerbread.html
But on this post the link to XXKH3 is broken so i found this other link on english with the link working
http://www.theandroidsoul.com/how-to-install-xxkh3-on-samsung-galaxy-s-2-ii-i9100/
I'll try this thing in a couple hours when the download finish due to my 1.5 mb internet and i'll let you know any new,
Good luck
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
imfukked said:
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
Click to expand...
Click to collapse
Hmm . Did you have the device encrypted or anything along those lines?
I'm good dude. I figured it out.
imfukked said:
I'm good dude. I figured it out.
Click to expand...
Click to collapse
Good deal. Care to share in case others run across this issue?
stuck booting at logo screen
hello, my s3 did the same thing keis wouldnt even recognize my phone after rooting and trying to go back to stock rom, found when installing using odin, i installed tar file in boot img i had to download a zip unpack it and istalled kernal tar and bingo solved my problem, hope it helped..