Ok i seen this error couple times when i doa wipe/data factory reset, i always forget to post the error so im do my best to remember the error and maybe some one can help me what it means
if i remember correctly the error says
wipe ext error extfsf_4 /dev/block/system/mmcblk2p1
like i said im unsure what the error really put out i was goin off memory, so that could be wrong, just wondering had an error similar to that
Try This Method???
Sounds like your sdcard.. Backup your stuff, format your sdcard, and try again..
if this helped.. slap my thanks button please
Hello,
I have a htc desire s (s-on, 2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04 installed).
When I start the phone with fastboot enabled, the widgets occasionally close and load again.
So everything start normal, but sometimes the widgets close in less than a second after startup and load again.
This only happens since 2.10.401.8 is installed.
I think that it's htc sense that crashes, but I'm not certain.
Already tried a factory reset, but same result.
Does Anyone have an idea what wrong and/or a solution?
After further testing I guess fast boot isn't working correctly anymore even after factory reset.
Is this a hardware problem or is there a way to test if it is a hardware problem?
Now it start to take a lot of time to startup and shutdown.
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
From what I've seen on here, this sounds like what used to be called "the dreaded eMCC chip" problem, but is actually the "cache" partition being corrupted.
From what I've read, you may just about get away with it. Have a look at the following threads;-
http://forum.xda-developers.com/showthread.php?t=1177299
http://forum.xda-developers.com/showthread.php?t=1314629
Thanks, I feared that it was the emmc problem.
I have never pulled out the battery.
I will look into the threads, but I don't know if there is much I can do being s-on.
Update:
I had to send the device to HTC and they replaced the mainboard.
Everything is working good again.
Hi.
Once I tried to install RUU on S-offed rooted phone. Instalation stopped and didn't continue. I had the same problem with partitions
I also can't get in recovery: "E:Can't mount /cache/recovery/command"
Click to expand...
Click to collapse
What helped is to format cache partition in recovery. After that I could bring back my previous rom. In the end I didn't try to install RUU anymore.
I hope it will help.
---
Sorry, I didn't see your last post
I have the S7270, I try to flash my device using the default firmware "S7270XXUANA2_S7270OLBANA2_S7270XXUANA2_HOME.tar" using Odin, but my device still can not be used and still bootlop. when entering cwm appear warning "did not match size '/system/csc/common/system/csc/others.xml". then when i use menu wipe cache, appear warning "error".
I do not understand why this happened, because I was given these devices by my friend. does anyone know a solution?
bfalcon said:
I have the S7270, I try to flash my device using the default firmware "S7270XXUANA2_S7270OLBANA2_S7270XXUANA2_HOME.tar" using Odin, but my device still can not be used and still bootlop. when entering cwm appear warning "did not match size '/system/csc/common/system/csc/others.xml". then when i use menu wipe cache, appear warning "error".
I do not understand why this happened, because I was given these devices by my friend. does anyone know a solution?
Click to expand...
Click to collapse
Have exactly the same problem with a S7270L, it seems to be a hardware problem rather than a software problem from what I've read. And I haven't found a solution yet, but if I do, I'll let you know!.
So i was using my phone 5 days ago like normal and sudendly it decided to reboot itself, after that it got stuck on the 4 balls android logo and doesnt boot into the system anymore.
what iv tried so far:
-Full Wipe
-Download and flash a full factory image, then full wipe
-Download and flash TWRP with SlimRom + Gapps then full wipe
Nothing works, it always get stuck in bootlogo, it just sits there dancing like its booting normally but it never does, im runing out of options here, what can i do guys?
Note: i have access to bootloader, all button works, also have access to recovery without any issues.
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
Let me download a kitkat image and see what happens, ill report back as soon as i do it
audit13 said:
Follow flashing a stock kit kat from?
If stock kit kat doesn't work after a full wipe, the memory chip is faulty.
Click to expand...
Click to collapse
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
mediavieja said:
So... i flashed the first build available in google site for this phone and it booted perfectly, im going to try to flash the last version again and see what happens, but why did this happened then?
Click to expand...
Click to collapse
Aight so i flahshed twrp and slimrom again but im once again stuck on bootloop what do u suggest?
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
audit13 said:
This is a sign that something is faulty in the memory chip. Stock KK, and possibly stock LP, may work but MM will always results in bootloop.
Click to expand...
Click to collapse
Nope, tried stock MM (latest stock) and didnt work
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
audit13 said:
Try LP and see if it works. If it doesn't, it's definitely the memory chip.
Click to expand...
Click to collapse
Must be then, cause i tried LP and didnt worked
I think it has something to do with differences in partition layouts between kk and LP/mm.
audit13 said:
I think it has something to do with differences in partition layouts between kk and LP/mm.
Click to expand...
Click to collapse
Do u know if theres anyway to fix it?
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
audit13 said:
I know of no way to fix this and I've not seen a post from someone that was able to run LP or mm on an affected phone.
Click to expand...
Click to collapse
Awww well thanks anyway for all ur help men, i really apreciate it
You are very welcome. We are all here to help and learn from each other.
The cheapest solution may be to buy a used nexus with a busted screen but working motherboard and perform a bit of phone surgery. I've done this a few times over the years with great results.
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
HSF3232 said:
There is a problem where /persist gets easily corrupted. Especially when you have to force reboot. A LOT. This might be your problem.
To find out if this is the case, please do the following:
1. Because you are using a Nexus 5, please download the Skipsoft Unified Android Toolkit (SUAT) and install it. Google it if you need to. Its windows only from what i can tell. Go through the screens until you configured the toolkit. You don't need pro for this setup. If you are running on linux or mac, please find a equivalent set of tools which can do the next 4 steps.
1.5. Unlock the boot-loader. Don't bother about backup, if persist is dead and you have not unlocked the boot-loader before, you WONT get your data back. (Better hope you made a partial-backup beforehand.) (Good thing is, if you did unlock the boot-loader before this problem occurred, RECOVERY OF DATA IS STILL POSSIBLE!)
2. Boot into TWRP recovery. When you get the modifications warning screen, TURN ON modifications. YOU NEED THIS FOR LATER ON.
2.5. If you already have the boot loader unlocked before the problem occurred, NOW is the time to do a backup! If /persist is dead, you will need to erase and re-flash to get android back!
3. On the bottom of the screen should be a button with 4 lines (the middle 2 should be shorter than the outer 2 if you are that blind). That is the log. Keep in mind where that button is. Go into mount and press persist to attempt to mount it.
If persist mounts successfully:
/persist is alive and kicking. Android should be starting successfully. If this is not the case, look for other reasons on why this could be failing. If other options have been exhausted, then you have a dead memory chip. Get it replaced! (And go for a upgrade while you are at it, 16 GB is not a lot. )
If persist does not mount:
Uh oh, looks like trouble. Now this is the time to check your logs. Remember the button i told you to remember? Press that button. Look for a red line that says "Unable to mount /persist (Invalid argument)"
"Unable to mount /persist (Invalid argument)" was not present.
Twrp might not be showing it or there is no way of recovering it. You have a 50% chance of recovery. Do you want to risk it? If so, carry on to step 4.
"Unable to mount /persist" was present but the text in the brackets was different.
Lookup the error code. If it is not any I/O input output errors then you should be fine to continue. If it is, Recovery is not possible.
"Unable to mount /persist (Invalid argument)" was present.
Oh dear. Looks like we have dead partition. However, because we got what we were expecting, recovery is possible. Follow the next steps. They can be done from a ADB shell on the PC or on the device.
4. Load up a ADB shell and run the following command:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
This basically runs a file system check. IT should find problems with the partition and rebuild the file system. Now here comes the next bit. (And this is where you hope you read everything and backed up beforehand.)
5. Go to the main menu and press mount. Try mounting everything. Now back out and press wipe. Press advanced wipe. Select everything that you can. Then "swipe to format" everything. Once that is done, go back into the main menu and press reboot. Press bootloader. You will get a warning about no OS, just swipe to reboot. (Why do you think we are rebooting back to boot-loader?)
If everything went well, you should now be able to re-flash with your choice of ROM. You may have to re-flash normal android first though. Look up guides on how do that.
Click to expand...
Click to collapse
Well i followed the procedure to fix persist, i was getting Unable to mount "/persist" (Invalid argument) so bu running command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist i was able to mount it, after that i rebooted the phone to bootloader and i was able to flash and run the latest software update so i have to say thank you very much sir im gonna try to put slimrom now on this bad boy and change the post title to fixed
Hallo,
at first: I tryed to post my problem in the CAT s61 section. But i got the Message that i do not have enough posts/points to do so. It was suggested by the forum to post my thread in Q&A.
I updated my CAT S61 via OTA, same way as the last updates. I am not sure to what version the update was. I had no problems or issues with the phone before.
Very shortly after booting up my phone crashes. I have to boot it up again and get that message every time:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!......
okay
drive google com file d 1zQHeQOlk2qlXDCSm8zx7s_c7s3UMOwTm view (questionmark) usp=sharing
Message on my phone on boot: "Android Recovery
CAT/CatS61/CatS619/PKQ1.190118.001/LTE_s0201121.0_S61S1.022.01user/release-keys
use volume up/down and power.
can't load Android system. Your data may be corrupted. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device
"
I shared a picture of the phone via GDrive. There is no option to upload pictures.
I can't find any useful help on the CAT-Phones site. The FAQ on the Site is mostly stuff for Android beginners. No PC tools or anything.
I don't want to lose my data and wipe my phone as suggested on the phone Message....
What can i do?
Sorry english is not my main language.
Same problem here, CAT S61, no idea if I had an update but today keeps rebooting to Android Recovery Screen,
If I power off and on I can get back into the phone with an annoying "Toolbox has stopped" error, CAT FAQ says to force stop but before I can get that far it reboots again.
Phone is charged.
Did you fix the problem?
Regards, Simon
ToolBox App Cache
Hey Simon, yes i got an email response from the cat support. I was on a buisness-trip, sorry for my late reply. I fixed it.
You have to open the app details of the toolbox app. force stoo the app, and under a sub-option in the apo info delete its cache and reboot.
If your cat s61 is in the restart-loop you can force stop ist by pressing power and vol down simultanously for dunno 8-13 seconds.
You have to be real quick. i needed like six attemps. but it worked for me.
No dataloss at all.
Thanks Dominus, I did find those instructions before your reply and tried it multiple times, but always before I could complete the instructions the phone would restart again.
I ended up doing a hard reset, not a pleasant experience, lost everything of course, photos were all in the cloud fortunately.
Phone is now operating normally again, I hope this isn't going to be a regular thing, I will certainly persevere with your instructions if it does.
Regards, Simon
Hello!! A friend of mine have a CAT S61 that after update won't boot and displays this error "Your deviced is corrupt. It cant be trusted and will not boot" but he didn't tried to root it or something like that.
And when I told him to get into recovery and wipe data he got this error of "no such file or directory.."
Do you know how to solve this error or do yo know where I can get the Stock Rom or OTA to flash and try? Ty
AugusTroll said:
Hello!! A friend of mine have a CAT S61 that after update won't boot and displays this error "Your deviced is corrupt. It cant be trusted and will not boot" but he didn't tried to root it or something like that.
And when I told him to get into recovery and wipe data he got this error of "no such file or directory.."
Do you know how to solve this error or do yo know where I can get the Stock Rom or OTA to flash and try? Ty
Click to expand...
Click to collapse
It seems they tried flashing something that was not meant for their device and now it has corrupted the system partition or somehow wiped out the operating system.
You will need to flash the full stock firmware to solve this. Can you boot the device into its flash mode? Download mode, fastboot mode or some similar flashing mode.
Do a Google search for:
"Return to stock (your model number)"
Sent from my SM-S767VL using Tapatalk
Droidriven said:
It seems they tried flashing something that was not meant for their device and now it has corrupted the system partition or somehow wiped out the operating system.
You will need to flash the full stock firmware to solve this. Can you boot the device into its flash mode? Download mode, fastboot mode or some similar flashing mode.
Do a Google search for:
"Return to stock (your model number)"
Click to expand...
Click to collapse
Ty for your response.
He says he didn't tried to flash anything. But I think the only way to solve this will be flash the stock Rom. The problem is that we didn't found the stock Rom and CAT didn't answered our emails.
Thanks again for your help!