I think I managed to finally soft brick my device.
Made some xposed changes (on v22 criskelo Note 2 version with devil kernel 1.98 ), the device got into a boot loop.
Tried to reflash v22 but it didn't work.
Then I tried to to restore my old backup via recovery but it's giving an "error mounting efs" error.
Now I'm trying to restore from KIES and trigger emergency recovery but not sure if it's going to be of any help .
Sadly I'm an idiot and don't have efs backup
After KIES emergency recovery the device is still stuck in a loop. Now custom recovery is gone as well replaced by Samsung's. The error given is E: failed to mound /efs (invalid argument).
So now I'm on a stock probably with broken efs and no backup. Where do I start? What do I do?
smage85 said:
I think I managed to finally soft brick my device.
Made some xposed changes (on v22 criskelo Note 2 version with devil kernel 1.98 ), the device got into a boot loop.
Tried to reflash v22 but it didn't work.
Then I tried to to restore my old backup via recovery but it's giving an "error mounting efs" error.
Now I'm trying to restore from KIES and trigger emergency recovery but not sure if it's going to be of any help .
Sadly I'm an idiot and don't have efs backup
After KIES emergency recovery the device is still stuck in a loop. Now custom recovery is gone as well replaced by Samsung's. The error given is E: failed to mound /efs (invalid argument).
So now I'm on a stock probably with broken efs and no backup. Where do I start? What do I do?
Click to expand...
Click to collapse
some user succesfully mount it back
http://forum.xda-developers.com/showthread.php?t=2073654
Related
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
3vilrabbit said:
Hey guys,
Yesterday I noticed my My Note 8.0 looping on it's bootscreen. The screen was also flickering...
I haven't been able to reboot the device ever since... I have tried al the conventional ways...
First attempt was through stock recovery... it returned a fail error message when I tried to factory reset, wiping cache,... every option available gave some kind of error:
Code:
E: failed to mount /system (Invalid Argument)
can't mount /system (Invalid Argument)
E: failed to mount /data (Invalid Argument)
can't mount /data (Invalid Argument)
Device has always been rooted. I have done this soo many times so I am 100 % positively sure that I didn't do anything that would explicitly cause this kind of error. So I am sure that I didn't remove or alter any files in system or data directory.
But anyways... How can I fix this...
Device doesn't get recognized anymore by my computers...
Click to expand...
Click to collapse
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
CCallahan said:
You are rooted but no custom recovery? I take it you do not have nandroid to restore from? I have only had this tablet for a few days but imagine it being Samsung you can Odin back to factory stock if you don't have a backup or flash a stock image from stock recovery: http://forum.xda-developers.com/showthread.php?t=2289441
Click to expand...
Click to collapse
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
3vilrabbit said:
I did have CWM Touch Recovery installed prior to the showing up of this error...
Device doesn't get recognized any more by any computer I own (different OSes, no success on neither one of them...)
Click to expand...
Click to collapse
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
CCallahan said:
I was trying to address your issue with it not booting properly. Have you gotten it to boot up? Did you have a backup to restore from in CWM?
As for recognizing on the PC, I'm sure you probably have the correct drivers installed already. I have had the same issue on my S4 and have not found a solution yet so have been using a cloud service or yanking the card out to transfer. Have not tried it with the Note yet.
**Edit....I might add that most will suggest checking the USB cable and trying different USB ports (to get on a different IRQ) but none of this has worked for me in the past. Might be worth trying at least to make sure.
Click to expand...
Click to collapse
I'm gonna bring it back to the shop and hopefully, if I put up a poker face if they ask me about rooting my device :angel:, they accept it and treat it with warranty
For some reason, I really don't know what I have being trying...my tablet miraculously is working again!
Thread can be closed...
Hello all
I was updating my gf phone from rooted UVALJ4 or UVALH2 (Cant remember now, but it was an old Firmware) to root66 T999_UVUENC2 via Odin 3.09 on my Win 7 pc but after the odin install (which passed) I rebooted the phone and I got stuck on the Samsung logo on the start up screen. After about 10 mins I pulled the battery and tried to enter the Recovery mode, but nothing appears. Just a black screen.
So i Odin flashed the TWRP 2.6.3.1 to try to get to a recovery, but that didnt work. Still no Recovery.
I then used odin to flash the stock tmobile UVUENC2 4.3 firmware and it still gets stuck on the Samsung screen.
Next I tried to unbrick it via http://forum.xda-developers.com/showthread.php?t=2439367 using "SGH-T999 4.3 only Debrick Image" and reflashed the stock 4.3 rom, but that didnt work. :crying:
What can I try next? WHat should I do? I can still access download mode, thats about it.
Please help if you can.
Thx
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
synplex said:
I dont know how but I got the stock recovery to finally appear and now I get these errors (see Pic) what do these mean?
The recovery errors read: E:failed to mount /data ( Invalid argument) can't mount "/data" (invalid argument)
E: Can't mount /data/log/recovery_log.txt
again thx
Click to expand...
Click to collapse
Never Mind Used Unified Android Toolkit to fix recovery and flash stock rom.
Thank god for that toolkit.
...time to donate
:victory:
Mod Please delete Thread.
Thx
In the future, try a factory reset, almost all boot hangs are solved with this. Happens because of incompatible data between versions, which would make sense condidering the jump you made. Kind of makes sense with the error message too, but I'm not 100% certain there.
Be careful with the toolkit. There is no support for it and it has bricked phones in the past.
So I wanted to install a new ROM to my SM-P600. I had a CryogenMod ROM installed and wanted to go to Hyperdrive. I reboot to recovery and do the Factory Reset in TWRP. Afterward I go install the Hyperdrive ROM. However I notice that i'm getting the message that TWRP is "unable to mount /data" in the logs. The installation of Hyperdrive seems fine but I never boots.
How do I go about repairing the /data partition? I have adb and odin installed and working.
One thing I tried was going in to adb shell but I get this error when I try "could not load library "libc.so" needed by /sbin/sh". :crying:
Thank you for your help.
Gasaraki- said:
So I wanted to install a new ROM to my SM-P600. I had a CryogenMod ROM installed and wanted to go to Hyperdrive. I reboot to recovery and do the Factory Reset in TWRP. Afterward I go install the Hyperdrive ROM. However I notice that i'm getting the message that TWRP is "unable to mount /data" in the logs. The installation of Hyperdrive seems fine but I never boots.
How do I go about repairing the /data partition? I have adb and odin installed and working.
One thing I tried was going in to adb shell but I get this error when I try "could not load library "libc.so" needed by /sbin/sh". :crying:
Thank you for your help.
Click to expand...
Click to collapse
have you had any luck with your corrupt /data partition? i spent a couple weeks it seemed on my /efs corruption & it just needed to be remounted. i had to use CWM/PHILZ for adb commands. i know TWRP can do it but i had better luck with cwm + i was able to backup my /efs with cwm. if you are still stuck give me a shout
good luck
mikmock said:
have you had any luck with your corrupt /data partition? i spent a couple weeks it seemed on my /efs corruption & it just needed to be remounted. i had to use CWM/PHILZ for adb commands. i know TWRP can do it but i had better luck with cwm + i was able to backup my /efs with cwm. if you are still stuck give me a shout
good luck
Click to expand...
Click to collapse
What is your process?
I have a S4 Mini that I am not sure if it is classified as BRICKED as I Have access to basic features .
Just to start I have no idea what percentage the phone battery is on, It is in a bootloop and stock recovery . when turned off and plugged in the battery system appears but doesn't not fully load.
I am trying to get a custom recovery on the phone but failing miserably . ADB sideload transfers the file CMW / TWRP but after reboot the phones recovery is still stock .
I have also tried ODIN with same error.
Inside stock recovery, I receive constant errors (invalid argument) wiping cache ect.
only thing I have not tried is loading a rom ? this maybe an idea. does anybody know or heard of a fix for this ? thanks
craig
before i continue with eny thing els. I would like to do an efs backup
fast booting chinese twrp gets stuck on boot and this thread is dead. People have been asking for a link for the last year
https://forum.xda-developers.com/moto-z-play/how-to/efs-backup-moto-z-play-t3711653
short version tried to do a restore and it failed to boot and now when i try to flash eny thing i get this error failed to mount '/system' (invalid argument)
i did find this video i will try this if i do not get a reply in a couple of days
https://www.youtube.com/watch?v=T-7neHzSIvc
i only included all this encase it helps
I flashed XPerience 13.0 (first rom) and after installing all my apps. I made a backup. I then proceeded with flashing magisk (did not realize i got error 1) and then rebooted and did not see magisk app so I installed it. That is when I find out that magisk failed to flash. safety net was failing now. did not have time to figure out how to flash magisk or pass safety net. So i did a restore. After restore It would boot to fastboot I can get to twrp and it can not flash anything now and cant mount system