yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] nevertells2:
Did you go read the link nitrobg posted yet? The corruption issue first came to light when folks started using ACMEInstaller3. CWM 1.0.1.2 when used to install a nighty roms causes fs corruption in the /system partition. The error checking routines in ACME3 try to fix the corruption resulting in thousands of inode errors. Without conformation from someone at TeamWin, we have to be cautious about using TWRP until we know that it is not based on cwm code with a touch UI, or some extensive testing that can confirm that TWRP does not introduce the same fs corruption that cwm does. CWM6 is now available for testing. The, corruption issue is fixed as well as other improvements. If you are part of TeamWin, what can you tell us? Thanks
[TouchPad Development] ViViDboarder:
Well, first off, the guys assumption is false:

Twrp is not based on CWM and has no CWM in it at all. It's forked from AOSP directly.

He also never goes into detail as to what about the backup/restore of /system caused corruption.

This could be related to what I've seen on the TF101 when flashing CM10 roms. There becomes a "corruption" of /data in that blkid reports the partition as ext3 when it's really ext4. But this doesn't appear to be related to twrp either but related to CM10 only. I had someone pose that it was because CM10 disabled journaling which could result in recovery not recognizing or mounting the partition correctly.

Though this doesn't sound like the exact same thing, it does point out that if CWM and Twrp have been working just fine on CM9 roms and everything else for a long time and CM10 or ACME break it... then it's probably their fault.

I can post there to see if I can get some more info.
[TouchPad Development] nevertells2:
If you guys on TeamWin can state for the record that TWRP is perfectly safe to use, then that puts the issue to bed and I'll be happy to help spread the word.
[TouchPad Development] ViViDboarder:
So I see you mentioned that it needs to be tested with twrp. Is twrp showing the same errors currently? If CWM is now fixed with their latest version, I may just have to compile the latest version of twrp as well.

While Twrp is not based on CWM at all, the .zip flashing mechanisms are forked off AOSP. Newer versions of twrp have been rebased on top of Jellybean.

Now, this is if it indeed is reproducible with Twrp. Although a refresh couldn't hurt! There have been enhancements since 2.2.0 anyway.

Finally, I'd like to propose my theory on the matter (I can't test since I don't have a device). I believe ACMEInstaller3 is incorrectly reporting an error. If there were corruption issues we would have seen countless posts about corrupted system partitions for quite some time now. It also appears that the corruption (if it exists) doesn't have any effect whatsoever to any applications other than ACMEInstaller3.

Was there some other reason why people were worried?

But for the record: Same code is has been running perfectly fine on over 30 devices with no issues.
[TouchPad Development] nevertells2:
ACME3 was released because the /system has to be enlarged so Jelly Bean can be installed. If you think that the issue is with ACME3, you need to take it up with Green, as he is the one who wrote and released it. When it was first reported that people were seeing thousands of inode errors while trying to upgrade to CM10, I PM'ed Green and he replied back that the old version of CWM had problems in the code that he was aware of and that he never used that version for that reason. Here is what he said to me in that PM:

"The reason why when using ACMEInstaller3 there are tons of errors, is that when they did their previous installation, they used CWM otpion to reformat /data and /system (or just /system which is done automatically when you install an upgrade).

CWM contains broken e2fsprogs that corrupts fs as it is being created.

For those who never used CWM to install any ipdates (like myself) there are no problems when ACMEInstaller3 is used.

Those who were tainted by CWM now need to ACMEUninstall before using ACMEInstaller3."

There you go. His words, not mine.

Please, PM Green see what he has to say.

When I get the time, I will ACMEUninstall one of my TouchPads and use ACME2 to install an older version of CM9. I'll then use TWRP 2.1.1.1 to install several newer versions of CM9 and then run ACME3 and see if I get the errors. This would be as close to replicating what an average user would do over a period of time. I'll let you know when I get the test done and what I find.
[TouchPad Development] ViViDboarder:
Thanks for your testing.

I talked to Green on IRC. It looks like the actual issue is with a library in CM source not checking for kernel compatibility on a particular feature.

Looks like CM just merged a patch to cover the issue. I'll see if I can update the version of CM I'm building against.

