Related
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
rail205 said:
Hi all, Strange thing happening to me. I was running Tweaked Rom for the longest time, then I decided to try Liquid Rom (as it does not update my bootloader), flashed as always and when it booted I had no signal, IMEI,etc. quick heart attack then decided to use my Tweaked nandroid. Which worked fine was back in action. Now when I go into recovery I get all kinds of errors saying cannot mount DATA,CACHE,DALVIK,INTERNAL. I tried updating my TWRP to the latest ... No Luck. they still wont mount and show 0mb space. Phone is still working. Anyone have any input or guidance for me.
Much Appreciated
Sorta Fixed, switched to CWM recovery and all is well, although if I go back to twrp it still shows cant mount internal sd, data,dalvik etc...
Thanks for Looking and maybe this will help others that run into this problem
Click to expand...
Click to collapse
I got the same thing on my Samsung Galaxy s3.
I see other threads like this, but didn't see any solutions, and most just helped people get into recovery mode... so sorry if this is redundant of something I didn't see.
This is a stock phone, and it is just about 10 days short of two years old.
It's my wifes phone, and completely just a normal phone...
Just sitting at the 'Note 2' screen this morning after being on the charger over night.
Nothing seems to work without going into recovery mode.
In recovery it won't let me wipe the cache, or even do a factory reset.
"E:failed to mount /cache (No such file or directory)" just keeps reporting for different commands is is trying to run whenever I try and execute anything in the menu. Always the /cache folder, not /system or anything else.
I googled and searched here and found some 'sudden death' problem that I guess Samsung issued an additional 12 month warranty for and I am wondering if this is the same of if this is covered possibly.
Was going to take it by the T-Mobile store today, but not expecting much cooperation from them except to try and get on a new contract and phone.
Any thoughts?
Of course T-Mobile was zero help
They tried to tell me it was a bad battery. LOL.
Said that since the old two year contract is up in a week or so they would just renew a new deal early, or pay $200 for the insurance deductible.
Going to call samsung directly to see if there is a manufactures extended warranty like I read and how I get that process started.
Nomad1109 said:
I see other threads like this, but didn't see any solutions, and most just helped people get into recovery mode... so sorry if this is redundant of something I didn't see.
This is a stock phone, and it is just about 10 days short of two years old.
It's my wifes phone, and completely just a normal phone...
Just sitting at the 'Note 2' screen this morning after being on the charger over night.
Nothing seems to work without going into recovery mode.
In recovery it won't let me wipe the cache, or even do a factory reset.
"E:failed to mount /cache (No such file or directory)" just keeps reporting for different commands is is trying to run whenever I try and execute anything in the menu. Always the /cache folder, not /system or anything else.
I googled and searched here and found some 'sudden death' problem that I guess Samsung issued an additional 12 month warranty for and I am wondering if this is the same of if this is covered possibly.
Was going to take it by the T-Mobile store today, but not expecting much cooperation from them except to try and get on a new contract and phone.
Any thoughts?
Click to expand...
Click to collapse
Not sure how savy you are.. but try using odin to flash a firmware...
Download the all in one for the note 2 and then it will put you where you want to be
Soft bricked G3 with a lost IMEI number
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
mrchuajason said:
Hey guys I have 2 major problems for my phone.
1) I was trying to flash Marshmallow 30B stock ROM yesterday, so I was told to install a few files. New system file, new modem file, new boot file and SuperSu BETA v2.65. I tried and tried many times yesterday, but unfortunately it didn't work. So I was like "okay fine, let's just use some custom ROM from XDA."
I chose the XenonHD 6.0 Experimental ROM and copied into my internal storage along with my gapps they recommended. I booted up into recovery mode, backed up the installed ROM and factory reset it. I went to flash my ROM first then my gapps. But then halfway flashing the log display showed this:
HTML:
unmount /system failed: No such volume found
updating partition details...
Then it ended saying it was successful and it continued on flashing the gapps and so on. Surprisingly no "unmount /data failed or anything, just the system that is acting up. After finishing flashing all the file, I went to reboot my device. At first it showed the LG logo as usual, then the screen became black. I went online and search all about this unmount system problem, and all they say is that I have to wait for about 10 minutes then the Android logo will come on. So I waited for 15 minutes? (I have an iPad mini beside me counting down the minutes). I came back the whole phone is still black screen, the whole screen is turned off, not idle blank screen. I started to freak out and I took out the battery and put it back again and went into recovery mode.
2) Another problem is this IMEI number loss, I don't know how I got lost this information. I'm not sure if my EFS file is corrupted or not. I realized it because I was receiving no cell signal while I was in the city central. Unfortunately I don't have a backup of the EFS file ( I don't even know if I have it ).
Please help me solve these problems. It's happened for a few days now.
Click to expand...
Click to collapse
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
I don't quite know how to do it though but I've been thinking about unbricking my phone and restoring to factory state and start all over again. Do you mind posting a link for the instruction on how to do all this? Thanks
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
KronicSkillz said:
i don't claim to be an expert in this field, but there are two things that come to mind that you could look into, maybe ask more experienced ppl on those threads.
it sounds like some sort of partition problem, or corrupt data, maybe you flashed a bad file or a file for another rom.
you could try manually formatting drives in command terminal without mounting them
also unbricking might work too but if your hopes and dreams are in this phone then talk to someone who knows more than me because i wouldn't bet my bankroll on these just suggestions for you to look into. I feel like the guys that write those guides probably can answer your question better and with more confidence.
Click to expand...
Click to collapse
mimivg said:
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------
I have the same problem,and i resolve it,try this
http://forum.xda-developers.com/lg-g...ables-t3282012
Click to expand...
Click to collapse
This was the ROM I initially wanted to flash. I think something went at flashing the Modem causing my phone to have this unmount /system problem.
Hi guys,
Until last night my Samsung galaxy note 2 phone was working perfectly. The battery went to 1% and i kept the phone in charging attached to my power bank as usual. This morning I woke up to a phone which had all sorts of alarming colours and messages flashing across the screen saying wipe cache wipe data/ factory reset, reboot, failed to mount /efs invalid argument , failed to mount /data invalid argument. After consigning to the fact that data loss is an inevitability,i went about with factory reset which only removed the unable to mount /data error, the /efs error invalid argument still persists. The phone still bootloops. This is coming from a guy who never ever heard of custom ROMs let alone rooting before this problem, thanks to Google. The phone is stock.
Now my request is this: please help me bring my phone in working condition.
Help me root it.
Help me install the best custom ROM.
Thank you.
BTW this incident has taught me the usefulness of the idea of phone backup.
Request help at the earliest, someone :crying:
Hello and good evening,
you may try restoring your IMEI with reading this guide:
[TOOL] Backup & Restore EFS (IMEI) for Samsung Galaxy Note 2 GT-N7100 / S4 GT-I9500
If you have any questions, feel free to ask.
Kind regards
Trafalgar Square
It says that my phone must be rooted,but its not. What should ido now.
arun-iball said:
It says that my phone must be rooted,but its not. What should ido now.
Click to expand...
Click to collapse
this is to update guys that I was able to successfully root my phone and install twrp recovery, now I am facing the problem that I don't have a backup of my efs folder. Do I need it for the script to run?
How do I restore my efs without any backup?
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here
issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?
Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again
update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..