[Completed] Samsung Galaxy Note II stuck on bootloop - XDA Assist

So, here's the full details. I tried to increase the ram of my Note II even if its kernel does not support swap because I saw a thread here that will help me increase my ram even if my kernel is not compatible with swap. It didn't work so I uninstalled all the apps required to do it (Swapper2, Terminal Emulator) then it suddenly restarts then goes bootloop. Then I installed a custom rom (CM 0.14) changed my kernel to AGNI but still, bootloop. Then I decided to go back to stockrom by flashing it through odin then still stuck on bootloop. I tried to wipe data/cache after flashing and this is what it showed me:
-- Wiping data...
Formatting /data...
E:failed to mount /efs (Invalid argument)
Formatting /cache...
Data wipe complete.
I followed the steps required to flash the stock rom but I'm still stuck on bootloop. Can you help me what to do? Thanks!

canega2596 said:
So, here's the full details. I tried to increase the ram of my Note II even if its kernel does not support swap because I saw a thread here that will help me increase my ram even if my kernel is not compatible with swap. It didn't work so I uninstalled all the apps required to do it (Swapper2, Terminal Emulator) then it suddenly restarts then goes bootloop. Then I installed a custom rom (CM 0.14) changed my kernel to AGNI but still, bootloop. Then I decided to go back to stockrom by flashing it through odin then still stuck on bootloop. I tried to wipe data/cache after flashing and this is what it showed me:
-- Wiping data...
Formatting /data...
E:failed to mount /efs (Invalid argument)
Formatting /cache...
Data wipe complete.
I followed the steps required to flash the stock rom but I'm still stuck on bootloop. Can you help me what to do? Thanks!
Click to expand...
Click to collapse
Greetings and welcome to xda, first can I ask if you have a back up of your efs folder ? I don't think you will need it but just in case. If you boot into download mode and connect to kies/smart switch and select emergency firmarew recovery you should be fine. It sounds like you need to install a pit file which this will do, alternatively you can just flash a stock rom through odin that contains a pit file or I think mskips toolkit has a pit file
Good Luck
Sawdoctor

sawdoctor said:
Greetings and welcome to xda, first can I ask if you have a back up of your efs folder ? I don't think you will need it but just in case. If you boot into download mode and connect to kies/smart switch and select emergency firmarew recovery you should be fine. It sounds like you need to install a pit file which this will do, alternatively you can just flash a stock rom through odin that contains a pit file or I think mskips toolkit has a pit file
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Thanks for the response! Unfortunately I don't have any backup efs folder. Gonna try those 2 methods you mention and will reply here if something happens; thanks!

So, I've tried all the methods and none of them worked for me. This is what happened:
First, I tried to do emergency firmware recovery method but its stuck on connecting even after I updated to latest drivers. Some says that its skies problem I did the second option. I search for GT-N7100 pitfile on xda which is 3kb in size and flashed it using odin together with the md5 file and this is what it looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The flashing process is completed. I wiped the data/cache as usual but same results. Did I do it wrong?

canega2596 said:
So, I've tried all the methods and none of them worked for me. This is what happened:
First, I tried to do emergency firmware recovery method but its stuck on connecting even after I updated to latest drivers. Some says that its skies problem I did the second option. I search for GT-N7100 pitfile on xda which is 3kb in size and flashed it using odin together with the md5 file and this is what it looks like.
The flashing process is completed. I wiped the data/cache as usual but same results. Did I do it wrong?
Click to expand...
Click to collapse
After flashing the pit file did you try flashing a stock rom through odin or kies emergency firmware recovery again ?

sawdoctor said:
After flashing the pit file did you try flashing a stock rom through odin or kies emergency firmware recovery again ?
Click to expand...
Click to collapse
Yes I did through odin only since kies always stuck at connecting then becomes unresponsive. And as I said, I flashed the pit file together with md5 from stock rom. Same results. I checked the version of pitfile which is the international one and I'm still stuck on bootloop.

canega2596 said:
Yes I did through odin only since kies always stuck at connecting then becomes unresponsive. And as I said, I flashed the pit file together with md5 from stock rom. Same results. I checked the version of pitfile which is the international one and I'm still stuck on bootloop.
Click to expand...
Click to collapse
If kies emergency firmware recovery and mskips toolkit do not work then I'm afraid I am out of ideas. If you ask in the note 2 forums here
http://forum.xda-developers.com/galaxy-note-2/help
Hopefully the experts there may be able to think of something
Hope you figure it out
Sawdoctor

