Database Info

Help: EFS Not Mounting After Flash

I've been running CM7 for a month or so and I started having some stability problems. So I decided to try DarkyRom.
I did everything like normal (used heimdall).
Upon boot it had an error.
Failed to mount /efs while applying multi-csc.
I'm dead in the water. I tried to flash back to stock. I get an error and thrown into samsung recovery. I can reboot from that and I boot to the gui with no radio. Phone info says "Unknown" Hardware and Baseband Version.
No. I did not backup any EFS (news to me). I do have access to the same model phone, my son has one he just uses as a fancy MP3 player (no phone/data plan).
Is there anything I can do? I did use the ADB Shell and ran "mount" to see if the EFS was mounted. It was a negative...
-MT

Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)

mainethoughts said:
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
Click to expand...
Click to collapse
First off,are you even on the right forum? Darky rom isn't built for this phone so it's not going to work.
Sent from my SCH-I500 using XDA App

Ugh...an unfortunate response. Yes...I'm on the right forum.

I did make a CWM backup from a couple weeks ago. Not sure if that helps.

mainethoughts said:
Ugh...an unfortunate response. Yes...I'm on the right forum.
Click to expand...
Click to collapse
Them why are you flashing roms from other forums/phones? Use odin and check repartition.
Sent from my SCH-I500 using XDA App

*hangs head* Admonishment accepted. I really don't know what I was thinking.
Here is my progress. I tried using Odin to just Re-partition. No go.
<ID:0/003> Can't open the specified file. (Line: 1455)
So then I downloaded stock EC10 (That was factory on my phone). I flashed that via Odin with "Success".
The same error as initially posted was on the phone. I rebooted from the stock recovery console and I was able to boot. 3g works. The hardware and baseband are now accurate. I'm getting a lot of force closes however. The twlauncher is constantly crashing.
So now the phone is semi-functional but there are still errors. (I was getting more forces than normal in CM7 that caused me to dive into this process in the first place).
I could be way off base but I'm thinking that possibly there is corruption (or wrong file system?) problems with the internal SD (I did format the External SD at the start of this).
I appreciate your help. Any suggestions from here?
-MT

Additional Note: Settings are not saved between reboots.

-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.

mainethoughts said:
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
Click to expand...
Click to collapse
Use the full odin restore package and make sure you use pit and pda files. Repartition must be checked. Wiping data might be a good idea as well.
Sent from my SCH-I500 using XDA App

I would odin the full mesmerize package EE19. http://forum.xda-developers.com/showthread.php?t=881064

That is what I have already done I believe. Followed instructions from:
http://forum.xda-developers.com/showthread.php?t=881064
-MT

If you've done that, then i'm at a loss. That usually is my solve-all solution... Sorry man.

Thank you much. Is it possible that I could have a faulty internal SD? I had suddenly started getting a lot of force closes in CM7. I guess I'm just wondering if I'm fighting two separate issues here. (My bonehead move vs. a real problem)
-MT

