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 ?
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
ericmerl said:
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
Click to expand...
Click to collapse
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Stock ROMs
Larry2999 said:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
ericmerl said:
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
Click to expand...
Click to collapse
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
ericmerl said:
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
Click to expand...
Click to collapse
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.
Here's the console log taken from TWRP once it boots:
Code:
E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...
Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'
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
I am getting a lot of little issues with this device. Its new, had it for a day now, was able to get lineageos on it and everything seemed fine. Then during a reboot, it stuck on the sony boot screen, no way to power off, no reboot. Had to wait till the battery died. then it booted, with lots of bugs. Went to twrp and factory reset, and cache cleared. Except now I get an error of
"Unable to find partition for path '/cache' "
Any idea how to fix? I can not wipe it, etc.
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.