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?
Related
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
MidwestEmo4Ever said:
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
Click to expand...
Click to collapse
Unfortunately after doing a quick search it looks like many people who have a problem very similar to yours had to send the phone in for servicing.
WangLung said:
Unfortunately after doing a quick search it looks like many people who have a problem very similar to yours had to send the phone in for servicing.
Click to expand...
Click to collapse
yeah thats what it looks like. I guess my only question now would be is there any way to salvage the media thats on my internal sd? photos/music stuff like that?
MidwestEmo4Ever said:
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
Click to expand...
Click to collapse
It's not bricked just reflash using odin or cwm back to stock
Sent from my SGH-T989 using Tapatalk
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.
Hello, this is my first post. First off thanks to the entire community for this wonderful forum and the ability to ask questions like the following here .
Phones background information: In my spare time I attempt to fix phones for family and friends. I recently received a sm-n910a (att note 4) that was on stock 4.4 kitkat and did (does) not have an active at&t mobile plan. Its function is to be used as a wifi phablet for web surfing/games and the user was interested in upgrading the Android system to 6.0MM if possible as well as SIM unlocking the phone for a future Straight talk prepaid plan.
1. Without full-root I was unable to make a complete backup initially but owner wasnt worried about a complete data wipe so I didn't think it would be a problem. (Dumb mistake I know now )
2. Used Odin to flash stock Android 5.1.1
3. Used Kingroot and/or Kingoroot to temp root. Pretty sure it was Kingroot, but not positive.
4. Used Z3x box program to simunlock (was successful)
5. Made complete backup using ADB
6. Downloaded stock 6.0 updates from xda forum post and loaded on sd-card.
7. Entered recovery to update to 6.0 but found errors:
E: failed to mount /efs (invalid aurgument)
DM verity verification failed // Did not display anything about the drk like other people mentioned online.
8. Used Z3x box program to wipe efs (was successful)
9. Entered recovery to check errors and the E: failed to mount /efs was gone
10. Researched online about Dm verity verification failed as much as possible and used the solution to wipe cache, wipe user data, flash stock 5.1.1 rom again, wiped cache agian.
11. At first startup the recovery system lets me access sd-card content and I can select the update file but as soon as it is done and attempts to update, fails with dm-verity problem immediately, and dm-verity verification failed persist after any reboot or wipe until I reflash.
12. After multiple attempts to reflash kitkat problem still persist and with the locked bootloader I am at a loss as to what to do next to rectify the problem.
Any help or suggestions would be greatly appreciated. I hope I posted in the correct forum thread. Thanks agian in advance. -CM
Nobody has any advice for me
Lol, just checking back in agian. Nobody has any suggestions or similar experiences with a situation like this. Any feedback is appreciated. Thanks agian in advance. -CM
perplexive said:
Lol, just checking back in agian. Nobody has any suggestions or similar experiences with a situation like this. Any feedback is appreciated. Thanks agian in advance. -CM
Click to expand...
Click to collapse
I have thé same problèm . But i have thé bootloop After flash Rom.do you have thé solution of your situation? Help me with it if you have.t hank
that requires you to do some modification
don't try it
i know this may seem off topic
but can you help me with something?
Hello.
For months I've been trying to get my Tab 3 to get rooted, I never had a chance with it until it's battery finally gave out. I've just revived it via new battery and now I'm just stuck.
/efs partition is damaged, no matter how many times I flash a stock firmware, it can't be restored. This specific tablet is from T-Mobile I believe. Is there anyway I can restore the tablet back to normal? Please?
I curse this error message so much as it's been haunting me these many months, I'd very much want to solve this but mind you this is my first time ever using these forums for help though!
I'm willing to rebuild it from ADB if it's ever possible.
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
File Based OTA
Supported API: 3
MANUAL MODE v1.0.0#
Sucessfully verified dmverity hash tree
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
E:Failed to clear BCB message:failed to find /misc partition
Click to expand...
Click to collapse
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Hir0xM said:
Hello.
I was fiddling around with my phone today and wanted to clear the cache from the Recovery.
After rebooting tho it showed me a message (note that I never toggled OEM unlock or even accessed recovery/download mode or anything before today):
And after a minute or so the Recovery showed up. I went to delete the cache, all went well until I was met with the same message at the end:
Should I worry about anything ? The phone booted normally but I'm a bit skeptical about that error (maybe the cause of my as of late noticeable battery drain ?) and any help is appreciated!
EDIT: Another thing to notice is that when booting into recovery, it seems the phone is trying to install an update which isn't there, and only then takes me to the recovery menu.
Click to expand...
Click to collapse
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
SnowFuhrer said:
Everything you said I think is normal. So don't worry about it. It still clears cache or whatever you do.
Click to expand...
Click to collapse
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Hir0xM said:
I see, thank you
It's a weird bug so that's why I was worried. I did read some reports that some users couldn't wipe data due to this in the Recovery and it got me a bit worried.
Let's hope it's just a stupid bug and nothing more. Thanks again!
Click to expand...
Click to collapse
No problem. Report if it doesn't work.
SnowFuhrer said:
No problem. Report if it doesn't work.
Click to expand...
Click to collapse
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
UmangA said:
Hi there
I have this issue. I cant factory reset the phone as it says MDM does not allow this.
so I used odion to reload the Stock Firmware on these but now I have FRP on this.
as it's a work device & dont know the user that last used this phone.
even after the flash I still have bcb message
Is there any other way of sorting this out.
Click to expand...
Click to collapse
When you get into work phones, things get really ugly. Can you wipe data by flashing just csc in Odin?
Similar problem with S7, it just keeps rebooting
I have an S7, I have the same problem, the phone started freezing and rebooting every minute. So decided to Wipe out the cache and do factory reset, saw this message "E:Failed to clear BCB message:failed to find /misc partition"
The phone never goes past the Galaxy S7 Android logo screen most of the time, if it did manage to go pass, it freezes after 2 to 3 mins and reboots.
So I tried and successfully rooted, installed TWRP, took a backup and tried to wipe cache, it failed.
formatted the and tried to restore from backup and it failed, as it never went pass the S7 logo screen.
so I tried Lineage OS 17 and it worked like a charm
then tried back to Android 9 ROM from Samsung, it too started to hang and freeze - If it was an Hardware issue, I would expect Lineage OS to freeze too.
I think and it looks like Samsung is forcing its customers to buy new phones .....
Please help
thanks
Z
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call aler
How to fix Galaxy J7 prime texting or calling issues: not receiving text or call alerts?
My phone is Samsung galaxy j7 prime
when I factory reset it show me this error E:Failed to clear BCB message: failed to open /dev/block/platform/13540000.dwmmc0/by-name/MISC: No such file or directory
Galaxy tab A 8
Even without appearing to have any hardware problems, my galaxy tab shows exactly the same messages described above and the same situations. I suspect it is even programmed obsolescence. Would anyone have any reliable tutorial on how to reset it completely and install a rom that was stable and compatible? Thank you :fingers-crossed::fingers-crossed:
Exactly the same problem
Hi guys,
I exactly do have the same problem. I upgraded from LineageOS 16 (which was working smooth.y ) to LineageOS 17.1 and faces a problem wit IMEI, So I tried to revert back to Stock ROM, flashed via ODIN latest version.
I could flash the stock ROM (doing NAND Eras and Re-Partition due to Vendor partition). But after reboot, the ROM won't boot and stuck with SAMSUNG screen blinking.. I managed to access the Stock Bootloader and could do a full factory reset, but I still get the error message like above.
If anyone has an idea how to solve...
My sister had many randomly chrashing apps and ask me how to fix it.
In recovery the same message was printed. BCB and /misc ...
Well I tried to clean install stock rom (A5 2017) with odin, but the user data was never deleted ... Don't know how to use odin ...
I have then flashed lineageos and now there are random reboots and apps are only crashing sometimes once opened.
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Anyone knows what causing these? And if they are still related to BCB and/or /misc?
houston_ said:
I attached a crash log. The app crashin is called antennapod (https://play.google.com/store/apps/details?id=de.danoeh.antennapod&hl=de&gl=US)
Click to expand...
Click to collapse
Somehow tha attachment was delincined.
Log_2020-12-01_21-40-15.txt
drive.google.com