(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.
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.
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.
Help? I've done about a week of searching, reading and experimenting.
I originally black-screen bricked my YP-G70 (USA) by trying to flash back to the stock ROM in Odin. However, I made the mistake of flashing it in the wrong item/field in Odin. Then, I basically panicked and did a number of stupid things. One of the stupid things was I checked the "clear EFS" box while trying things out. The other stupid thing was I checked the "lock flash" button in experimenting (without even knowing what they do). So, yes, I'm stupid. I know, I know.
Anyway -- I was able to use the Unbrickable Resurrector to get back to the device... and used the Download Only recovery from Adam to get it in download mode.
Next, I was able to get it to the point where I can get the stock bootloaders and either a custom or stock kernel in there. I even used the custom kernel to "repair permissions".
However, my problem now is this: It seems the /cache and /efs directories are missing and I can't get past the errors. When I try to flash a ROM onto the device, including the stock recovery ROM, it appears to succeed in Odin. But, the device still can't really start up because of the missing /efs and /cache.
Re-flashing the PIT file doesn't help with this.
Is it possible to get a Samsung Galaxy Player US 5.0 Wi-Fi YP-G70 efs.tar file and flash it with Odin to get things past this point? After much searching, I haven't been able to find an EFS file anywhere to get past this point.
Can anyone help point me in the right direction?
Currently, when I turn on my device, it gives a long series of errors that seem rooted in two messages:
E:failed to mount /cache (No such file or directory)
E:failed to mount /efs (No such file or directory)
(and a series of similar errors for paths within those two paths).
Thanks
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.
Hello all,
I recently wiped my phone clean, to give it to a friend, through TWRP. I was stupidly drunk in the process and didn't realize that I wiped every possible partition! At this point, I have no OS, no data, but can still access recovery and the bootloader without an issue (thank god! not a brick!). I am fairly good with working on this phone, but I have ran in to a couple problems. Apparently, RUU's are NOT working for returning to stock. I have tried many combinations of firmware versions, including the original out of the box RUU's for my ATT HTC One. Not a single one has worked. However, interestingly enough the RUU will run without an error, but gets stuck in stage 1/6. I've left it overnight and still stays in stage 1.
After doing intensive research on the issue, I realized that my problems possibly pertain to the fact that I am unable to mount /cache and /data. I can't even repair permissions because of this, so it has truly hindered all possible fixes. I believe it may be due to the fact that I might not have root anymore, but I don't know how to get root without a system partition. TWRP attempts to do an auto root but fails each time.
Wonderfully enough, I have issues using ADB Sideload. It will flash a .zip until 92%, at which point it stops with an unknown error. I've tried with multiple .zip's found from HTC1GURU's Stock ROM Guru Reset downloads page. No avail. I've looked into other fixes and still no luck.
SO...I'm practically at my wit's end, about to pray to Mobile Phone Buddha that this thing will work again...
Any suggestions?
Anyone??
I've found a very useful guide provided by mike1986 regarding an unblock procedure using the mkfs.ext4 file, however I am unable to access the /data partition regardless of all fixes I have found online. I ned some real linux expertise in my situation. I wish I could get contacted directly by mike 1986...
Is this att? What boot version? Flash the latest twrp from there website then erase catch and when entering recovery the computer should see it as a removable disk where you can put roms to flash then flash anyone that is compatible with your current firmware. Good luck
Sent from my HTC One using Tapatalk