My Verizon tab was having issues, so I used heimdall to reflash it to stock like ive done in the past. It takes it now about 5mins on the samsung screen before it goes to the verizon logo. Then it proceeds to stay in a boot loop. Getting into recovery also takes about 5mins now. Managed to get there once and I saw there was some errors in some of the logs. I think i killed my tab any suggestions?
In Recovery it says
E:Can't mount /dev/block/mmcblk0p1
E:Can't mount Cache: recovery/command
#Manual Mode#
E:Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
E:Can't mount CACHE: log/recovery.log
E:Can't Open CACHE: log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
When I try to factory reset it says
E:Can't mount /dev/block/mmcblk0p2
(invalid argument)
E:install_application_for_customer:Can't mount DATA:
your storage not prepared yet. please use UI menu for format and reboot actions
Try using heimdall to put the standard KhasMek kernel and recovery on it.
No change its just sitting on the samsung logo now
Part of the installation of KhasMek kernel involves about 3 minutes of sitting at the Samsung logo, but there should be a voice playing over the speaker letting you know what it is doing.
EDIT: Try getting back into recovery if it is still just sitting at the samsung logo, and see if it put CwM recovery on it, then you might be able to wipe data/factory reset and wipe cache. If not, then you will probably need to go into a little more detail how you "reflashed to stock" in order to get the answers you need.
Installed the KhasMek kernel had it install cwm. Was able to boot into recovery Wiped data cache, factory reset, Then restored a nandroid backup. Since then its been stuck on the samsung screen. Went back to stock originally using the pieced together verizon stock firmware. This entire problem started when I found that my tab wasnt booting after a battery drain. I turned if off one night it was acting perfectly fine and since it hasnt booted past verizon screen. Figured it might help to flash it to stock after that point.
Since it has not worked since you tried flashing to stock, I would assume that the issue was in that step but was not the kernel or recovery, and since you have done it successfully before, you might just need to try flashing to stock again. I had a link to a guide but I can't find it now, but a quick google search returned these:
/how-to-restore-verizon-galaxy-tab-back-to-stock/
and
how-restore-vzw-galaxy-tab-stock-dj11
It appears that as long as you can get to DL mode you should be able to bring it back.
Related
I know there's already dozens of threads with this problem but I've been going through them for three days now and I've pretty much given up trying to fix this. I'm posting here as a last resort.
All of sudden my nexus started shutting off or restarting and then it froze at the google screen, not the X logo like most people. I went into fastboot and then to recovery then tried the wipe data/factory reset option, doesn't do anything. Left it on that screen overnight and all that happened was the battery drained.
Now I'm stuck with in the android recovery screen because I kept trying to wipe it so much
E:failed to mount /cache (Invalid argument)
E: Can't mount /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:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
I've downloaded sdk files, images and toolkits. I've done commands but I can only get up to unlock bootloader because it fails. I don't know what else I can do at this point, nothing seems to work. I've watched a video of a guy doing the wipe data/factory reset and it reset in seconds so I'm very frustrated with this thing. It's only 10 months old and I can't remember if I got a warranty or not and I don't even know how long a warranty is on these anyway.
Forgot to mention a couple things. When I try to wipe it, the android is frozen unless I press the power button and volume up again. Then the blue line and the little shape in front of the android start moving. There's no text here and the text freezes on -- Wiping data... Formatting /data and I never rooted it.
I am getting this same issue. The lack of replies is concerning.
broncop3t3 said:
I am getting this same issue. The lack of replies is concerning.
Click to expand...
Click to collapse
The reason there are no replies is probably because there is no solution if people can't help they won't comment and clutter up the board with useless posts. Tell me everything you can about your situation is your bootloader unlocked? Rooted? What ROM are you on? Can you access fastboot mode? Ect and I will see if I can help
Sent from my C5303 using xda app-developers app
I was on cyanogenmod 11 4.4. I had many random reboots and was going to do a factory reset through recovery, it was freezing too much to reset through Android. I used Nexus root toolkit when I rooted/ installed CM11. Now when I try to use the toolkit I get fails and trying though recovery gets me the E: failed to mount errors.
Nexus 7 Wifi (2012)
unlocked bootloader (still shows unlocked on "google" screen
Was Rooted
I can access fastboot mode.
I tried to flash via fastboot and was unsuccessful.
Thanks for your help.
What error message do you get when you use wugfresh NRT back to stock and unroot with the option for soft bricked
Edit: It just occurred to me the most common reason for flashing failing or "failure to mount" is a corrupted nand memory, a bit like bad sectors in a hard drive.
Nand going bad could produce the spontaneous reboots and would explain why you are unable to reflash it.
The only option if that is the case is RMA or a new motherboard.
Sent from my C5303 using xda app-developers app
Recently, my Nexus 4 has been crashing randomly - shutting off with no warning or notice. It has always rebooted back up without issues. Last night, however, it just got stuck in a boot loop - spinning balls for hours on end.
Bootloader and Recovery Mode come up with no trouble.
The phone is and always has been pure OEM/stock. I've only ever updated using built in OTA process.
I tried to reflash to stock using Wug's Nexus Toolkit, but it repeatedly failed saying the device was locked. I tried to unlock the bootloader, but that seems to require a reboot to take hold, and every time I tried the reboot it would loop again.
In Recovery Mode, I get the following:
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:failed to mount /cache (Invalid argiument)
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​
I have downloaded the full image and tried flashing the cache, and system with no effect. Toolkit doesn't show an error, but nothing changes.
Does anyone have any suggestions? I'm at a loss.
Did you try
fastboot erase cache.img
fastboot flash cache cache.img
Then perform wipe data/factory reset before booting into android.
I have a GT-S5360 which is stuck in a boot loop.
I've tried wiping the cache and a factory reset: makes no difference.
I tried rooting it with the update from here: http://forum.xda-developers.com/show....php?t=2085390
It appears to do what it should: says "Install complete", but still gives the same problem.
When I go to reboot, it says:
E:failed to mount /data (invalid argument)
E: copy_log_files_to_data
:: cannot mount /data Rebooting
Click to expand...
Click to collapse
Then I tried downloading something to it with Odin, which looked like it did what it should, but the phone is still stuck in a boot loop and now I cannot get to enter Odin mode.
Finally, I did a search of this site and found an appropriate looking thread which took me to here: http://www.mediafire.com/download/x8...ockworkmod.zip
Which comes back as "Installation aborted".
If I try to wipe data after running the update, it comes back with:
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /cache...
E:format_volume: rfs format failed on /dev/stl10
Data wipe complete
Click to expand...
Click to collapse
I'm guessing there is something not working with that update: can anyone suggest a better one to try?
Or some way to get back into Odin?
Thanks in advance.
I'm having issues booting into my innjoo device.
It all started one morning, I woke up and saw some errors on my screen like (android.process has stopped working) I switched off the phone and turned it back on, but it got stuck on the innjoo logo and never booting up.
I decided to boot into recovery, where I encountered a list errors saying
(E: failed to mount /cache - invalid argument)
(E: cant mount /cache/recovery/log)
(E: cant open /cache/recovery/log)
And some other similar errors.
Choosing the wipe cache partition and the factory format option resulted in the same error. Which led me to believe my internal memory may be corrupted somehow (the data partition perhaps).
Is there a fix for this? And does anyone know of a way to correctly partition an Sdcard so it can be bootable and recognised by the device?
Help! My phone is now stucked on a boot logo. I tried rooting and flashing via odin on Oreo, after then, it stucks on boot loop, on which I know how to fix, going back to stock rom works, but then signal is gone (boot loop wasn't expected, didn't managed to see bandbased version) I then, flashed this: https://forum.xda-developers.com/showthread.php?t=2420881 through odin via AP, which is a wrong method on which I know I am stupid enough, right after then, OS won't boot up but stuck on boot logo, also tried using TWRP and Official Lineage OS 14.1 and the same thing happened, it starts to boot up, it rebooted after a few mins, then it goes back to TWRP.
HELP, I think the wrong method of flashing of this: https://forum.xda-developers.com/showthread.php?t=2420881 file is the mistake, idk what did I messed up with it, it was supposed to be used for EFS restore app not flash through Odin, what should I do? Any OS just stucks on boot logo but download menu and recovery mode (official/twrp) is still there, also the phone is still viable to be flashed.. Please help.. I just got this phone not even 24 hours ago.. Lol, I know stupid me, that I didn't checked the file carefully, I learnt my lesson, criticize me or anything.. But please, help if you can.
I had not known that the Marshmallow, Nougat and Oreo was pretty harder to do things on, I'm quite new with this new OS release, I was pretty confident because I was doing this all over the years (I only know step by step, not really in-depth information). Way back, odin only requires AP, now it requires 4 columns on which I cannot reflash without unchecking the Bootloader.
P.S. Before boot loop starts to happen I tried rooting on Oreo, downloaded my own country region openline version(I am openline, yes) and also tried Lineage OS 14.1, Now, I am trying to download Russia(not my country) Stock Rom Oreo, it might be the case that it doesn't allow me to flash bootloader as this was the downgrade, and I skipped right through it. But I am worrying about the wrong flash file and after the download finishes, the same thing happens and I won't be able to get passed out of boot
EDIT: I've did everything and ODIN works for the flashing the whole columns including bootloader with russian full stock ROM, but its still stuck on boot logo, EFS not detected on recovery. I'm losing hope, this is not recoverable yeah?
Here's the error code on recovery mode:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [Unknown]#
No Suppport SINGLE-SKU
E:Failed to mount /efs (Invalid argument)
File-Based OTA
E:Failed to mount /efs (Invalid argument)
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-verify verification failed...
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
E:Failed to mount /efs (Invalid argument)
... and so on.
E:failed to clear BCB message: failed to find /misc partition
i have this problem too