That said... The corruption doesn't seem to hurt anything as literally anyone running CM on the TP will actually already have been exposed to the bug. Worth clearing up though. Everyone should be safe.

Will keep you all posted on progress of the new build. Just moved to a new server and I have to set it up.
[TouchPad Development] nevertells2:
DeesTroy posted in the ACMEInstaller3 thread that there was an issue in TWRP with fs corruption and that it is fixed in version 2.3.2.3.
[TouchPad Development] ViViDboarder:
Yea, workaround sounds like the right way to go and appears to be confirmed.

I'll update OP.

Can someone with a device confirm that 2.3.2.3 is showing in GooManager?
[TouchPad Development] nickster1:
Yup its there.
[TouchPad Development] Nomad1600:
Can I confirm the steps needed to be taken to update from the older version of twrp to the newer version? Do you go to Goo manager, click on the three dots on the upper right, and and select which option?
[TouchPad Development] sstar:
That's what I would do. Try it,you won't break it and it will show what is going to be DL/ installed and give you the option to say no.
[TouchPad Development] nevertells2:
Install open recovery script.
[TouchPad Development] Nomad1600:
OK, clicked the three dots, clicked on Open recovery Script, it then offered up a new screen that mentioned the new file: openrecovery-twrp-2.3.2.3-tenderloin.img. Pressed ok and it started the download.

Does that download take a long time though? Its been downloading for over five minutes and it hasn't shown me a progress bar but rather a series of blue lines going to the right. If this continues for another 5-10 minutes, is there a safe way to interrupt and try again? Is there something I should be doing otherwise?

---------- Post added at 12:37 PM ---------- Previous post was at 12:18 PM ----------

And as an update, since it is still showing as "Downloading" I clicked on the Goo manager icon in the notification area, it asked if really wanted to cancel, at which I point I said yes... and it had no effect, it continues to read that its downloading.

So... is there a safe way to interrupt this "runaway" ? Reboot?

And is there a better way to try to download the file without the runaway process?

Also, I am getting four bars on my wireless, and other notifications are coming in, so I know its not a case of not being connected to the internet. Thanks in advance.

---------- Post added at 12:59 PM ---------- Previous post was at 12:37 PM ----------

Never mind, crisis averted. ;) I went into settings -> apps -> running -> goo manager and stopped the process. Then went back into Goo and redid all the steps (click three dots -> Open recovery Script, started the download and it immediately said the download was complete. Just to make sure I rebooted into Recovery, and while it took a bit longer than normal to go into TWRP, it now shows TWRP version 2.3.2.3 . So all is good.

So I am safe to use twrp once I go to CM10? I haven't gone to ACME3 yet.
[TouchPad Development] nevertells2:
According to TeamWin, the new version 2.3.2.3 is safe. According to J.C. Sullins, if one reformats the /data and /system using CMW6 or I'm guessing the new TWRP, then you should not have a problem running ACME3 to install CM10. I guess the only way we will know of sure is when you try it. The alternative is to use ACMEUninstaller and then ACME3 to install CM10 and you will not have problems.

Actually, after formatting /data and /system, I suppose you could just flash the CM10 rom using TWRP or CWM6 and not even bother with ACME3.
[TouchPad Development] ViViDboarder:
OP has been updated to reflect the new version.
[TouchPad Development] Root-Maniac:
Hey I updated to recent version of twrp and now y pad won't boot into recovery, it says uimage is wrong size or something like that..... wife is pissed now, lol

Also I used too to download and install...
[TouchPad Development] slick_shoes:
I updated to 2.3.2.3 and when i tried restoring my nandroid, it gave me the www.palm.com/ROM

I had to use the Doctor. I even tried to restore different nandroid and it kept doing the same. Got tired of using the doctor so I went back to 2.2.2 and don't have any issue anymore.
[TouchPad Development] Root-Maniac:
A little help please... I used goo.I'm too install...
[TouchPad Development] tinnef:
You should check the direct download link, it points to the Nexus4 version:

http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.3.2.3-mako.img

I would not be surprised if that causes some of the problems that are reported here
[TouchPad Development] nitrobg:
Probably your /boot folder is full. Try flashing moboot cleaner, reflash your ROM again and install TWRP.
[TouchPad Development] ViViDboarder:
Boots to everything but recovery fine? I'd try again. Might be a bad download.

Edit: Just noticed the post mentioning the direct link being incorrect. If you installed with that then that is definitely the problem.

Shouldn't effect Goo though. That was a copy paste error on my part when updating the OP. Also, many other users have already used Goo to update.
[TouchPad Development] Root-Maniac:
I can't get a new recovery installed for the life of me...
[TouchPad Development] crhylove:
I used the Goo Manager no problem. Opened Goo, 3 dots (settings), then install open recovery. Boom! LOVE having TWRP. Reverted back to CWM after the acmeuninstall acme3install, and was hating it.
[TouchPad Development] Root-Maniac:
After a long day, I discovered that i after I mounted the boot and deleted the old twrp ultimate it installed fine. :)
[TouchPad Development] nevertells2:
Because this is a thread and not a forum, I see no way to determine how may folks are visiting here. It seems like only people that are having problems post. How about some reports on how well version 2.3.2.3 is working for you. Tell us what you have done with it, backups, restores, wipes, formatting data, system. boot, etc. This would help users as well as developers determine the usage and success of the build. Thanks
[TouchPad Development] Nomad1600:
Since upgrading to 2.3.2.3 I have only performed one set of wipes and that action seemed to work with no problem. At some point in the next week I will try ACMEuninstaller and then ACME3installer, then restoring my Nandroid of my current ROM (SGA TnC). I still haven't been too motivated to try one of the CM10 ROMs (at that point I may try SGA's Slim ROM). Once I do I will be happy to share my experiences.

