Hi everyone. I've been having this problem since I started rooting my Note, and I haven't the slightest clue how to fix it. Basically, when I boot to TWRP recovery and try to do a wipe (the default wipe which includes wiping cache, Dalvik, and formatting data), the recovery hangs on "Formatting /data using make_ext4fs function," and after about two minutes the application restarts. If I attempt to flash a ROM after that, I get "Can't mount /data," and other can't mount errors and even though Aroma loads fine, the tablet gets stuck on the boot screen (Samsung logo). Someone on the TWRP website suggested that the tablet is encrypted but I never encrypted the device myself.
Thanks for reading!
P.S. I see similar errors to the picture at the botttom of this thread: formatting data using make_ext4fs function
Related
Hey guys,
I'm getting really frustrated with my HOX. I'm desperate for help.
I kept getting these gapps, android.acore and htc.bgp errors which caused all the apps to crash also suffered from random restarts with JB and I rollback to ICS 4.0.3. Still no good. Same stuff happening.
I did so many cache wiping, factory resets resotring my system but nothing seems to get my device to work properly for more than two days.
Sometimes i got these errors right aftor a recovery, so its not because of a specific app.
Today my phone just shut down and refused to start (HTC white screen stuck).
I tried restoring my old system image but clockworkmod gave me "Error while restoring /system!" with I/O errors.
I don't think there is anything wrong with OS but something more native not ruling out hardware\battery issues.
Any assistance would be more than helpful, i'm really struggling here ..
I don't get any replies so i'll try to explain myself better :
My HOX gets a lot of gapps/htc/android errors. Factory reset and recovery doesn't solve it.
Every two days my device is shutting itself down and won't start until I do a full recovery of the system (which sometimes fail).
Happened with JB and now with ICS stock rom.
I just downloaded a 3.14.709 backup, flashed it using clockworkmod and the first thing to appear was an android.acore error and the phone shut down.
I think there is something wrong with the hardware or serious software issue I don't understand.
Is there away to completely wipe the whole device and install everything from scratch ?
Any thoughts would be greatly appreciated ..
Do a Factory Reset in recovery and go to "mounts and storage" and format system too.
Then Wipe Cache and Dalvik Cache to be sure
Now flash the rom you want + kernel from fastboot (fastboot flash boot boot.img)
If tyou still have such problems then its most likely the hardware...
MeLViN-oNe said:
Do a Factory Reset in recovery and go to "mounts and storage" and format system too.
Then Wipe Cache and Dalvik Cache to be sure
Now flash the rom you want + kernel from fastboot (fastboot flash boot boot.img)
If tyou still have such problems then its most likely the hardware...
Click to expand...
Click to collapse
Thanks a lot for the advice,
I did the following :
1. Factory reset - wipe cache \ data \ sd-card
2. Format system
3. dalvik cache and cache erase
4. download a recovery for my cid from the forum here
5. flashed boot.img
6. restored the recovery using clockworkmod
7. flashed gapps.
The device went up ok but I hope it lasts more than a day or two before it start rebooting \ crashing.
The last time I did it it gave me errors before it even showed the home screen.
Once again thanks a lot .. I will post further updates soon.
Good luck,buddy.
Tough luck,
After less than 24 hours I started getting Talk\Facebook\Play\Whatsapp has stopped.
Than the phone got into a boot loop and wouldn't start (Stuck on HTC white logo screen).
When I went into boot recovery and try to wipe the phone to load a recovery I got these errors :
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
and
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p13
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Error formatting /data!
Error formatting /sdcard!
Error formatting /system!
etc .. etc ..
And it wouldn't let me choose a backup to restore.
I'm getting more and more convinced it's not a rom\boot\kernel issue but rather a hardware issue ..
Any thoughts on my assumption or fresh ideas ?
I finally flashed a non Sense ROM onto my dev edition M8, and now I can't even touch /data. I got the enter password to decrypt storage bug while using Paranoid Android, so I followed the steps here to get back to a working system, but the ROM never booted to the password screen. It froze on the boot animation, the went in a loop, I tried to wipe data through recovery, the screen went blank after a few seconds, and then tried to boot the system again. I can't get it to wipe via fastboot either as I get a "FAILED (remote: not allowed)" when trying erasing and formatting data/userdata. I also can't delete anything from /data in recovery. Does anyone have a fix for this? Flashing other ROMs also suddenly quit and go back to trying to boot the system.
Edit: Flashing a stock recovery to wipe /data fixed it. Why didn't I think about that sooner?
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Note2Hunter said:
This happened a few days ago. So first of all what happened was before I went to sleep my phone rebooted by itself for no reason which I thought that maybe my phone died,But the next morning i woke up to a samsung logo on my phone (not blinking) which I thought was rebooting again, but it wasnt booting into the OS. Im running dirty unicorn 4.4.4 (final ver) and the unicorn booting animation wasnt showing up. Before I try to boot/go into recovery/bootloader there is a red blink ( not too sure if that was always there) and I am able to access my recovery and bootloader. I checked my recovery log and it says the following:
E:unable to find partition size for '/boot' '/recovery' '/modem'
E:unable to mount '/efs' '/cache' '/system' '/data' storage /data/media during GUI startup
E:Failed to get default contexts and file mode for storage files
So seeing this I tried going into my bootloader which I was successfully able to go. Therefore I tried flashing stock through odin and resulted in failing or just freezing. *Had notes about being unable to write
I had this phone for 2 years without any problems and I'm with Rogers. Has anyone else gone through this or know a solution?
Click to expand...
Click to collapse
jun3280 said:
A similar thing happened to me recently. The battery was part of the problem I believe (for 2 of my Note 2s), as it wasn't holding a charge properly (this was causing problems from charging, to regular freezes, reboots). Finally, the last time the phone just got stuck on the samsung boot logo. By then, I had my new battery, so I swapped that in - but that didn't fix the problem. I booted into Philz recovery and saw the same error messages as you. I wiped dalvik cache 3 times, factory reset, and reset for installation of new rom (which still gave me the same error messages and something about unable to format E. Despite the error message, I proceeded to reinstall the custom Rom (Ditto Note 3) again from an external SD card. Everything loaded up like normal. SMS, chat records, contacts were all in tact (like a dirty flash). That said my wifi was having issues - so I ended up redoing the aforementioned process (clear cache, factory reset, reset for installation of new rom). This time no messages about the E: location. Installation was fresh and all content was wiped clean. The wifi issue was still occurring - but it turned out I just needed to install the AGNI kernal again.
Good luck
Click to expand...
Click to collapse
So did you install it using an external sdcard?
Hi I was running leedroid m9 with root and s-off. Last night main system processes started in on a crash loop, thinking of my normal methods I rebooted the phone. Cue boot loop. At first I wasn't able to get into recovery but then I miraculously got in...only to be met with being unable to mount, wipe, or format anything (unable to mount /x (invalid argument)) apparently due to encryption that I had never set up (unable to find crypto footer). When I attempt to format data I get something along the lines of "failed to remake data" along with the same slew of mounting errors. Also download mode just doesn't work, stays at the HTC splash. Is there any hope for my phone in this state or is it donezo? Maybe something to be done twrp terminal?
Hi there, so I'm having a bit of a problem. I tried to revive my old M9. I remember flashing it with a custom ROM (Android HD Revolution) and everything was fine. I left it since I got a new phone and today wanted to play around with my M9 again.
However, it would be stuck with the HTC Logo while loading, and my TWRP was gone, could no longer boot into it and my download mode was also screwed, as it gave me the error (failed to boot to download mode).
Anyway so I tried restoring to one of my TWRP backups, by mounting a TWRP img file first using my PC. It went fine, after that I booted into system and the HTC logo would be on white background and preventing me from using the screen, although funnily enough the system was functionally normally i.e. the volume keys worked and I could see it change on screen but, it was just as if I had a some kind of overlay and couldn't use the screen itself by touching.
I then tried to flash with the same custom ROM, but after installing it and rebooting the phone it was stuck in a boot loop, where it would shutdown and try to boot again.
So I turned it off using power up and home button, and tried to wipe the partition to install another ROM, using the same TWRP method I did above.
Only this time, I can't do anything: wipe, install, format etc. I get the error "Failed to mount '/data' (Invalid Argument)" "Failed to mount '/cache' (Invalid Argument)" whenever I try doing anything within TWRP. I can't even mount cache, system or Data. It is if they're not there.
And now my phone is back to where it started, i.e. infinite boot screen with HTC Logo and "This build is for etc..." text.
Note: Trying to change file system from ext4 to ext2/3 and back to ext4 does not fix the problem ,as the same errors pop up when trying to change file system.
90% chance the nand is goosed. 10% chance of recovering by flashing a stock firmware in download mode (same version as currently installed, external sd card method).
Twrp has a known issue for bricking devices at random.