Let me just start out by saying I'm a nube with limited skills. I have a Samsung Showcase SCH-S950C for Straightalk. I was sitting around on saturday and decided I would figure out how to root my phone because I had nothing better to do. I followed the instructions in a forum on this site and was able to root with no issues. After that I of course then decided to try my hand in flashing a custom rom to the phone (cyanogenmod) and this is where i went wrong. After flashing the rom I booted the phone and now the rom won't load and is stuck saying, "Unfortunately, setup wizard had stopped" and "Unfortunately, the process android.process.acore has stopped." The only menu I can get into is the sound menue via the volume key.
The next step I took was to reboot the phone back into CWM to see what I could do. Upon loading I was faced with the below errors.
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
Tried wiping the cache, factory reset and wiping dalvik and am unable to do so. It won't mount the cache, data or datadata. I then tried to put it back to stock via instructions for flashing a recovery mod for the phone and that did not take because I cant wipe it. From what I read i need to repartition the phone to fix this issue but I do not know how and honestly not even sure exactly what that means. As I said to start Im a nube. I also noticed in USB mode it says i now have 4 custom binarys on the phone and Im sure that is not helping things.
This is the point I stopped so as not to completely FUBAR the phone, if I have not already done so. If anyone can point me in the write direction on how to proceed I would greatly appreciate the help.
Look for odin and some related rom of your phone. Flash again. Normally problem would be fixed.
Sent from my XT901 using xda app-developers app
Probably non-useful information
I know nothing about the Showcase, so please accept this information for instructional purposes only.
I had zero experience with anything Android related until September. I successfully used old flip style or otherwise non-smart phones, so never had any experience with any version of Android (or any iOS either for that matter). My brother-in-law had given my parents a Fascinate that he replaced with a Note. It sat around their house until I picked it up and decided to see what I could do with it. I found this guide to be exceptionally helpful:
http://forum.xda-developers.com/showthread.php?t=1238070
Whereas I don't know if any of this information is relevant to your Showcase, the operational theory may relate. The phone that I was given was already rooted so I used the instructions in the guide to use Odin to return the phone to stock, then update to a Jellybean ROM. I learned a great deal working through the process a couple times, and have since been given a first gen Kindle Fire, an LG Ally, and a Droid Charge that I had enough confidence to work with, and successfully rooted and flashed each.
Related
I went ahead and flashed XTRSense 4.6 today after backing up my previous install from 4.0.6 (Or 4.1, can't remember) and after starting the process of restoring everything (And running the cache2cache script) I decided to restore my previous version because my texts didn't transfer over even though I used titanium backup on seemingly every messaging component. Every time I try to restore any nandroid backup or flash 4.6 again it fails on the writing boot - "Error while flashing boot image". So now every time I try to reboot it gets stuck on the androids, but I can still access recovery thank god.
How do I go about fixing this? I assume that since I can still access recovery that I'm not totally screwed, but I'm at a loss on how to fix this. Also, I am on ClockworkMod Recovery v2.5.0.1. I really should have restored Amon_RA when I had a chance.
Zerox12 said:
I went ahead and flashed XTRSense 4.6 today after backing up my previous install from 4.0.6 (Or 4.1, can't remember) and after starting the process of restoring everything (And running the cache2cache script) I decided to restore my previous version because my texts didn't transfer over even though I used titanium backup on seemingly every messaging component. Every time I try to restore any nandroid backup or flash 4.6 again it fails on the writing boot - "Error while flashing boot image". So now every time I try to reboot it gets stuck on the androids, but I can still access recovery thank god.
How do I go about fixing this? I assume that since I can still access recovery that I'm not totally screwed, but I'm at a loss on how to fix this. Also, I am on ClockworkMod Recovery v2.5.0.1. I really should have restored Amon_RA when I had a chance.
Click to expand...
Click to collapse
Clockwork
10 chars
If you're implying 10 character limit, I tried renaming it and still no dice.
The error when installing a new ROM is :
E:Can't symlink /system/bin/bugreport
E: Failure at line 22:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted
Zerox12 said:
If you're implying 10 character limit, I tried renaming it and still no dice.
The error when installing a new ROM is :
E:Can't symlink /system/bin/bugreport
E: Failure at line 22:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted
Click to expand...
Click to collapse
He is saying to install the Clockwork recovery in place of Amon Ra.
The 10 character thing is a limit to this forum - each post has to be at least 10 characters long. "clockwork" has only 9...
Well then that made no sense because I said in my first post that I am running clockwork recovery.
he us saying clockwork is the problem. many eris users have had many issues with clockwork.
amons ra FTW
Same problem except...
I have an EVO and tried to return it to stock condition prior to return. I can not get off of the Hboot screen, except into recovery. I have several "nandroid copies" on my SD card but none of them will load. I an getting the same "error while writing boot image" can you tell me step by step what to do?
Well the Verizon RUU finally killed the damn thing. Won't turn on, no charging light. Hopefully my insurance plan through best buy will cover it.
Zerox12 said:
Well the Verizon RUU finally killed the damn thing. Won't turn on, no charging light. Hopefully my insurance plan through best buy will cover it.
Click to expand...
Click to collapse
Repeat after me:
"I don't know what happened. I was charging it while I slept overnight, when I woke up the charge LED was off and the phone will not turn on. Yes, I tried charging it through both the charger and just the usb connected to a computer. No it hasn't worked at all since."
Also clockwork for Eris bricks phones. People need to stop friggin using it.
(CM9 Build 20120502 dated 2012-05-03 06:19:39)
I'll start off acknowledging my idiocy...I started tinkering with things I knew too little about. I messed up my phone fairly severely today, but managed to get it up and running again...with one issue. I no longer have a cellular connection (voice or data). I was having trouble the last couple of days, as I couldn't access the "More..." settings under "Wireless & Networks", but I figured it was a bug in whatever release I was running at the time and would be resolved eventually. I semi-borked my phone early in the afternoon (I repartitioned the internal storage incorrectly), but it was still able to connect. I then really borked it by tinkering with the partition tables. I was able to get that restored via parted restoring the GPT and doing some magic I didn't quite catch. I had previously attempted to flash back to stock via heimdall at one point, so I had an unrooted kernel and whatnot. I managed to flash a kernel with CWM, which allowed me to restore my last nandroid image. I've tried flashing a new modem. I've tried a complete wipe (data, cache, dalvik cache), but I get no connection. I have wireless, so that's something...but definitely not optimal.
Is this fixable? Should I try re-restoring to stock (from a workable state this time) and starting over from scratch? I have a rooted stock nandroid that I'll probably try restoring tomorrow. Could this actually be a hardware issue that just happened to show up at the same time I borked the rest of the phone? Any help/advice you have is appreciated!
EDIT: I've flashed back to stock, including flashing the bootloaders and param file. On first boot after flashing, I get the following error:
Code:
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
If I click "reboot system now" the system will boot, but without service. I can still hop on wifi if available, but I have no phone, and no data away from wifi.
EDIT 2: I fixed it, and I'm putting the info up here in case someone comes across this post. I downloaded [urlhttps://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&feature=also_installed]GSII_Repair[/url] from the market, and stepped through the first two steps of the repair process. After step 2, it tells you to reboot. Once I rebooted, I was up and running. I will be making a complete backup of efs.img and the rest of my system just in case I do some stupid tinkering again, and if you're here, I'd advise you do the same. It appears this can spontaneously happen based on a couple of other, less stupid methods (at least according to the comments on the app).
I would flash back to stock using odin or heimdall. Give yourself a clean slate to start over. I don't think that it is hardware related as it was working before you started tinkering.
So I flashed my original stock (rooted) image, which didn't help. I then heimdall-flashed back to pure stock. Still no go...however, it then booted directly to stock recovery with an error: "failed to mount /efs". After another couple of searches, it appears that normal flashing doesn't touch this. Given my phone is already pretty messed up, is there a good way to try fixing this?
The entire text in the stock recovery is:
Code:
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
SUCCESS!!! I downloaded GSII_Repair from the market, and started stepping through the "repair" steps. After step 2, it said to reboot. I rebooted. I now have signal, and can make calls.
I was really starting to think I was screwed there for a minute.
Hey guys, first post. I'm sorry if this has already been done. I've searched and come up with some threads for other phones and I'm really, really getting nervous and need to just have a definitive answer to my problem because I got this phone less than a week ago.
So I rooted using this guide (I have a Telus i717) (I guess I cant post links) on rootgalaxynote .com for the i717
and went with this 'ics objection rom' found under i717 roms on rootgalaxynote .com
it was working fine until I restarted the phone, the screen went black but the capacitive buttons were still lit. Entered recovery and tried to recover,
keep getting these messages E: Can't open /cache/recovery/log - E: Can't open/cache/recovery/last_log
When I try to wipe cache it says Wiping cache... Formatting /cache... and just hangs there, nothing happens. The phone is functional now, I can boot it up and make calls and use it regularly and whatnot, but I need to fix this.
Also, my issue is that I need to be able to fix it on a Mac. Well, I don't NEED to but right now my PC is an hour train ride away and it would be much more convenient to be able to fix it with a Mac (that is, if the only way I can fix it is by using some sort of Odin-type thing that I used in the first place)
Again, sorry if this is in the wrong place or it's been covered before but I'm getting concerned that I've somehow caused some permanent damage? 5 day old phone...
Thank you in advance for any help!
Evan Watts
try to wipe dalvic cache first then wipe cach
Enter recovery with the buttons not by any app like Rom Manager.
Try flashing this touch recovery from your current recovery: http://forum.xda-developers.com/show...touch+recovery (the zip labeled CWM)
Then flashing the rom zips again after wiping data/cache.
I had the same errors happening when I updated my recovery to the latest version via Rom Manager. Then I reverted back to the original CWM touch recovery I had before, and everything wiped and flashed just fine.
just install a new version of CWM or re-install the one you last used... that was the only thing that worked for me
Lol... this post is from July of last year
Sometimes it takes a while for some members to get their answer together and post it.
I'm very sorry if this isn't in the right spot. I've looked around a bit, and used the search engine, and I haven't been able to find anywhere that I think this belongs. Anyway, here's my problem.
Ok, so here's what happened. I was looking at my build.prop settings in rom toolbox. Out of curiosity, I changed lcd density from 240 to 160 just to see what it would look like. I planned on changing it right back immediately but Touchwiz kept force closing.
I then tried restoring my phone back to factory, but my recovery no longer works. I know how important it is to give as much detail as possible so here's the ENTIRE output from after rebooting into recovery, clearing user data, clearing cache, and then reinstall packages...
#MANUAL MODE#
--Applying Multi-CSC
Installing Multi-CSC
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I had previously tried installing ClockworkMod Recovery ( through Rom Manager ) and thought it had failed because when I rebooted, it took me into the stock Samsung Recovery Utilities. Now I'm thinking that it may not have actually failed, and that I had to select 'reinstall packages' and that would have finished the ClockworkMod recovery install. I'm now thinking that the failure to verify whole-file signature is happening because I no longer have root due to clearing user data, and clearing cache. I may be wrong, idk.
I know how to reset the build.prop lcd density setting to fix that issue, but I have to wait for my aunt to get her computer back to root again. She's currently having it fixed, and I have no other access to a computer.
What I'm asking for help with is to either get my recovery utilities to be functional again in case I ever need to do a hard reset, or get ClockworkMod installed. Whatever is safer is the route I want to go.
I'm kind of thinking that ClockworkMod not fully installing itself is stopping the recovery from functioning like normal. The reason I think that is because I've restored my phone to factory stock many times. The sdcard was NOT in the phone those times and now it's trying to use 'update.zip' from the root of the sdcard when I select reinsall packages. Kind of like ClockworkMod recovery is partially installed, enough to try to use itself instead of the stock recovery, but not enough to be a working recovery.
As I said above, I'd really like to have a working recovery on this phone. I'm actually homeless at the moment, and I have absolutely no money to buy a new phone. Shiiit, I have to bum money from customers at a shopping center every single time I want to eat even. This phone is basically the only thing that keeps me sane. Being homeless is REALLY, REALLY boring as you can imagine. This phone makes it much more tolerable.
Sorry for the length of the post. If there's any other details that may aid in fixing this, let me know and I'll post them. I'm pretty sure I've provided all the detail possible though.
Ok, I typed that up while I was away from wifi, and decided to do a little more research before posting. I'm seeing that I was right about the ClockworkMod recovery not being fully installed. I didn't do the last step of rebooting and then reinstalling packages originally. Now. I'm wondering if the signature verification is failing because I no longer have root access or if it's something else. If that's it, I'm going to finish the installation once my aunt gets her computer back unless there's some way I can get it to reverse the partial ClockworkMod install.
Again, I'm sorry if this is in the wrong place, and for the length. Thanks in advance for any help you can provide.
Hey guys,
I am a noob. I admit it. LoL.
My device is the Samsung Fascinate, on Verizon. I'm running (or was trying to run) HellyBean (Android 4.2.2), and I have ClockworkMod v4.0.1.0.
I had quite a bit of trouble getting the device rooted in the first place. Many of the common rooting guides had links to files that were corrupted, or the links just led nowhere at all. I found the thread here on XDA that actually provided the name of the file as well as the link, and I was able to get the files from other sources, and finally complete the root.
The hellybean flash was a different story. I read the whole guide through, and missed the note at the bottom about GAPPS. So it got complicated, and I nearly bricked the device. So anyways, I got HellyBean and Gapps flashed successfully, and am approximately two months into getting my phone back into a usable state. (The Titanium Backup of my contacts was apparently incompatible with 4.2.2, and plain-text restore made no changes, so I've been restoring it manually person by person. LoL.)
Last week I went out of town for a few days, where power was limited, and so I devised a system where I brought an extra battery, and I would power off the phone and switch the old battery out with the newly charged one each evening. So on Sunday, I did the normal; powered off the phone, replaced the battery, and powered the phone back on. Cyanogenmod animated logo comes up, and stays up for 10 minutes. So I jerk the battery and try again. Same problem. I booted into CWM, and I get several errors, as well as "Error mounting /System!". I'm seriously disappointed. LoL. I thought for sure that this time, I would have a ROM I enjoyed using, and was stable. I guess I was wrong.
Symptons:
Cyanogenmod Logo Stuck on Loop
CWM displays these errors:
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, under "mounts and storage" when I try to mount my system, it gives me this error:
Error mounting /System!
Noticed that phone was extremely sluggish after previous reboot. Phone recovered with the help of Go Task Manager Pro (Advanced Kill), and I thought nothing more of it.
Just before re-boot, noticed that Go Task Manager Pro had reverted to Go Task Manager, and was asking me to re-buy the Pro version. (Odd, since I've never had troubles with the Go apps before.) This was another factor that prompted the re-boot, besides the battery being low.
Changes made directly before last re-boot:
Installed Google Goggles. Had an error signing in.
Needs:
Regain information such as contacts, notes, texts, and app data.
I neglected to make a Nandroid backup, since I was trying to wait until I'd gotten the phone into a state where I could use it after a restore. (Obviously a mistake, and one I won't make again.)
I have not made another Titanium backup for the same reason.
My question is: Is there a way to regain the information? If not, is there some reason why my phone would do this, and if so, how can I resolve it? Do I need to simply re-flash HellyBean and Gapps, or do I need to return to the stock (groan) ROM first?
If you all need any more information, please don't hesitate to ask. I'm doing the best I can, but this is my first time.
Thank you all for your help!
You need to flash back to stock and start over and FYI titanium is fully compatibly with 4.2.2 so just restore from that and your Google account should automatically restore everything else
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
You need to flash back to stock and start over and FYI titanium is fully compatibly with 4.2.2 so just restore from that and your Google account should automatically restore everything else
Click to expand...
Click to collapse
Thank you! Could you, however, tell me what went wrong? There was no apparent reason for this. If I don't know what went wrong, there's no way to guarantee that it won't happen again.
NafetsaDroid said:
Thank you! Could you, however, tell me what went wrong? There was no apparent reason for this. If I don't know what went wrong, there's no way to guarantee that it won't happen again.
Click to expand...
Click to collapse
More than likely it was a issue that has been fixed you mentioned the cuanogenmod logo in hellybelly that was from a older build the new 4.2.2 hellybellys has a custom boot animation I suggest downloading the latest 4.2.2 hellybelly and see if it happens again and if not it was probably fixed
Sent from my SCH-I500 using Tapatalk 2
That would do it. Should I just download hellybean from their website like I did the last time, or is there a specific link that I should go to? Thank you so much for your help!
NafetsaDroid said:
That would do it. Should I just download hellybean from their website like I did the last time, or is there a specific link that I should go to? Thank you so much for your help!
Click to expand...
Click to collapse
Nope just go to the website and download the latest version which I believe is 04_05
Sent from my SCH-I500 using Tapatalk 2
What happened is your system partition got corrupted. The main evidence is the thing with go task manager. Apps like that rely on your device's Android ID to recognize you've bought the pro version. If your system partition was corrupted, then when go task manager tried to read your Android ID, it errored and thought it was running on a different device. Probably, at its root, a serious kernel error that happened before you rebooted the phone.
Posted from my Galaxy Tab 2 with CM10.1
---------- Post added at 07:23 AM ---------- Previous post was at 07:05 AM ----------
WAIT!!!!! Don't wipe and start over! The data partition of your phone is still intact. The errors you saw that involved /cache are known issues with CWM4. Just follow the instructions in here: http://forum.xda-developers.com/showthread.php?t=1694984 and reflash HB.
Posted from my Galaxy Tab 2 with CM10.1
Yea I forgot to mention NEVER EVER EVER EVER EVER USE A TASK KILLER IT CAUSES SLOW DOWNS A D SOMETIMES BRICK THE PHONE but your system patricians WAS messed up or you wouldn't have got them errors even in cm7forcwm
Sent from my SCH-I500 using Tapatalk 2