Thanks Nevertells for all your efforts advancing TP.
[TouchPad Development] crhylove:
So far 2.3.2.3 has been great! No problems here!
[TouchPad Development] allstar319:
Is 2.3.3.0 on Goo a newer version? Fixing permissions causes TWRP to crash, I'm assuming, and then comes back up in about 5-10 seconds.
[TouchPad Development] nevertells2:
I've just created a new thread for anyone who has installed and used either CWM6 or TWRP 2.3.2.3 to post their experience on. Please go have a look and help your fellow users and developers alike find out where we stand with these two new recovery programs, Thank you.

Link: http://rootzwiki.com/topic/37783-if...323-tell-us-how-it-works-for-you-good-or-bad/
[TouchPad Development] ViViDboarder:
Well, if you have anything interesting for me, make sure to let one of us on TeamWin know. We can't really watch every thread.
[TouchPad Development] nevertells2:
Be happy to. Just trying to improve the product and the user experience.
[TouchPad Development] Thing O Doom:
I have cm9 installed and working and I want to install this as my recovery. I currently have no recovery as I didn't include that.

I have adb working through cm9, including shell with root access, what would I input to flash the recovery.img? Or am I completely missing something necessary with moboot entirely? I'm new to the touchpad and just trying to set it up.

Thanks

ToD

--

More info:

What I've done so far is use acmeinstaller3 to flash Gapps, Cm9, and moboot.

I have moboot with hpwebos, hpwebos recovery, and cm9.

Optimally what I want to do is just flash twrp recovery.img via adb and have it in moboot, but am I missing a step?

Do I need to run acme again with a flashable .zip of twrp in cminstall folder? Where would I find / how would I make one?

Just trying to figure the whole moboot thing out xD

Thanks
[TouchPad Development] nevertells2:
Yup, you are missing something completely. Install GooManager from the Play Store and use it to install TWRP. Run GooManager and tap the three dots in the upper right. Select Install Open Recovery Script and follow the prompts. Once it is done you should find a selection for TWRP on your Moboot screen.
[TouchPad Development] nevertells2:
@ViViDboarder

Do you have any way to track how many times version 2.3.3.0 has been downloaded? Not many folks are posting about issues or how well it is running. Thanks
[TouchPad Development] sstar:
I am using it and it is running fine , the only issue I had was on up grading to the 2.3.3.0 version was that it made a new ifolder n TWRP/backup that was not viewable when in TWRP I am not sure whether the older recoveries could have been moved as I didn't need them and they have now been deleted .

