Related
Hi all,
i've search and tried most of the methods on threads with similar issue but to no avail.
So i'm posting my situation here hoping someone with the expertise can help me.
My IMEI became null/null after flashing Criskelo rom. I had previously saved a copy of my efs.img on my PC.
When restoring my EFS backup, it says "/dev/block/mmcblk0p3: write error: No space left on device"
So i used Odin, flash a stock ROM with pit, bootloader, pda, phone and csc.
The flashing was successful with no errors but stuck samsung logo for as long as i can wait.
I then booted to stock recovery and notice it says "E: failed to mount /efs (invalid argument)"
so i did a wipe data/factory reset and wipe cache partition.
Reboot. Still stuck at Samsung logo.
I tried to sideload my efs.img but there is a "E: signature not verified" error
So i thought what the heck and flashed Chenglu's CWM via Odin. Phone successfully boot to CWM
i wiped data/factory reset, cache and dalvik. Reboot and still stuck at Samsung logo.
I then tried flashing CF-Autoroot, it was ok as well with no issues but stuck at Samsung logo again.
Rebooted back to CWM, Tried to mount efs, got an error saying error mounting efs
i flashed various stock rom via Odin, all process PASS with green but mostly stucked at samsung logo...
is my device soft bricked? or is my sd card is dead? or is my efs partition fried?
anyone kind enough to share his complete backup file? my country sells the n7105.
i bought the export n7100 instead so its kinda hard for me to find a friend with the same fone.
i have been flashing roms since the good old Galaxy S and this is the 1st time i cannot revive my phone from past experience...
bump for you, im facing the same error.
Hi mate, im not sure if this would work but have you tried the super wipe mod here http://forum.xda-developers.com/showthread.php?t=1925402.
worth a shot cant make it any worse.
also checkout this for a solution http://forum.xda-developers.com/sitesearch.php?q=E: signature not verified
Hi thanks... sadly links are down. will try the super wipe thing.
i remember doing the wipe in TWRP before flashing Criskelo.
i did get away with the signature thing. its easy. just turn it off in CWM.
i went to my local samsung service center and they rejected my phone as its considered "export" to them
did the super wipe.
Flash stock with Odin.
Still keep getting stuck at samsung logo on boot and recovery still shows : Error: Can't mount /efs
cant you restore it to factory settings and return it to where you bought it from.
GezDixon said:
cant you restore it to factory settings and return it to where you bought it from.
Click to expand...
Click to collapse
mine is under warranty, so I could try to restore to stock rom which gets stuck at the samsung logo.
problem is that going into download mode shows this :
custom binary download : 12
Current binary : samsung official
system status : custom
iv had alook round and cant see anything that will fix it, in odin theres a clear efs button.
edit: just found this info on a usb jig that resets counter to 0
http://forum.xda-developers.com/showthread.php?t=1934771
how do I go about clearing the EFS since it is greyed out.
so there's no work other solution to this, except for getting the jig?
likepeas said:
how do I go about clearing the EFS since it is greyed out.
so there's no work other solution to this, except for getting the jig?
Click to expand...
Click to collapse
Edit the ini file for Odin and set PhoneEFSClear=1 that'll check the EFS Clear option (even though it remains grey). See if that helps.
likepeas said:
mine is under warranty, so I could try to restore to stock rom which gets stuck at the samsung logo.
problem is that going into download mode shows this :
custom binary download : 12
Current binary : samsung official
system status : custom
Click to expand...
Click to collapse
same. my counter is 15
but i already ask a friend in malaysia to help me with samsung service center malaysia this weekend
i don't have the phone now. hope they don't nitpick on the counter thing
i got the same problem
xenocide976 said:
Hi all,
i've search and tried most of the methods on threads with similar issue but to no avail.
So i'm posting my situation here hoping someone with the expertise can help me.
My IMEI became null/null after flashing Criskelo rom. I had previously saved a copy of my efs.img on my PC.
When restoring my EFS backup, it says "/dev/block/mmcblk0p3: write error: No space left on device"
So i used Odin, flash a stock ROM with pit, bootloader, pda, phone and csc.
The flashing was successful with no errors but stuck samsung logo for as long as i can wait.
I then booted to stock recovery and notice it says "E: failed to mount /efs (invalid argument)"
so i did a wipe data/factory reset and wipe cache partition.
Reboot. Still stuck at Samsung logo.
I tried to sideload my efs.img but there is a "E: signature not verified" error
So i thought what the heck and flashed Chenglu's CWM via Odin. Phone successfully boot to CWM
i wiped data/factory reset, cache and dalvik. Reboot and still stuck at Samsung logo.
I then tried flashing CF-Autoroot, it was ok as well with no issues but stuck at Samsung logo again.
Rebooted back to CWM, Tried to mount efs, got an error saying error mounting efs
i flashed various stock rom via Odin, all process PASS with green but mostly stucked at samsung logo...
is my device soft bricked? or is my sd card is dead? or is my efs partition fried?
anyone kind enough to share his complete backup file? my country sells the n7105.
i bought the export n7100 instead so its kinda hard for me to find a friend with the same fone.
i have been flashing roms since the good old Galaxy S and this is the 1st time i cannot revive my phone from past experience...
Click to expand...
Click to collapse
plz help im doing factory restet with odyn and evrey stock firemwere from difrent country doesnt worck. the phone is stoping on samsung logo ,i can instal custum recovery by odin but , after instaling in custum recovery omega 7.2 or cm10 the phone is not boting its stoping on first boot animation plz help, sorry for my bad eglish
i have the same problem ????
same here
Has anyone found a solution to this yet?! I have the exact same issues, phone died, then when powered back on was stuck in a boot loop, returned to stock and got the unable to mount efs invalid argument text, now its still stuck in a boot loop with a flash count of 8 so cant be sent in for repair, any advice is greatly appreciated!
I have the exact same problem
i have the same problem . . and to make matter worse i don't even have any warranty . . :crying: . ..
is there no way to to get the phone to boot in to the OS regardless of any functionality ??
I couldn't find the topic where i learned this info, but it's something like this: if you flashed the modem (i think so) and you have an EFS backup like me, you just need to flash any other thing and restore the EFS backup. But, if you don't, you must stay with the modem.
okay, i just found it: http://forum.xda-developers.com/showthread.php?t=2332913
Good luck. (And press the thanks button if i've helped you :fingers-crossed: )
Enviado de meu GT-N7100 usando o Tapatalk now Free
same problem, korean note 2
lost my IMEI, no EFS back up , cant detect internel storage ( SD card works though )
i have access to DL mode, i can flash recovery , but stuck in boot loop for flashing ROM
blueazure said:
same problem, korean note 2
lost my IMEI, no EFS back up , cant detect internel storage ( SD card works though )
i have access to DL mode, i can flash recovery , but stuck in boot loop for flashing ROM
Click to expand...
Click to collapse
Seem to have been struck by the same issue and no efs backup prior to this.
Custom binary download: 0
Completely stock Note 2 just got screwed after flashing new 4.4.2 ROM for my country via Odin, the ROM booted fine, transferred contents to PC, factory reset the phone, set google account and reinstalled apps and transferred saved data back. Data, phone calls and everything else was working. The phone got to 10% battery lost network (this is normal lately lol) and shut off when battery died. Phone never rebooted and stuck at Samsung logo. Recovery reports "/efs I/O mount error" tried the guides by ketan and a couple others nothing seems to help
same applies to me. Perhaps some hardware fried is my guess.
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
mrcpu said:
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
Click to expand...
Click to collapse
The other weird thing is that I used odin 3.06 to flash twrp 2.8.5, or at least attempt to, download processed, device reset, but recovery is still CWM 6.0.4.3. WTH?
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Bajanman said:
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Click to expand...
Click to collapse
Correct, it is an AT&T. I have tried the options in that thread, but I swear, nothing I flash actually "sticks". I've used odin 3.06, put the files in PDA, plugged it in in download mode, the progress bar appears on both odin and the phone, it resets, it reboots, and nada. Hung.
I can't even flash a replacement recovery, nothing "sticks". I've used KIES to flash, it tells me it's successful, but I still have CWM 6.0.4.3. I've tried the original 4.1.1, NJ1 (rooted), I've tried flashing a bootloader, then tried the one with the param file attached, I downloaded a pit file, followed the directions on that page with the Re-partition option, and I still can't get anywhere with it.
If I cold even just get a different recovery installed, just so that I *know*, my odin is OK, then I'd feel better about making progress.
I've tried to flash philz_touch 6.48.4, openrecovery-twrp-2.8.5 through odin, and I can't even get the CWM recovery replaced. Odin reports success, reboots the device, frozen.
I swear, if this was one of my servers at work, I'd figured the NSA has hacked the firmware to just discard writes and report back success.
I'm not crystal clear in ODIN how to flash bootloaders, on one hand, presumably, the "bootloader" button, but one guide shows the bootloader file being put in PDA, so who knows. I may have ended up with a bootloader mismatch, but I thought flashing the latest stock recoveries.
FWIW, the phone was running Dirty Unicorn, although I'm unsure of specifically which version, she's had it for a while.
Thanks for any help.
Just realized something.
If I hold down the power/vol down/home and boot into download mode, I get the little red "odin mode" at the top left, 4 lines of text about custom, etc, and then the green android icon.
If I boot into recovery, then use it to boot into download mode, the green android is there, but none of the text (odin mode, etc) is on the screen. Is this normal?
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
have you tried all this using the same computer and usb cable? i would try a different computer, port, usb and re download all files again. perhaps use a different version of odin. good luck:fingers-crossed:
It's the same computer and cable I do my Note 3, and kindle fire 8.9, and with a different cable my nook HD, so I'm skeptical that it's any of those pieces, but for the heckuvit, I will try a different one.
Note 2 GT N 7100 --Stuck on CWM 6.0.4.3
gizhola said:
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
Click to expand...
Click to collapse
Dear friends, sorry for my interference, i having CWM recovery v 6.0.4.3 on GT N7100, i used to flash omega ROM 4.3, everything went well until i got stuck on Samsung log and the phone did want restart, i decided to go on CWM recovery, stunned with this message
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
Still I can go on download mode, I tried use odin to flash stock rom but failed it takes me always to CWM v 6.0.4.3 where it stuck and dont allow me to format or do any thing except my external sd1 that I tried to flash from but returned to same prob ( CWM v 6.0.43)
also I tried to flash tried twrp 2.8.0.4 but failed
the prob is my internal sd can't be mounted and whatever i do don't pass
I read in your post something about flashing auto root in odin or fix CWM root
can you help please Im stuck in CWM v 6.0.4.3
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
Is my phone bricked for real ?
I had installed rom from http://forum.xda-developers.com/note-2-tmobile/development/rom-t3324244 and it was working fine. Yesterday after a call it went into Bootloop and I had to perform factory reset to get it out of the state.
Today again after a call, my phone went to boot loop but this time I saw that the apps were getting optimized and would begin the bootloop on every reboot.
Went to TWRP and tried to perform a simple cache wipe and I get a lot of "Error opening: '/data/data/com.android.*.* (I/O error)"
Data wipe is also not able to recover the situation nor is a zip installation of the same rom.
So any steps possible here ?
Only way to fix this was to lose all the data I had. Odin saved my phone and I had to flash the whole ROM through it and got it back to normal.
Even the Nandroid restore failed as the Advanced Wipe was failing every time.
Not sure how these I/O errors even came up in the first place.
Okay so I am sort of a Nob, I rooted my phone, my SM-N910P. I was attempting to put a customized firmware in and it turned off went to restart and then stopped. It now won't get past the Sprint Logo and that is after about half an hour.
I have tried to factory reset with no avail, I have tried to clean partitions and still nothing.
I have tried to use several different firmware all come up with some error. The most recent error I am getting is " sw rev check fail fused 4 binary 1 "
Please any help would be great. Also this phone has a bad ESN / Black listed I was only using it for lack of better thoughts is a tablet.
Please Help...
Maybe what you flashed wasn't compatible and cannot boot.
Without knowing what stock update you started with and what you flashed in recovery, hard to say.
But since a factory reset won't boot, you likely need to Odin the stock tar and start over. But try something else first; IIRC, that binary issue may be caused by mounting system (maybe you wiped system?) and not unmounting prior to flash. Also, if you checked an option to verify zip, you should uncheck that. It's possible that it won't boot cause you've wiped system and failed to flash a ROM successfully.
Try this: If you wipe system, either reboot recovery before flashing or unmount system. Newer security requires system unmounted.
Sent from my SM-N920P using Tapatalk