Hi,
I have somehow managed to make me tablet unusable. I do not get any wifi or lte connectivity (SIM is not read correctly).
I tried to flash via odin and using kies emergency firmware recovery. While not flashing the custom recovery, entering the "original" recovery throws this error: E: failed to mount /efs (Invalid argument)
Could someone please help me restore it? (maybe you can take a backup of yours?)
I have a p605 16Gb LTE
*IGNORE THIS POST*
Captus said:
Hi,
I have somehow managed to make me tablet unusable. I do not get any wifi or lte connectivity (SIM is not read correctly).
I tried to flash via odin and using kies emergency firmware recovery. While not flashing the custom recovery, entering the "original" recovery throws this error: E: failed to mount /efs (Invalid argument)
Could someone please help me restore it? (maybe you can take a backup of yours?)
I have a p605 16Gb LTE
Click to expand...
Click to collapse
Posted in wrong section mate
Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted since, after I factory reset and cache wiped my 4.1.1, I get passes on Odin whenever I try to install 4.1.1 again, which is all I wanted to do so I could try to upgrade to 4.3, but I never got that far. I just can't get 4.1.1 working again after a factory reset cache wipe.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Pfhyde said:
Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted myself, later, since I get passes on Odin whenever I try to install new firmwares, so I don't have the same problem those trying to roll back to 4.1.1 after failing to get 4.3 going, since in my case, I just can't get 4.1.1 working again after a factory reset cache wipe. I wanted to put a stock 4.1.1 on so I could try to update to 4.3, but I never got far enough to even try that.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Click to expand...
Click to collapse
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
mstrswrd06 said:
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
Click to expand...
Click to collapse
Well, I haven't ever had 4.3 on my phone, so there's nothing to 'get back' to. I was wanting to upgrade to 4.3, but then my factory reset/cache wipe made my phone unbootable after installing 4.1.1 firmware roms. If you think I should just try to install 4.3 in the state my phone's in now, then okay--but that seems to possibly introduce other problems, from what I've been reading elsewhere.
Did you get the stock 4.1.1 firmware from sammobile.com?
audit13 said:
Did you get the stock 4.1.1 firmware from sammobile.com?
Click to expand...
Click to collapse
Yes, as it turns out I did that already--I recognized the site immediately. I downloaded the default at&t rom again and will try flashing it (again) in the morning, but I doubt anything new will happen.
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
audit13 said:
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
Click to expand...
Click to collapse
First, when I go into recovery after flashing 4.1.1 default for at&t (though my phone is unlocked and was rooted--don't know if the root is still there after all that's happened) it says right away
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
#Manual MODE#
--Appling Multi-SCSC...
Applied the CSC-code:ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E: etc.
Then, when I try to wipe it gives me an error:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
Data wipe complete.
Then rebooting freezes on pulsing blue samsung logo--again
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
It says
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Sorry for my belated responses, but I work late on the weekends in NZ.
audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Glad you got your phone working. You do not have the 4.3 bootloader and, if I were you, I would not install the ATT 4.3 OTA update. This will install the 4.3 bootloader which makes it more difficult to get back to stock.
Pfhyde said:
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Click to expand...
Click to collapse
Some people have no problems at all, but CWM has a history of not wiping properly. That's why I don't using it anymore. There always came a point when it just would not wipe properly.
So I have a Galaxy S4 Mini (GT-i9091) stuck on boot loop.
On entering Recovery, I try "wipe data/factory reset" and get a failed message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TPA
Unable to open dst ' /system/app/VivaElFutbol_v1.03.apk' (No Such file or directory)
--Wiping data ...
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Flashing Stock ROM through ODIN gets a PASS (all threads completed, succeed 1 / failed 0), but on reboot it goes back to the Logo Boot Loop. I read elsewhere it may be a hardware issue rather than a software one. I'm looking for any advice or steps that I may be missing or is the phone doomed to be a shiny & fancy paperweight? Any info would be appreciated! :fingers-crossed:
Up? I have some problem
Enviado de meu SM-G800H usando Tapatalk
romTester14 said:
So I have a Galaxy S4 Mini (GT-i9091) stuck on boot loop.
On entering Recovery, I try "wipe data/factory reset" and get a failed message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TPA
Unable to open dst ' /system/app/VivaElFutbol_v1.03.apk' (No Such file or directory)
--Wiping data ...
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc. 1/by-name/userdata
Flashing Stock ROM through ODIN gets a PASS (all threads completed, succeed 1 / failed 0), but on reboot it goes back to the Logo Boot Loop. I read elsewhere it may be a hardware issue rather than a software one. I'm looking for any advice or steps that I may be missing or is the phone doomed to be a shiny & fancy paperweight? Any info would be appreciated! :fingers-crossed:
Click to expand...
Click to collapse
Hi my friend!, I'm suffering now exactly the same problem as you...I can't erase that app and the phone goes back every time to the logo boot loop...Did you find any solution to your problem?? please any information would be useful...
Thanks,
really? nobody can help?
I am having same problem. any solution?
Hi there ..
I have the same problem for GT-i9192 with same problem message showed up after entering recovery menu :
Unable to open dst '/system/app/VivaElFutbol_v1.03apk' (No such file or directory)
did you fix this ?!
reply needed ^^
i am having the same problem but i cant even enter recovery mode
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: CUSTOM
SYSTEM STATUS : CUSTOM
KNOX KERNEL LOCK : 0X0
KNOX WARRANTY VOID : 0X1
CSB-CONFIG-LSB : 0X30
BOOTLOADER AP SWREV : 2
WRITE PROTECTION : ENABLE
hello,
does someone know what problem i have and how i should fix this?
first of all, when i was wiping my phone it all went fine but it took to long so i turned off my phone and turned it back on, i got in an boot loop and couldnt even get into recovery mode because that would also led me into a ''teamwin'' bootloop, anyway i reflashed my recovery so luckily i can get back into recovery, but i still have bootloop for the system so i cant start up, but now i also face this problem.
i wanted to flash stock rom and this is the full error log i get ( i also tryed with custom rom but same problem)
_____________________________________________________________________________________________
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I also tryed wiping my phone, i tryed advanced wipe and full wipe and also factory reset, but i always get this same kinda error.
anyone know a fix for this?
Which version of twrp do you use?
i use Twrp 2.8.7.3
Try the last one : https://dl.twrp.me/Z00A/twrp-3.0.0-0-Z00A.img.html
Your zenfone 2 is WW or CN?
its CN
sorry for the kinda late answer tho,
well i wanted to flash the 3.0 twrp version, but it gives me an weird kind of bootloop, so thats why i downgraded to 2.8.7 :/
that's strange, are you sure it was for Z00A?
Look at this : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 to change to WW version.
[Q] [q] sm-n930f boot loops and error messages after hydra rom install & stock flash
Hello,
I've incurred ENDLESS boot loops after trying to install Hydra Rom. I've been getting very strange error messages also. In light of this, I've tried to flash back to stock through ODIN multiple times, but I've only been successful after I change the partition files to FAT through TWRP RECOVERY beforehand. It gets stalled up, I reset, then only Download mode is accessible, at this point I can get a success message through ODIN when I flash stock.
Interesting enough, the files seem to have reset after the stock flash through ODIN is successful... well, halfway successful. Everything seems to look good but then the screen pictured below shows. I reboot and NOTHING but boot loops. I have to go through obstacles to reflash TWRP and get it working again too, which is how I found the files go from FAT, back to 4.
I'm not sure what's going on, and I wish I had more information, but I'm terribly confused at this point. Anyone have any ideas??????
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 verification failed...
try to install newest twrp and format all or repair partitions ... then try to flash hydra 1.3.5 with hydra kernel 1.2.5 select in aroma .... after this flash csc selection be sure to select your csc and then reboot hope it comes back hehe