On a slightly different note I have just updated my Rom Toolbox Pro and it now offers the ability to make and name backups thru various recoveries ie CMW/TWRP rom wiping multiple flashing and checking for updates of recoveries and roms apart from all the stuff it used to do. I am not sure if the new features are available with the lite version but will check and edit this post later if necessary . I now don't bother with Goo manager as it's no longer needed .
[TouchPad Development] ViViDboarder:
Yea. If you find the download on Goo you can see the download count. I'm on vacation and on my phone, otherwise I'd check for you.

Glad you got it all figured out. I can't really help further about what happened with the folder without more information.

As for GooManager, great that another app is working for you. Twrp was always meant to be open for others to make their own apps. The thing that we like about Goo is the integration to their hosting service to make rom updating and installation and updates of recovery easy.
[TouchPad Development] sstar:
Just tried with Rom Toolbox lite and has pretty much the same capabilities as pro apart from automatically checking for updates but this can be done manually , it really works very well TWRP especially the naming /renaming of backups .
[TouchPad Development] nevertells2:
Tried looking for it and did not have any luck. If you can post a link when you get a chance would be appreciated, after the vacation of course.;)
[TouchPad Development] abomb78:
This is my first experience with the Touch pad and I am liking it. I picked it up on Tuesday and loaded up the CM9 nightly 12-23. I am familiar with the CWM through messing with my now backup phone (Atrix 4G) and initially used it on here. I downloaded Goo and installed the TWRP yesterday and saw that CWM was no longer an option. I just completed a backup through the latest TWRP without issue. The touch screen feature is nice, but is this as effective at restoring backups and installing newer rooms such as CM10 when it goes stable or perhaps the next CM9 nightly, as I know CWM is?
[TouchPad Development] bananagranola:
CWM is still an option, just not from Goo Manager (I don't think it ever has been as far as I know). Get it from goo.im/devs/jcsullins/cmtouchpad/recovery. But TWRP is a good recovery as well; it does backups and flashes as well as CWM.
[TouchPad Development] abomb78:
I just didn't see it as an option on my boot loader restart, then again I am new to the Touch Pad. I still think it is cool that I can boot back into WebOS, though I see no reason to at the moment.
[TouchPad Development] sstar:
That is because when you install TWRP via goo manager it automatically removes CMW and edits your default recovery file in the boot folder, the latest CMW zip also removes your previous recovery and edits default recovery file. They both do this in order not overload your boot folder which has a limit of just over 30mb (Can't remember the actual figure ). However you can manually copy an ulimage of CMW to your boot folder and it will appear as an option on your boot loader , this is only something you should do after you have become more familiar with the Touchpad.

Welcome to the xda Touchpad forums ,
[TouchPad Development] abomb78:
Thank you for the welcome. I was unaware of the limit. Now it looks like I should read up on ulimages. Anyone who wishes to fill me in on them or anything else that might improve my Touch Pad experience please send me a PM as I am interested but don't really feel the need to clog up the thread anymore than I already have. I am impressed there are there are people responding so frequently and wanted to share that my experience with installing and running a backup in the latest TWRP worked without issue.
[TouchPad Development] sstar:
This link has some excellent video tutorials http://www.reverendkyle.com/index.php/articles Some are outdated but the basic principal remains the same . You will also find one about ulimage's just enable view all rather than the 10 per page to easily scroll through what's available .

Have fun.
[TouchPad Development] abomb78:
His videos are very informative and I used them to do the CM9 install. I will look a little deeper.
[TouchPad Development] ViViDboarder:
Links with Download Counts

Goo.im

http://goo.im/devs/OpenRecovery/tenderloin

Techerrata

http://techerrata.com/browse/twrp2/tenderloin

Techerrata installs are manual installs while Goo.im are through GooManager.
[TouchPad Development] nevertells2:
I personally have been using TWRP for months and like it a lot better than CWM. I particularly like it better than the new CWM6. CWM6 uses a new and hard to understand method of backing up. It may work OK, but one can no longer copy and delete backups like the old version did and TWRP still does.

---------- Post added at 08:55 PM ---------- Previous post was at 08:49 PM ----------

Thanks man! Sure helps when one knows the correct path to follow. And yes I caught the instructions previously on the TeamWin website about renaming the .img file to uImage.TWRP and pasting it into the /boot folder.

Interesting, 2.3.3.0 isn't getting much interest over in Techerrata. Personally, I am just as comfortable copying the uImage into the /boot folder as installing it from a zip file.
[TouchPad Development] sstar:
VIVIDboarder

As per your request for more information about the folder problem it is being caused by upgrading moboot to either 0.3.7/0.3.8.

Other people are now beginning to notice problems if they were using TWRP and upgrade moboot .

Here is a link to a comment on rootzwiki that probably explains it better http://rootzwiki.com/topic/37783-if...ow-it-works-for-you-good-or-bad/#entry1063962 .

The thread was started by Nevetells so he probably has more info .

I hope this helps explain what happened .
[TouchPad Development] nevertells2:
Just a FYI, I have 2.3.3.0 installed and kept the theme I had been using with version 2.1.1.1 and it still works fine. Using this theme does kill the keyboard function, but honestly, really don't use or need it. I find the default file names created by TWRP perfectly fine. I also think the layout that comes with the theme is a bit more intuitive.

---------- Post added at 03:05 PM ---------- Previous post was at 02:55 PM ----------

Yeah, the changes that J.C. Sullins made in moboot 0.3.7 and 0.3.8 changes the way moboot passes a serial number to Android. For some reason it also causes TWRP to create a new directory under the backup folder that uses this serial number as the folder name instead of the naming convention "0000000000000' that has been used up to now. I went back to 0.3.5 and the backups are saved in the old folder. Don't know if this is something you want to look into or not. To work around this one can just copy previous backups into the new folder and delete the old "0000000000000" folder or revert back to 0.3.5.
[TouchPad Development] ViViDboarder:
The way we retrieve the serial is the same with all devices. Changing it doesn't seem like a good idea just because someone patched moboot. Why did he change it?
[TouchPad Development] sstar:
FYI you can use Rom Toolbox to create/flash/rename and a lot more all still using TWRP.

Thanks for the advice about copying over its exactly what I suggested to someone having the same problem on rootzwiki.

All the best.
[TouchPad Development] nevertells2:
The older versions of moboot were not passing a legitimate serial number and this was screwing up certain games that require a real serial number. Version 0.3.8 fixes an issue in 0.3.7. If there were other issues he was trying to fix, he hasn't let anyone know.
[TouchPad Development] ViViDboarder:
I think we use whatever serial ADB reports... Could you test that? In recovery try adb devices from a computer and see what it says. If it's the serial that twrp is using or not.
[TouchPad Development] nevertells2:
Sorry, never used ADB and don't know how to either. If there is a command I could enter into terminal emulator, I could probably try that. I seem to remember reading somewhere that someone did check the serial number and it was the one passed that was being used as the file name. If it can be checked via TE, I'll be happy to install moboot 0.3.8 again and test it.
[TouchPad Development] overflyer:
Ive been checkin for moboot 0.3.8 on google code and goo.im but i cant find it anywhere :(

New moboot has to be installed with ACMEInstaller right?

EDIT: Soirry im so blind, its in the testing area, so im probably gonna wait till its safe. What the advantages of the new version?
[TouchPad Development] nevertells2:
The only thing I am aware of is it creates and passes a proper serial number to Android that some applications need to function correctly. It is causing problems with TWRP users because it causes TWRP to use a new directory to store backups in and until they figure it out, they freak out. I suppose once it's installed and you copy any backups you created prior to that to the new directory, then you are OK. It may do other things, but the developer is not saying, at least now anywhere I read.
[TouchPad Development] nevertells2:
I am currently running TWRP 2.3.3.0 using the only theme I have found. Using this theme borks the on screen keyboard but I think provides a more Android like UI. I am perfectly happy with the default filename given by TWRP. If I really needed a different name, I would just use a file browser to change it. All that said, I was just wondering if anyone had seen any other themes for TWRP?
[TouchPad Development] sstar:
I didn't even know there is a choice ,all I can see when I boot into TWRP is reload theme in advanced . Is there a way to change it?
[TouchPad Development] nevertells2:
I believe you mean, " Reload UI". To have a theme, one has to create a folder in the TWRP folder named Theme and put the ui.zip theme in that folder.