Ok people so I think I F***** up royaly. I had my KF for months now and swaps plenty of roms on i butthe other night I was flashing a rom and accidently erased everything off the KF. Now it won't boot flashed rom. It says installaton success but follows with e: cannot load or something in that effect. I finally got my computer to recognize KF and mount but it won't boot custom rom. it'll either stay stuck on the triangle screen, back to TWRP or boot but screen stays black. Idk what else to do . I tried dozens of things and I feel that my head is going to explode. Please someone help.
Btw when using KFU I get
ABD status offline
Boot Mode 0x5003
Anyone?
mr.f20b said:
Anyone?
Click to expand...
Click to collapse
Patience Grasshopper...
Did you remember to wipe system and factory reset before flashing the ROM?
yea I did. after it's done installing it says
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
E: can't open /cache/recovery/last_log
E: cannot load volume /misc!
E: failed to mount /cache (invalid argument)
what am I doing wrong?
I finally got it to boot but now it's stuck on the boot animation..
Scratch that, I finally got it to work. Got it to normal boot. kept freezing on me but instead of holding the power button, i rebooted thru twrp. Did the latest update thru KFU , rebooted and did sustem wipe and factory reset, reinstalled and currently running Cyanogen Mod 9 Thanks for the help soupmagnet
In recovery, enter the following commands and post the results
Code:
adb shell
parted /dev/block/mmcblk0
print
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.
I just got a brand new Nexus 7 (2013), installed drivers from the ASUS support site on a Windows 7 pc, fastboot oem unlocked the bootloader, fastboot flash recovery ClockworkMod Recovery, rebooted into recovery, and get this error:
E: Can't mount /cache/recovery/command
E: Can't open /dev/block/patform/msm_sdcc.1/by-name/misc (no such file or directory)
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
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Can't open /dev/block/patform/msm_sdcc.1/by-name/misc (no such file or directory)
Then I tried mount /system and get:
Error mounting /system!
I had done absolutely nothing else to the device, not even activating it. Booting up regularly goes just fine so it's possibly not bricked, but I really wanted to do the mount /system in CWM for a particular reason.
Thanks for any help.
like the same issue many of us are having with really new Nexus 7 devices..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/nexus-7-wont-mount-files-twrp-t3272873
sgtfoo said:
like the same issue many of us are having with really new Nexus 7 devices..
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/nexus-7-wont-mount-files-twrp-t3272873
Click to expand...
Click to collapse
Thanks, I'm sure that's part of the problem. But after more extensive testing/cussing, it turns out I'm having a problem with the ADB driver as well. I'm using a Windows 7 pc with only USB 3 ports and can update to the ASUS drivers just fine in TWRP Multirom recovery mode. But while in Device Manager the driver says it's working properly, the device won't list with adb devices.
Since I'm trying to do stuff with the device not yet activated, I can't go in and turn on USB debugging. Does that have anything to do with it? With tons of searching online I can't tell since I haven't really seen much about my particular situation.
Hi guys today I power off to change the simcard and power on again and I get my phone with the logo of Fire for half hour, and dont start up.
Then I try Power+Volumen UP and I see this:
E:failed to mount /cache (Invalid argument)
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
I try to delete cache and not finish after 20 minutes.
UPDATE 1:
After many reboots and try to wipe cache.
Wipe Cache Complete.
But Continue on Firephone Logo.
I press power off and when the phone to off I see the desktop is something like the image logo dont unload but load the OS.
I connect to usb port on m y pc, I see device manager and see adb device.
I start console and:
adb start-server.
Adb Shell
and I get a shell!
UPDATE 2:
I copy picture from camera with this command:
Backup Pictures
"adb pull /storage/emulated/legacy/DCIM/Camera ."
Backup "All"
"adb pull /storage/emulated/legacy/ ."
See the Dot at the end with previous space
"adb backup -all" ask for unlock screen and I cant do it!.
Now how can I make backup of my files on this state? or try to fix it?
invalid argument ( Fire Phone )
hello, help me please ...i'm same Problem
I used my phone normally and then everything from a cpip to planted, and then I do the same manipulation as you on my Smartphone Amazon but nothing without following it shows me on the recovery '' E: Failed to mount / cache (Invalid argument)''
what does it mean according to your expertise please?
U see AMAZON LOGO OR FIRE LOGO when u press the power button?
If u see amazon logo, try to sideload original firmware, u have some tutorials in Amazon Fire Phone section, search on google "sideload amazon fire phone firmware" if will not work, the phone is DEAD
was his problem Dear Friend, I try with the Official Firmware 4.6.6.1 But it has still not given its many times written to me (Invalid argument), But in other forum for other android phone that have even worry they have been able to settle but for my Fire Phone I do not find it until, I'm on there is a solution because the Phone is not Hardbricke but rather Softbrick so you just have to find the best order in Linux To repair this softbrick ???
But, until I have always searched the net, but without finding a better solution except I have seen on this forum we are only two who have this problem of (invalid argument)
helped me please, there are no those who are strong in LINUX Here?:crying::crying::crying:
Hey guys!
I hope I can get some help here. Got a ZE551ML Zenfone, it died on me yesterday. It ran out of battery and turned off, then when I recharged it and tried turning it on, it wouldn't boot up. It gets to the Asus logo and the turning circle and just sits there forever. I tried restarting many times, but the result is the same.
I tried going into recovery and wiping cache, but any action in recovery just gives the error:
E:failed to mount /cache (invalid argument)
Just booting into recovery gives that error, mounting /system, adb sideload, factory reset.
I tried doing things in fastboot, but get a similar error on everything:
Code:
Erasing 'cache' FAILED (remote: 'Can not mount the necessary partition')
fastboot: error: Command failed
And same if I try to format or flash anything. Tried to get TWRP, but can't flash it, same error.
I read a lot of threads about debricking, but they're all focused on getting fastboot or recovery up and then just flashing something. My recovery and fastboot work, but I can't flash anything. Is there anything else I can do to debrick it? I'm not an expert so I'm not sure if any of the other tools would be useful, like AFT or xfstk. Is there anything I can flash with them that would restore the partitions or something?
And if it's really a hardware failure, is there any way to get the data off it at least?
Any help would be much appreciated!
It is an eMMC failure. The exact same thing happened with mine and a friend's ZenFone 2 (both 4 GB RAM, 16 GB ROM and 1.8 GHz CPU). eMMC is the internal storage of the phone and to my experience the 16 GB chip was from SK hynix in both the units (H26M52103FMR). The chip does not have high endurance and wears out over time. We got both our motherboards replaced. AliExpress sells motherboards cheap for ZenFone 2.
Yes looks like you're right. The motherboards are close in price to a second hand working Zenfone 2 haha. Looks like it's the end for it.