I'm always redirected to wheretowatch.com whenever I click a link

So, after a lot of murmuring I finally identified the root of the problem: the efs. This guide helped me fixed the problem:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
After I input the command on ADB, what I did was wipe data/cache and mount/efs then reboot. This method fixed E: failed to mount /efs Invalid Argument error. Thanks for all the help!

canega2596 said:
So, after a lot of murmuring I finally identified the root of the problem: the efs. This guide helped me fixed the problem:
http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
After I input the command on ADB, what I did was wipe data/cache and mount/efs then reboot. This method fixed E: failed to mount /efs Invalid Argument error. Thanks for all the help!
Click to expand...
Click to collapse
Thats great news, I'm glad you fixed it so I'll close this up
Regards
Sawdoctor

Related

[Q] Problem returning to stock after using lagfix. Errors in stock recovery utils.

I've been trying to get my phone back to stock for a day or so now.
Originally I flashed the PeanutButta Jelly Time voodoo fix kernel (let it format), then applied the sdcard fix. I was having problems with the market force closing and it was impossible to install new apps after applying these.
I decided I would try and go back to stock. I went into CWM recovery and selected disable lagfix, rebooted.
I then tried flashing back to stock using the PSTLite method. Phone bootloops and splash screen does not make any sound. If I boot into recovery I see:
E:Can't mount /dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount dev/block/mmcblk0p3
(Invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount dev/block/mmcblk0p3
(Invalid Argument)
If I reflash CWM using ODIN and apply the lagfix kernel I no longer see errors in recovery. The phone makes the droid sound during boot and I make it passed boot but every single app force closes before anything actually starts up. After the everything force closes the phone hard reboots.
The fact that I can only get passed the splash only using a lagfix kernel makes me think that lagfix wasn't disabled properly? I've heard the voice come on during boot saying "lagfix disabled" but it doesn't seem to be the case.
I've tried all the methods mentioned to try and get back to stock. PSTLite, flashing ED1, ED2 with Odin etc. All ends up back in this state. When in recovery after going to stock I've tried clearing all the data, the command says it suceeds but I still see mount errors similar to those posted above.
Any help would be greatly appreciated!
I had a similar problem with /data partition not mounting.
I used the SamsungPST Lite with the full restore ODIN here:
http://www.mydroidworld.com/forums/...harge-full-factory-tar-flashing-software.html
In addtition, I had SamsungPST Lite repartiion using the PIT file from this thread:
http://forum.xda-developers.com/showthread.php?t=1111486
I'm pretty sure you need to repartition to fix the problem. I determined this by doing some digging in the fascinate forums.
To get rid of lagfix completely IMNUTS says to do this
Create the file /sdcard/voodoo/disable-lagfix and reboot. Voice should come up stating lagfix is being disabled (similar to it being enabled).
Thanks for the tips guys but still no dice.
I already had the disable lagfix file created in the folder but that wasn't helping. I tried flashing the PIT along with imnuts' MD5 files in that thread but still having problems.
If I run a vodoo kernel I can boot into the OS, but again hit with all sorts of immediate force closes.
Returning to stock still gives me the same errors mentioned in my OP.
Anyone have anything else to try?
If you flash either the ED1 or ED2 full Odin packages that are available, along with the PIT file, it should fix your problem. Be sure to check the box for Re-Partition when flashing the full Odin file with the PIT file.
Everytime the phone reboots I get the robot voice and it goes through its thing and eventually says "Voodoo lagfix is now disabled". After hearing the success voice the phone stays stuck on the Samsung screen. When rebooting it tries to disable again (making me think it never disabled in the first place).
If I try to boot into recovery after lagfix being disabled it just ignores me and I hear the robot voice trying to disable again. This is making me think that the lagfix is never getting disabled even though it reports disabled.
After it said it supposedly disabled lagfix I tried to flash a non-lagfix kernel which said it worked. Then rebooted and chose a stock.zip to flash and still doesn't work. Is there any definitive way for me to get rid of lagfix? This feels like the problem to me.
Tried ODIN again with the .PIT file, ED1 with re-partition checked. Passes ODIN with no problems. Phone bootloops on droid logo (no droid sound).
Already tried the 3 packages mentioned in your other post about the .PIT files (SamsungChargeFull, almost everything, factory_reset).
Still get the same errors mentioned above in recovery blue recovery mode.
When trying to do a factory reset it formats data, dbdata, cache, but then spews the errors about mounting.
Feels like its still on the wrong FS.
Use one of the full odin packages, not the files linked to in that post. Your options are either ED1 or ED2. I've also updated that post. If you aren't flashing a partition, then it will not be reformatted properly, and the packages listed in the CWM fix post initially did not flash everything like the full Odin packages do.
I would use the ED1 full Odin, ED2 kept giving me errors and noticed it did for others as well.
As I said in my post, flash ED1 full package with samsung pst lite
Sent from my SCH-I510 using Tapatalk
Same issue here have tried ee4, ed1, ed2, ect.. along with pit and no go. Made sure it was on re-partition and have also tried samsung's pst as well.
Any suggestions?
did you try with battery in during flash?
I had issues as well and it finally worked only after I flashed the 2.2.1 Stock Odin with PIT and put the BATTERY BACK IN during flash. not sure why that makes a difference, but it did.
H3Dude said:
I had issues as well and it finally worked only after I flashed the 2.2.1 Stock Odin with PIT and put the BATTERY BACK IN during flash. not sure why that makes a difference, but it did.
Click to expand...
Click to collapse
Yeah have flashed it with and without battery. Neither worked.
EDIT: Just ran a flash with the pit file and 2.2.1 with battery in again, still no go.
Alright so i went and tried and flashed humble 1.42 since i hadn't tried a gb rom. It booted up, but throws so many errors i can't do anything, then it restarts. I feel like I am getting closer.
Any suggestions from here?
Wipe all data in cwm, then use the stock Odin with the pit file to repartition your phone.
Sent from my Droid Charge running GummyFroyo 1.9.1
No longer boots now and goes straight to cwm.
Frustration is setting in >.<
Alright here is a pic of what i get right after odin or the samsungpst flash using pit and any of the stock builds
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If i reboot it goes to the bootloop at the droid charge animation. Same if i clear chase and/or wipe data.
Any help is appreciated. I don't want to give up just yet. Just need some help.
Make sure it is being run as an administrator if you are using windows vista or 7. I also had the same errors with the full stock odin images but its because it was in run in admin mode.
moondrius said:
Make sure it is being run as an administrator if you are using windows vista or 7. I also had the same errors with the full stock odin images but its because it was in run in admin mode.
Click to expand...
Click to collapse
Running it on my xp laptop. Is that the issue? Should i be running it on windows 7.
If so i'll give it a go on my desktop.
I don't feel like that should be an issue, but I am willing to try anything at this point.
No xp should be just fine. I know there have been issues with laptops and odin so you might want to try the pc instead.

[SOLVED]Stuck on JB samsung logo and CWM logo

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been running the deodexed UCMC1 with stock kernel until i got my replacement batteries today.
Turns out they had a different model # (EB585157VK, SERIAL AAaD702QS/5-B 2013.07.02) and were slightly thinner then the stock battery (the seller had a skyrocket one pictured on ebay).
Anyway they seem like legit OEM.
I get all stupid and exited to have new batteries and instead of powering off the phone from the menu i just pull out the stock battery and insert the new one. :highfive: (cynical mental highfive)
Phone is now stuck at above samsung logo and cwm only goes as far as the logo and version number, no menu no nothing.
I've read about the same problem someone had with an S3 mini here.
Will odin help me?
Maybe, have you pulled the battery, let it sit for a few minutes and put the old battery in?
Edit, this might be of interest http://forum.xda-developers.com/showthread.php?p=42749682
jd1639 said:
Maybe, have you pulled the battery, let it sit for a few minutes and put the old battery in?
Edit, this might be of interest http://forum.xda-developers.com/showthread.php?p=42749682
Click to expand...
Click to collapse
Yes, it didn't help.
I've tried flashing the Rogers JB rom and an old CWM in odin.
The old CWM worked but doesn't find the internal SD. When I mount the USB from CWM to PC the internal SD is shown in windows explorer but it's grayed out while the external SD is accesible like it is in CWM.
I tried flashing CWM touch 6.0.3.3 from inside old CWM and it flashed fine but it stops booting at the CWM logo again..
The Rogers rom flashes the glowing samsung logo and the screen turns black..
lingowistico said:
Yes, it didn't help.
I've tried flashing the Rogers JB rom and an old CWM in odin.
The old CWM worked but doesn't find the internal SD. When I mount the USB from CWM to PC the internal SD is shown in windows explorer but it's grayed out while the external SD is accesible like it is in CWM.
I tried flashing CWM touch 6.0.3.3 from inside old CWM and it flashed fine but it stops booting at the CWM logo again..
The Rogers rom flashes the glowing samsung logo and the screen turns black..
Click to expand...
Click to collapse
Mohan had a zip that restored the pre-load partition. You might give that a try.
all this because you pulled out battery while phone was on, sh*t, ive done it many times w/out issues but wont be doing it anymore
did you try booting with the old battery
when you flashed firmware w/odin did you reset/wipe b4 booting into rom
try flashing twrp w/odin then reset/wipe b4 booting into rom
jd1639 said:
Mohan had a zip that restored the pre-load partition. You might give that a try.
Click to expand...
Click to collapse
Thanks i will. Do you know if it's possible to swap the internal sd for another one?
vincom said:
all this because you pulled out battery while phone was on, sh*t, ive done it many times w/out issues but wont be doing it anymore
did you try booting with the old battery
when you flashed firmware w/odin did you reset/wipe b4 booting into rom
try flashing twrp w/odin then reset/wipe b4 booting into rom
Click to expand...
Click to collapse
Old battery didn't help.. After odin I didn't wipe b4 boot :silly:
I'll try TWRP too.
lingowistico said:
Thanks i will. Do you know if it's possible to swap the internal sd for another one?
Click to expand...
Click to collapse
Afaik, the internal is soldered on.
jd1639 said:
Afaik, the internal is soldered on.
Click to expand...
Click to collapse
It's fine though, old CWM 5xxx shows install zip from SD and install zip from internal SD and it's the opposite in new CWM. So it turns out SD is fine, phew Problem is i think it looks for backups only on external so i can't access my backup.
mohans preload fixer didn't help.
I'll try TWRP now.
Wipe in old CWM didn't help but it did in TWRP!!! Thank you Vincom i bow to you in gratitude. :highfive::laugh:
It said it couldn't find E:\android..but formatting went fine.
Booted up to Rogers JB but gallery and phone crashes in background of welcome wizard.
But i flashed the preload fix in between all of this.. so it was probably because of that.
Flashed Rogers JB from Odin again and now it works!
Next time I will turn phone
Good to hear you got it working again
lingowistico said:
Wipe in old CWM didn't help but it did in TWRP!!! Thank you Vincom i bow to you in gratitude. :highfive::laugh:
It said it couldn't find E:\android..but formatting went fine.
Booted up to Rogers JB but gallery and phone crashes in background of welcome wizard.
But i flashed the preload fix in between all of this.. so it was probably because of that.
Flashed Rogers JB from Odin again and now it works!
Next time I will turn phone
Click to expand...
Click to collapse
when flashing stock and having boot up problems and such, resetting and wiping the caches with stock recovery usually solves it 99% of the time

failed to mount /efs

Hello there guys. i have an "E: failed to mount /efs (invalid argument)" problem to my s7 G930F Exynos.
The phone is NOT rooted. Had NOT activated OEM unlock or USB debbuging.
I tried to flash the stock rom and i succeeded but the problem is still there.
I dled and flash the G930F_FD_Factory_Binary and i succeeded but the problem is still there.
I tried to flash a custom recovery like TWRP but Odin fails every time on both stock rom and Factory Binary (i guess the lack of OEM unlock or USB debbuging causing that).
I managed to access ADB command while on Factory Binary only but still didn't manage anything at all.
I cannt do a factory/wipe reset cause of the "E: failed to mount /efs (invalid argument)" problem.
I am out of ideas. I sent the phone to Samsung Service but cause of a small damage in the down right corner they ask me 250 euros to fix the damage and the /efs problem. They told me that they cannot fix the /efs problem alone.... Why ? Do not ask me.. It's their procedure
So... i need your help :/
I had this problem also on my samsung tablet and seems that i got it fixed by fxing it from the twrp recovery. There is a option in the settings to fix permissions and guess this is the problem you are having it also. It cant be mounted because it has no rights.
RiTCHiE007 said:
I had this problem also on my samsung tablet and seems that i got it fixed by fxing it from the twrp recovery. There is a option in the settings to fix permissions and guess this is the problem you are having it also. It cant be mounted because it has no rights.
Click to expand...
Click to collapse
i cannt install TWRP
soulremover said:
I cannt do a factory/wipe reset cause of the "E: failed to mount /efs (invalid argument)" problem.
Click to expand...
Click to collapse
Can you do a factory reset from the stock recovery? It may be worth a try, but I think it won't help.
Likely, the EFS partition got corrupted for some reason. And as far as I know, this isn't easily fixable. This partition contains the IMEI and other information, and is encrypted + secured by certificates. One can't just copy the EFS from another phone.
Maybe the Samsung service is the only option .
Or try to root it so you have system access and then you can see if you can get to the efs folder and then try the permissions. But its weird that you get this by just flashing stock with odin. Only thing i would do is use kies to revert back to stock rom and see what happens
I'm having the same problem
I'm having the same problem, have you solved it yet?
Thx!
same problem here. can't load in TWRP and don't know how to root form recovery screen? The load screen is block by custom load. FRP locked
Can you use adb ?
SrKag said:
can't load in TWRP and don't know how to root form recovery screen? The load screen is block by custom load. FRP locked
Click to expand...
Click to collapse
If flashing the stock ROM (maybe try different versions) and doing a factory reset doesn't solve it, send it in for warranty.
Don't try flashing TWRP or rooting - it won't work if you didn't enable OEM unlocking (= disable the FRP) in the developer options before. With FRP enabled, the device runs only stock software.
And as I stated before: Even if you would have full access to the phone's memory (via a debug interface of the CPU) and therefore could flash whatever you want, there is no known way to repair the EFS. It is encrypted and device specific to prevent "bad guys" from changing the IMEI.
But still, I find it really bad that flashing stock firmware via Odin can damage the EFS partition.
Yea try to flash a stockrom with the samsung KIES tool and if that doesn't work then send it back.
Nothing will work I no I had the efs problem can u use adb?
Sent from my Samsung Galaxy S7 using XDA Labs
Hi I hope you can help......I have this ERROR & I tried several ways to fix it Running the EFS Professional.exe as Administrator.....& it keeps telling me I don't have enough storage & I deleted a bunch of apps & data from phone /sd but I keep getting this error unable to back up certain partitions
dd:writing'/sdcarrd efsprobackup/temp/userdata no space left on device
887462+0records in
887461+0records out
363504025 btes (3.4gb) copied,94,239635 seconds,36.8 MB/s
exitcode=1
now I tried odin method & it says invalid binary,......plz assist.......I tried flashing firmware N910TUVS2EQB1_N910TTMB2EQB1_N910TU VS2EQB1_HOME.tar.md5 bl/cp but it didn't work
Same issue here. My phone entered a bootloop after an OTA update about a month ago. It was 100% stock, not rooted, not even OEM unlocked i was just using it as is.
It goes in download mode , goes in recovery also. In recovery is giving the following error >
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity error
I tried sending it for warranty ... they refused - it has marks of falling, but no cracks or damage 100% perfect condition.
Then I tried using KIES recovery , goes 100% , phone restarts ... same, bootloop, and same error in recovery.
Same thing with SmartSwitch.
Same thing with Odin.
never rooted, not even developer options enabled ... used it "as is" and just "OK"-ed the OTA updates when they arrived ... only issue i ever had was a few days before the bootloop , i tried to take a picture, the screen went black and no response from the device ... my pictures were saved by default to the SD Card (class 10, Adata), so i powered it off - vol up + power + home , the phone booted, then i switched it off, and took the sd card out and no issues for 2 days, then the OTA update (already was at 7.0) which was a small one ~300mb ... installed, the phone worked till the next morning and the screen froze while i was using Gmaps ... powered it off as before ... and the bootloop was evident
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT: SM-G930F
CURRENT status: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 0(0x0000)
RP SWREV: B:1 K:0 S:0
Recovery >
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing COMBINATION ROM does go 100% , but still bootloop
_____________________________________
Can not send for warranty - has marks of falling , the service shop refused warranty - 3 repair shops gave up and said they don't know how to repair the device. Can not load custom recovery FRP is ON, KIES and SMARTSWITCH emergency firmware recovery goes 100% , again bootloop.
thehost said:
Same issue here. My phone entered a bootloop after an OTA update about a month ago. It was 100% stock, not rooted, not even OEM unlocked i was just using it as is.
It goes in download mode , goes in recovery also. In recovery is giving the following error >
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity error
I tried sending it for warranty ... they refused - it has marks of falling, but no cracks or damage 100% perfect condition.
Then I tried using KIES recovery , goes 100% , phone restarts ... same, bootloop, and same error in recovery.
Same thing with SmartSwitch.
Same thing with Odin.
never rooted, not even developer options enabled ... used it "as is" and just "OK"-ed the OTA updates when they arrived ... only issue i ever had was a few days before the bootloop , i tried to take a picture, the screen went black and no response from the device ... my pictures were saved by default to the SD Card (class 10, Adata), so i powered it off - vol up + power + home , the phone booted, then i switched it off, and took the sd card out and no issues for 2 days, then the OTA update (already was at 7.0) which was a small one ~300mb ... installed, the phone worked till the next morning and the screen froze while i was using Gmaps ... powered it off as before ... and the bootloop was evident
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT: SM-G930F
CURRENT status: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 0(0x0000)
RP SWREV: B:1 K:0 S:0
Recovery >
Flashing COMBINATION ROM does go 100% , but still bootloop
_____________________________________
Can not send for warranty - has marks of falling , the service shop refused warranty - 3 repair shops gave up and said they don't know how to repair the device. Can not load custom recovery FRP is ON, KIES and SMARTSWITCH emergency firmware recovery goes 100% , again bootloop.
Click to expand...
Click to collapse
hi
Unfortunately, your device's efs partition has been compromised.
Try to write a rom of 4files on the phone if it does not answer, you need to restore the efs file on your phone
This is a backup of my s7 g930f efs.
http://efs.firmware.ir/g930fds/
If you use this efs file, your device will be changed or deleted imei number.
Try to solve with a combination or other ways. If you do not solve your problem, you can use the efs placed
good luck
asgharSo said:
hi
Unfortunately, your device's efs partition has been compromised.
Try to write a rom of 4files on the phone if it does not answer, you need to restore the efs file on your phone
This is a backup of my s7 g930f efs.
.................................................................................................
If you use this efs file, your device will be changed or deleted imei number.
Try to solve with a combination or other ways. If you do not solve your problem, you can use the efs placed
good luck
Click to expand...
Click to collapse
what do you mean write a rom ? i don't understand ... please elaborate ... i downloaded your backup but you say i need TWRP to use it, right ? or it should be flashed with Odin ?
thehost said:
what do you mean write a rom ? i don't understand ... please elaborate ... i downloaded your backup but you say i need TWRP to use it, right ? or it should be flashed with Odin ?
Click to expand...
Click to collapse
For your flash you should use this ROM.
And you need twrp to restore the efs file.
Requirements and how to use efs in the posted efs post.
I tried the rom you posted, no effect, then tried TWRP ... FRP ON blocks the install ? can not install it
hi . . how to fix sm-n935f note 7 fe .. failed to mount efs , failed to find misc partition . . rmm state : prenormal .. stuck at boot logo .. any solution to fix it ?
i am also having same problem. I am unable to resolve the issue. i had tried all the solutions, which are posted here nothing worked. At last i gave in service center, to flash the stock rom. The mentioned it can't be done and there is a problem with board. Board has to replaced.
Kindly suggest the solution for it. Thanks in advance.:fingers-crossed::laugh:
maybe try this:
https://forum.xda-developers.com/ga...covery-official-twrp-herolte-t3333770/page125

Bricked S7 - Imei lost

I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
darkalez said:
Click to expand...
Click to collapse
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
MAX 404 said:
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
Click to expand...
Click to collapse
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
darkalez said:
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
Click to expand...
Click to collapse
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
darkalez said:
I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
Click to expand...
Click to collapse
DroidHackeR said:
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
Click to expand...
Click to collapse
MAX 404 said:
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
Click to expand...
Click to collapse
Looks like OP has tried ODIN already
/data is likely encrypted, so it's not surprising that it doesn't mount, but it looks like you may have corrupted your EFS somehow. This is actually really REALLY bad. The EFS is device unique and by design irrecoverable. Previous Samsungs could regenerate it if you wiped it from recovery and then flashed stock with Odin, but AFAIK this hasn't worked since the S5. If you decide to wipe it make sure you dd your existing partition first, but if that doesn't fix it you may need to take it to a service centre and pay for a repair
Always backup the EFS first before flashing ROMs
flashing stock won't fix IMEI. Looks EFS is broken.
Try to find some1 with box.
*Detection* said:
Looks like OP has tried ODIN already
Click to expand...
Click to collapse
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
MAX 404 said:
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
Click to expand...
Click to collapse
BTW, to address that error he needs to format data. But backup his stuff 1st.
starche_old said:
BTW, to address that error he needs to format data. But backup his stuff 1st.
Click to expand...
Click to collapse
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
MAX 404 said:
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
Click to expand...
Click to collapse
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
starche_old said:
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
Click to expand...
Click to collapse
Hi
No really , as long as you dont use the data partition with TWRP is not necessary , check their thread , that step is no longer listed on the OP
1 In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2 Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
3 Extract Odin_3.12.3.zip to your computer.
4 Install Samsung Mobile Phone Drivers for Odin to find your device.
5 Download a .tar image of TWRP for herolte.
6 Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + v[Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
7 Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
8 Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
9 At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
10 If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
11 Go to [Reboot] -> [System].
12 Wait 2-5 minutes for your device to finish setting itself up
As i said in stock ROM , custom roms may vary
Regarding IMEI you are totally right if he does not have a EFS back up
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
starche_old said:
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
Click to expand...
Click to collapse
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
As I SAID I can't flash stock firmware with odin, because of efs folder problem.... I already tried it.
I haven't got a rom installed on my s7 and I can't flash any, it'll not boot.
I gived it to a local shop.... I wait for his reply
darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
Try this guide to repair your efs.
Might be worth looking into re-partitioning here
If you can get into download mode, then there is always hope! Please excuse me if I missed any info, didn't read through the whole thread. Good luck! :good:
MAX 404 said:
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
Click to expand...
Click to collapse
Agreed.
And sorry everyone for off-topic
@darkalez: Since you have TWRP, you can flash other ROMs without any problem. I guess there are .ZIP files with stock ROM, although that won't reflash the recovery.
Why do you want to flash stock? If it's just to use that ROM, then do so via TWRP. Else you are in loss.

[cofface] [3.1.1-0]Twrp recovery for Huawei Nova2

Hi guys,
I made the TWRP from TeamWin official sources for Huawei Nova2 . You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot into fastboot mode
Flash using
Code:
HTML:
fastboot flash recovery cofface_pic_al00_recovery_en.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery
Let me know if there are others
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
email:[email protected]
Unfortunately It is not working!
After flashing your file there is still the Huawei EMUI Bootloader and no TWRP. Bootloader was unlocked before. Fastboot was working fine.
Any idea?
Problem with Google GAPPS
Hi,
Thank you for your tuto and your ROM
I have bought my nova 2 in china.
Do you know how to install GAPPS. I have tried different version (stock, pico,.. ) but it's no use.
Do you know if I have to change the region first ?
Is it ok with your ROM ?
Regards
Perfect
Perfect, thank you!
Not working
Hello,
TWRP ist not working for me, I still have the EMUI bootloader after flash and reboot.
Boot into TWRP Recovery ("fastboot boot cofface_pic_al00_recovery_en.img") is aborted with:
"FAILED (remote: Command not allowed)"
Is there anything I've done wrong?
Thx!
dr.luther.1517 said:
Perfect, thank you!
Click to expand...
Click to collapse
did it work with your Nova 2?
i have got a demo device ( from germany ). Can some one upload his OEM info for a normal device ?
And yeah... it works
Success
Works very well, Thanks !
But ... while playing with it I lost the stock ROM for my Huawei Nova 2.
Since there is no download source available, could anybody share a stock ROM backup so I could restore using Twrp ?
Thanks !
My Nova 2 (PIC-LX9C432) automatically encrypts the disk after the first run, and then TWRP is unable to read /data partition nor do nandroid backups as a result. Can someone guide on how to disable encryption or get TWRP to decrypt data.
I read elsewhere that newer versions of TWRP are able to decrypt if you set a password / screen lock.
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
jusma said:
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
Click to expand...
Click to collapse
Perhaps you could get some tips from nova (1) thread there we had the same problems. But so long we have a working twrp with backup possibility.
Hi, i used this Twrp, but did not notice the error mesaje when i "create" a back up for all my data, then when deleting some things, i went off the road and ended deleting the complete operative system, and know i dont seem to be able to find a room for my phone is a huawei p10selfie(in my country) or huawei nova 2 plus (in the rest of the world) model BAC-L03, sry if i dont use the correct words, since english is not my native lenguaje
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
iamramanlmc said:
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
Click to expand...
Click to collapse
Nova 2i is Mate 10 Lite! https://forum.xda-developers.com/ma...e--roms-kernels-recoveries--other-development
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources