Related
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
So, I have the Samsung Fascinate from Verizon, had this phone when it was new and just found it again and it is much better than my blackberry, or so I thought. I am trying to install ICS build one by following http://forum.xda-developers.com/showthread.php?t=1238070: - I have been able to install PW but when I am trying to install ICS1.zip (I renamed for simplicity purposes) I get the following errors: E: Can't mount /cache/recovery/log and cache/recovery/last_log
I have read enough to know that I needed a class 6 or better SD card so I bought a Class 10 8 GB from Best Buy and gave it another shot. I have mounted and unmounted the SD card multiple times, and when installing it shows:
-- Installing: /sdcard/ICS Build 1.zo[
Finding update package...
Opening update package...
Installing the update...
Installation aborted.
Any suggestions are greatly appreciated by those with positive feedback or calling me ignorant and not finding the answer online. Again, thanks in advance.
P.S. Yes, I have installed everything up until step 19 is where it stops working
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
So you odined back to stock and then tried flashing build 1 in cwm4 fixed for mtd?
---------- Post added at 09:02 AM ---------- Previous post was at 08:59 AM ----------
kadin.zimmerman said:
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
Click to expand...
Click to collapse
Build 6 link is dead...and for most flashing build 1 or 2 first is the only way ics build 6 will install. Also many folks have had trouble with class 2 sd cards...your not doing anything special more so just lucky its working for you.
kadin.zimmerman said:
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
Click to expand...
Click to collapse
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
New link to build 6 : http://www.mediafire.com/?sjn6x76c48me9su
So if going right to build 6 didn't work, then you would just have to give it another try, but installing build 1 or 2 first. No big deal, however I do know people who have had it work just fine.
I never said i was doing anything special because i had a class 2 sd card. I simply find it hard to believe that the sd card would have that much of a bearing on whether or not you can install a rom on a phone. I realize some roms partition the sd card the way it wants it, but in the end, the rom is flashed onto the actual phone itself, not the sd card. I know what the difference is between different classes of sd cards so you don't have to explain.
---------- Post added at 03:58 PM ---------- Previous post was at 03:52 PM ----------
PushyFurball said:
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
Click to expand...
Click to collapse
Sorry i thought that link was working...here is the one i originally start out with when flashing from stock. : http://dl.dropbox.com/u/32493357/cwm4_fixed_for_cm7-ODIN.tar
Please don't hit me, dropbox link doesn't work either.
PushyFurball said:
Please don't hit me, dropbox link doesn't work either.
Click to expand...
Click to collapse
Give it another try, it is working for me when i click on it
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Ok, turn your phone off, remove the memory card, and flash this kernel instead : http://dl.dropbox.com/u/32493357/CWM3_Voodoo.tar.md5
Then put the memory card back in and boot to recovery
---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------
PushyFurball said:
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Click to expand...
Click to collapse
Actually i have never put a pit file into odin. When ever i went back to stock i just did the stock .tar.md5 file and it worked fine. I am not sure what the pit file is used for so maybe i would not use that. Let me know if that voodoo recovery got rid of that error
So the good news first, not putting PIT on their got rid of the errors of mounting and whatnot. Bad news is...
-- Installing: /sdcard/ICS Build 1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That is the same for Voodoo Lagfix and cwm4.
Now when I tried just the Build 6, it is constantly going to "Samsung" over, and over, and over again.
Ok good you are making progress lol. So you did try it with build 1 initially and it didnt work? Thats strange because it usually does.
So have you gone completely stock without the pit file, loaded a cwm kernel, and then wiped data and cache and still no luck?
There are two different versions of ICS for the fasciante, one by alphalulz and the much better builds from teamhacksung. No matter what i tried and it didnt work on my device (before i eventually figured it out) , alphalulz's ICS V2 always would load on my device. It also loaded its own custom kernel as well, so when it installed, i would let it boot up to confirm the V2 version was working, and then i would clear all data and cache in the new kernel it gave you, and then would switch over to teamhacksungs builds.
here is the link to download the V2 rom : http://rootzwiki.com/topic/9687-rom-aosp-ics-extreme-alphalulz-v2-1118/
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
PushyFurball said:
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
Click to expand...
Click to collapse
Hey your getting closer...you will get it dont worry lol
so you just had build 1 working right?? go from build 1 to build 5 (being sure to clear data and cache) and then from build 5 to 6, ONLY clearing cache. Going from build 5 to 6 does not require a data reset.
I am a new proud member of having a Samsung Fascinate with 4.0.3 . Thank you so much for your help kadin.zimmerman!
-Thread Closed- ^_^
Now download ROM manager and do a backup so you can revert back to that state in case something goes wrong! I do backups about once a week
Sent from my SCH-I500 using XDA App
I installed FA16 (2012/1/16): ODIN CWM that was listed on the first page of the developement forum. There were no issues - only took a few minutes. Afterwards - nothing seems to have changed on my phone. the firmware is still 2.3.5, the kernel is still 2.6.35.7 and the build number is sch-i500-eh03. Have I missed something? The phone seems to be working OK. Note: I installed CWM from the ZIp file after I put it on the SD card in the root directory. Thanks for your help
No you haven't missed anything - you flashed a new recovery kernel. Do you know what the purpose of the recovery kernel is? The recovery does not effect your 2.3.5 operating system, the cwm recovery allows you to boot to it (by powering the phone completely down, and then holding the up volume, down volume, and power button simultaneously) and then you will be presented with a menu to install a custom rom such as the new android 4.0 or the cm7 cyanogen mod etc...so its pretty cool
Thanks for 'learning me'. Anyway, before i started playing with my Fascinate today, I had ver 2.2.1 installed - worked fine. After all the changes, I lost the Google search box on the home page - is there anyway I can get that back? I have the icon - just like the search box better. Thanks
Well what all changes did you do other than installing a recovery? Did you flash any files?
And you have 2.3.5 now right, so how did you get it. Did you do a Verizon over-the-air update or did you flash that file as well. I am just confused as to what you did because technically if all you did was install a recovery, it wouldn't mess with you Google search
kardin - recoveries and kernels are 2 completely different things. You keep saying CWM recovery kernel, but that doesn't make any sense. I'm not saying you don't understand what a kernel or recovery is, but they're not the same thing and I think you might confuse people when you say recovery kernel.
Hey guys, I've searched endlessly for hours and I'm at a point where I am so confused right now do not know what to do. I know the answer is somewhere in the forums, I'm just not making sense of anything anymore. I'll cut to the chase:
I have a Rogers tablet Galaxy Tab 10.1 GT-P7500 wifi+3g/4g version that I had rooted and flashed ICS last January/February to a AOKP ROM. Today, I felt the urge to try getting a Jelly Bean ROM on my device. I downloaded the appropriate CM 10 ROM under the title "cm-10-20121112-EXPERIMENTAL-p4.zip". Booted in recovery mode, did a backup, wiped + factory reset, then wiped cache, then wiped Dalvik cache, then installed from zip. I got some error 7 / status 7. Researched a bit and concluded I needed to update my CWM Recovery from the 5.8.xxxx version I had to the 6.1.xxxx one that is the most up to date. So I restored from my backup to make sure I could just go back to how things were.
This is when things got complicated. I couldn't find any proper guide on how to just update CWM, I kept getting referred to Droid Basement (which is equally as confusing), and figured out this is the Parent Directory droidbasement.com/galaxy/roms/cm10/p4/ . I downloaded "recovery.tar.md5" thinking I could maybe just go into recovery and apply it somehow, or go into ROM Control and "update" from a file and use that, nothing. I stumbled on this page "androidauthority.com/galaxy-tab-10-1-p7510-p7500-jelly-bean-cyanogenmod-10-cm10-136000/" which then linked me to another article explaining how to update CWM accordingly "androidauthority.com/galaxy-tab-10-1-3g-4g-p7500-root-50789/" (Did the second paragraph steps)
I downloaded the KERNEL.ZIP and RECOVERY.ZIP and did as they said, except I re-wiped and factory resetted, wiped cache and wiped Dalvik cache thinking this is something you "need" to do everytime you install any .zip whatsoever. I then flashed the kernel + the recovery, and then nothing. I get a black screen, but if I hold down the power + left volume and try to get into recovery, I get to the recovery menu, if I click recovery NOTHING happens, I can go into download mode, but I have no idea what to do there / have never used that. I know "odin" has something to do with this, but I have a mac and apparently this is only functional on windows and I don't have bootcamp running right now, I do have an old windows laptop that I could use if really needed if "odin" is not compatible with mac in the end. I am not sure if this is considered bricked, hard/soft, but yeah, I need help! I apologise once again and don't mean to offend anyone, I'm sure the answer is somewhere here, but I can't seem to find it especially since none of the threads are ever specifically in regards to my Rogers tablet, and also since a lot of guides are for wifi only tablets and I'm not really sure if that really makes the big difference.
Thanks!
Wow dude... i suggest if you do not know what you are doing try to find out the most information you can get before you even flash a ROM untill you are sure what exactly you are doing. If i was your tablet i wouldn't start up either because i would get confused
Here's a guide from our friend QBking 77 how to get back to normal, everything is well explained, follow him STEP by STEP!!
http://m.youtube.com/watch?v=KYBs98R9rTs
Good luck
---------- Post added at 06:42 AM ---------- Previous post was at 06:40 AM ----------
Ohh, before you run into more issues, do not download the ROM for the p7510 in his discription, but get your stock-rom from your device from http://www.sammobile.com/firmware/
Hey Defqon thanks for the link and I had stumbled upon it earlier, problem is he says wifi only version when I have the GT-P7500 version 4G Rogers. Does the tutorial still apply for me?
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
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.