I think I'm FIXED!
I was finally (I don't know how) able to get Odin to Flash CWM 4 (The Blue one needed to install CM7).
I got ZERO errors in CWM. So I took the opportunity to clear caches, format data...I got destructive.
I then installed the CM7 Rom. -SUCCESS
Installed GAPPS - SUCCESS
I hope everything is OK at this point. I know CM7 is booting in about 20 seconds opposed to 5 minutes like it was before I decided to try to morph my phone into an I9000.
I actually saw the black screen with the little phone to PC icons at one point tonight. I think I came real close....
Thanks for your help!
PS: CONFIRMED mmcblk0p1 is mounted! (EFS, etc) PHEW!

I had this happen to me right after a Odin even did the rfs formatter tool exact same problems not saving settings upon reboot and it saying something along the lines of process.android.blah blah blah and double vibrate when booting before the fc anyhow I just reflashed miui to get cwm4 wiped everything reflashed cm7 no probs since
Sent from my SCH-I500 using XDA App

[Q] Why'd I get this boot failure.

I was just beginning some work on a new rom. I used the same rom kitchen setup I have used before. (adding the Edison file). I imported a backup I just took with CWM, which has always worked, then just to test it I built it without any mods so that I could make sure it was OK. I wiped data and dalvik, then flashed the zip. success. I rebooted and it popped into the fastboot boot failure screen. below were three errors that I do not remember exactly, but they were all CG system something or other. one was 0x18, the other were actual words.
This was not a big deal, I just had to fxz back to stock, root, and then restore the backup I made before hand, but it still scared me for a sec and is a little odd. Does anyone have an Idea what I did wrong?
EDIT: I just realized I forgot to change format system to delete recursive in the updater script. Could that be it?

lkrasner said:
EDIT: I just realized I forgot to change format system to delete recursive in the updater script. Could that be it?
Click to expand...
Click to collapse
Yep that's it. From what I understand... our bootloader checks for certain signatures on /system and other partitions, and if the signatures are wrong or nonexistent then it gives an error similar to what you have. That's the reason we can't flash international system.img's, the signatures don't match up.
Changing "format("...")" to "delete_recursive("/system")" should work.

cogeary said:
Yep that's it. From what I understand... our bootloader checks for certain signatures on /system and other partitions, and if the signatures are wrong or nonexistent then it gives an error similar to what you have. That's the reason we can't flash international system.img's, the signatures don't match up.
Changing "format("...")" to "delete_recursive("/system")" should work.
Click to expand...
Click to collapse
cogeary is 100% correct, you can not use the format keyword in the installer script, it has to be the delete_recursive keyword, lfaber06 and I had these exact same issues when we first started this whole ROM building experiment back in Dec. last year.

thanks, good to know! this scared the crap out of me until I realized it was sitting in fastboot just waiting for me to flash it back.

[Q] CWM unable to mount /system

This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.

cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .

I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.

Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.

cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium

I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?

cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium

Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium

rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system

rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.

cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium

Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.

I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.

Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.

I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition

I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.

can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you

[Q] Corrupt GPT, SBF and Fastboot have no effect

Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!

Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!

No one?

Hello,
have you fixed it ?

Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.

ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer

jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?

ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+

[Q] Please explain "Installation" per cmenard's ROM

Hi Guys,
I have a Samsung Tab 2 GT-P5113, rooted, and love it. I had to install drives and use Odin to get this ROM installed but it worked and it worked really well. Um, this is the one I used:
http://www.androidauthority.com/galaxy-tab-2-10-1-root-clockworkmod-recovery-cwm-95536/
It is great, I love it, but it is not Jellybean. I have 4.0.4. Now I have ClockworkMod, love it, it really works well. So I downloaded the Milestone zip from here:
http://forum.xda-developers.com/showthread.php?t=1892046
I got the gapps to go with it, and used CWM to install it. CWM works really well, I rebooted to the CWM boot screen and chose the zip file, wiped all caches, and I did pick the make a backup first option and performed the install. The device booted to the little green guy and all the text details appeared. Wiping cache, etc., but when the zip installed, it failed with a Status 7 error, failed to mount /system/ errors such as fonts, device or resource busy, /system/app/ApplicationProvider.apk "Read only file system".
I saved the report log, it is very informative down at the end, last paragraph gives all the juicy details. I should publish this log if I want real help. Let me do it now. Yeah, here ya go:
http://home.comcast.net/~theohmster/text/cwm_fail.txt
Oh, I can attach it! The original CWM recovery.log is attached as a txt file. Duh! :silly:
Look at the last page of the attached log. I understand Linux so I actually know what all these errors mean. Read only files means that the installer does not have root permission. Resource busy means an open file. Can't find /sd-ext in /etc/fstab, now that is a good one, there is no fstab in the /etc/ directory, not even on the phone. But why they are occurring is out of my grasp as I am not a ROM developer and android OS is not Linux, exactly. ...ugh!
Why? I mean, I do not know what to do about this. I tried this several times, first time was a total failure, the MD5 was off by a mile, downloaded it again, got a good copy, could view in Winzip, MD5 matched, but this failure. I did this several times, thank God I had chose the backup first option in CWM and was able to restore the system in short order. The entire process took about ½ hour or less. Am I doing this wrong? I tried to understand cmenard's instructions and I don't quite understand what he is saying to do. The instructions are simple. Here is the URL to the download and instruction page:
http://forum.xda-developers.com/showthread.php?t=1892046
But, it fails by my method, what do these instructions mean in plain English? Flash Rom, what do you mean "flash the Rom"? I got two zip files, gapps and milestone. What is this "Rom" to flash? Wipe I can do in CWM. Flash the zip. You mean install with CWM? Wipe the cache. Again? How? Run CWM again?
Flash Rom in CWM or TWRP
Wipe data/factory reset if you are coming from another ROM
Flash the zip
Wipe cache/dalvik cache
Then flash GApps.
Reboot
So like what am I doing wrong? I really want this Jellybean, especially for my Razr Maxx, but if it will not work on the tablet, I will not mess with my rooted 4.0.4 Razr where I really want JB. The phone was pretty fast 6 months ago, but it seems that all these updates and apps have slowed the thing to a crawl. I use Micro CPU Monitor and love it, two single pixel wide green lines at top screen, one for each core. They are often both pinned all the time so the phone is slow. Use it on the tablet too, same issue but nowhere near as bad on the tablet as it is on the phone. Like who wants to wait 60 seconds every time you touch the screen to make a call or use the maps? Jellybean is said to make things a LOT smoother and really grease the wheels to make ICS really slick and that would help, yes?
I showed the log to a developer on droidxforums, he is really good and made the CD iso files that boot the PC to Linux and rooted the phone. But he really was not sure of the issue and does not have this device.
Somebody help me please. I really want to fix this and am really bummed. Thanks. Happy New Year. :crying:

Okay folks, don't break a leg or anything in your mad dash to render assistance here. It is not worth it, take your time...

OK let me start up my computer and I'm gonna take a look...
Ok...
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Click to expand...
Click to collapse
AFAIK these are fine.
EDIT: The datadata one is questionable though.. that might be a typo somewhere (maybe... not totally sure. I know there's a /data/data directory, maybe a missing slash? Just thinking out loud here. Whatever it is, I doubt that this is your real problem. That would be the inability to mount /system
Couple questions/things to try.
Firstly, can you remount /system as RW in terminal emulator?
Second, can you install any custom ROMs other than CM10? Try any really, just want to see if the problem is CM10 or your device/CWM setup (Let's hope not the second one)
You do seem to be doing the CM10 install correctly from what I can see.
Oh, and thank you for having the sense to make a backup. Too many people don't and complain about bricking their device and having to ODIN to stock.
Sent from my GT-P3110 using Tapatalk HD

FYI, datadata is a partition symlinked to /data/data, it is only present on some devices like my Fascinate where /data/data is stored on a different memory chip.
Posted from my Fascinate using XDA Premium