[nevertells]

pgzerwer2, on 04 March 2013 - 02:51 PM, said:

Well,tried to run Acme Installer 3 with nothing in the CM Install folder to resize system partition but it stalls after about 8 minutes after it says "stop printing. " Able to get out without any apparent damage, but the partition is still 300 MB instead of 400. Any hints?

Sent from my cm_tenderloin using Tapatalk HD

Believe it or not, if you had waited, ACME3 would have finally finished. What is happening is ACME3 is trying to clear thousands of inode errors and literally getting bogged down in the process. Best way to accomplish what you are trying to do is make a nandroid backup preferrably with cwm6. Save a copy on your PC. Run ACMEUninstaller. Put the CM9 rom, Moboot 0.3.8 and CWM6 in the cminstall folder. Be sure to add "update" to each filename without the quotes. Don't worry about installing gapps. Run ACME3. When it is done, do a quick boot up to insure everything went as planned. Now reboot to cwm6 and restore the nandroid backup. You will now have a clean /system partition with 400mb of space.

steventrannn, on 04 March 2013 - 07:10 AM, said:

Is this the correct way to clean filesystems after updating to the latest TWRP?
1. Backup
2. Wipe Cache
3. Wipe Dalvik Cache
4. Factory Reset
5. Wipe System
6. Restore Backup

No, it's not. You quoted J.C. Sullins suggestion, why not just follow that?

Edited by nevertells, 04 March 2013 - 04:08 PM.

[Gradular]

nevertells, on 04 March 2013 - 04:06 PM, said:

Believe it or not, if you had waited, ACME3 would have finally finished. What is happening is ACME3 is trying to clear thousands of inode errors and literally getting bogged down in the process. Best way to accomplish what you are trying to do is make a nandroid backup preferrably with cwm6. Save a copy on your PC. Run ACMEUninstaller. Put the CM9 rom, Moboot 0.3.8 and CWM6 in the cminstall folder. Be sure to add "update" to each filename without the quotes. Don't worry about installing gapps. Run ACME3. When it is done, do a quick boot up to insure everything went as planned. Now reboot to cwm6 and restore the nandroid backup. You will now have a clean /system partition with 400mb of space.



No, it's not. You quoted J.C. Sullins suggestion, why not just follow that?

Wrong NT. He was asking about TWRP. JC posted about CWM. And other then not having to wipe cache, that is correct. System reset wipes both data and cache partitions.

Sent from my cm_tenderloin using RootzWiki

[nevertells]

Gradular, on 04 March 2013 - 04:20 PM, said:

Wrong NT. He was asking about TWRP. JC posted about CWM. And other then not having to wipe cache, that is correct. System reset wipes both data and cache partitions.

Sent from my cm_tenderloin using RootzWiki

Yeah, he was asking about TWRP, so my bad on that. I was suggesting that he follow Sullins recommendation as I don't think many folks know exactly how twrp works.

So you are saying that "Wipe System" in TWRP accomplishes the same as Sullin's suggestion to use wipe data, wipe system, wipe cache in CWM?

Regardless of which one is used, if one is trying to clean up the corruption in the file system caused by older versions of twrp and cwm so ACME3 will run without all the inode error issues, I would be inclined to backup, uninstall, and reinstall with ACME3.

[pgzerwer2]

nevertells, on 04 March 2013 - 04:06 PM, said:

Believe it or not, if you had waited, ACME3 would have finally finished. What is happening is ACME3 is trying to clear thousands of inode errors and literally getting bogged down in the process.

That would be odd since I went out of my way several months ago to use the CWM 6 process to get rid of the inode errors. Oh well.

Sent from my cm_tenderloin using Tapatalk HD

[nevertells]

pgzerwer2, on 04 March 2013 - 05:45 PM, said:

That would be odd since I went out of my way several months ago to use the CWM 6 process to get rid of the inode errors. Oh well.

Sent from my cm_tenderloin using Tapatalk HD

Try what I suggested and see if that doesn't cure your issue.

[Gradular]

nevertells, on 04 March 2013 - 04:49 PM, said:

Yeah, he was asking about TWRP, so my bad on that. I was suggesting that he follow Sullins recommendation as I don't think many folks know exactly how twrp works.

So you are saying that "Wipe System" in TWRP accomplishes the same as Sullin's suggestion to use wipe data, wipe system, wipe cache in CWM?

Regardless of which one is used, if one is trying to clean up the corruption in the file system caused by older versions of twrp and cwm so ACME3 will run without all the inode error issues, I would be inclined to backup, uninstall, and reinstall with ACME3.

My bad. I meant factory reset and it just does data and cache. And I agree, the best way to clear out inode errors is to backup, uninstall, reinstall, restore.

Sent from my cm_tenderloin using RootzWiki