yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] WoefulDerelict:
More please...

Could I get the HBOOT, MICROP and Radio version from your SPL? Hold the volume rocker and power button down while turning on the device to access the bootloader for that information.

IF these Frankenstein devices exist I'm going to need a profile of the revised hardware in order to correct the issue along with some proud owners to test fixes as I don't have access to one. The Marvel I was given is based off the original hardware profile and TWRP2.1.8 works fine when built with CM9 and the cryptomilk.org MSM7227 kernel. I'll do what I can to fix it but, I'm currently trying to resolve build issues with the new 2.2 release. I'm hoping this new code base along with a revised kernel will resolve many of the current issues.
[HTC Wildfire S] WoefulDerelict:
It's ALIVE!

The problem is it's behaving like I brought it to life with a couple bolts of lightning. To say that it has issues would be overly kind but, it boots and I can navigate around. I'm currently trying to track down all the shorts making 2.2 twitch. Stay tuned.
[HTC Wildfire S] WoefulDerelict:
Fresh revision.

Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
[HTC Wildfire S] eoghan2t7:
Thanks but theres a few issues

1. Theme isn't updated

2. On-screen keyboard wont work due to current theme

3 l. Swipe to start backups/restoring wont work due the theme.

More or less this is just like the previous twrp until themes are resized etc :(
[HTC Wildfire S] WoefulDerelict:
Yea, I knew that.

This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
[HTC Wildfire S] eoghan2t7:
Yeah the themes are XML based but the image editing will be the worst part ;)
[HTC Wildfire S] WoefulDerelict:
I'm trying to imagine that being easy. I'm not totally inept in Adobe or AutoCad products so I'm sure I can toss together something in a week or so. Depends on how much the real job needs my time and brain meats.
[HTC Wildfire S] WoefulDerelict:
This community is certainly not without it's provisos; however, I can't say that I've seen a great many users display much awareness or respect for them. I certainly see no point in being an ass about language. While I can certainly appreciate the intent I find it obnoxious to add to the superfluous prattle polluting my thread to scold someone for not taking the time to run what they have to say through a translator for me. I'd personally rather wade through good french than attempt to wrap my head around even more bad english. If a user doesn't speak or write english I'd prefer they express themselves as best they can in their native language and then include a gist translation below but, I'm more than capable of feeding it to a gist engine myself. As this thread could easily be pruned down to it's OP without the loss of pertinent information to moving the project forward I'd really rather not see the problem exacerbated.
[HTC Wildfire S] WoefulDerelict:
Freshly brewed!

Discovered a change in the code structure that may have negatively impacted the dynamic library binding. Corrected the issue and generated a dedicated environment for MarvelC builds. Uploaded fresh files for users to test. Enjoy!
[HTC Wildfire S] broncogr:
On the subject of language, only English is allowed on XDA.

You can write your post in whatever language as long as its followed by an English translation.

Other than that, thread cleaned.
[HTC Wildfire S] WoefulDerelict:
The madness begins...

For those interested in this branch of TWRP I'm currently working to port the new theme to the 320x480 devices. I'd spoken with some of the people involved in the project and while someone had volunteered to port it they haven't come through. I've managed to successfully scale the new set of UI images and I'm currently stepping through the XML to get it working. With any luck I'll have a new build out by week's end for users to test. Big thanks to broncogr for tidying things up around here.

Still poking at the format bug but, no real leads on the root of the issue or how to resolve it at present. The off-line charging issue likely resides in the Cryptomilk code and will hopefully see a fix before long.

Big thanks to all the users that have volunteered to test and provided me with feedback. Hopefully there will be a stable, issue free build ready for everyone to enjoy soon.
[HTC Wildfire S] WoefulDerelict:
Delivering the WIN!

As promised, there are fresh builds containing a bright and shiny 2.2 theme scaled and ported by lil ol me. Finally, you'll get to see all the new features that were supposed to be included in the 2.2 update. I believe all the known issues still remain at large. I suspect more may pour in now that there are so many more features for users to test and break. Stay tuned!
[HTC Wildfire S] WoefulDerelict:
New release!

Latest version of TWRP with a few minor bug fixes to go along with my spiffy new 2.2 compliant theme for 320x480 devices. Users can and should use the simulation feature when testing the UI. List of known issues has been updated to reflect issues in this release.
[HTC Wildfire S] WoefulDerelict:
Ratings?

How am I even supposed to interpret a blind poor rating? I guess one star is better than no stars. :p

I smell a rat or a big fat troll. Guy can't do anything nice for you kids without someone taking cheap shots. Sheesh, smoke a blunt and chill er sumthin.
[HTC Wildfire S] insink71:
I will say that I'm impressed by your:

1. Research.. You asked on Eoghan's (original release of TWRP for Wildfire S) thread, etc..

2. Willingness to admit bugs and most impressively fix them

3. (Restatement) You are not just kanging other's work and throwing it up; You are actually attempting to make a nice workable version of TWRP for the whole Wildfire S family.

Haven't flashed of yet, but I'll test/help on marvelc.

I will also say this as an aside (not for op of this thread but for others).. Open source I like to think of as community owned. I hear devs squealing about their work. Well, its volunteer and as soon as its released; its not "yours" anymore. Besides didn't the lion share of what you claim as "your work" come from Google or downstream from Cyanogenmod.. or TWRP team.. These people or teams are often thanked and dismissed, but they built the tool.. More or less what "devs" do is build a tree to define hardware to that tool, write configuration files.. and occasionally do find a way to make tool act better and commit it back upstream. I am a bit sick of all the in-fighting and bickering.. Yes, sometimes trees are tedious and take months to build; These devs should be applauded, but the high horses some have got on of late.. It saddens me.

Blind rated you 5 without testing.. just to balance things out. Don't be discouraged. You're doing a fantastic job.

Rob
[HTC Wildfire S] WoefulDerelict:
So many stars...

I spent some time with my vape, enjoyed myself a brief nap and my thread jumped from one star to four... big thanks for that. :silly:

Special shout out to insink71 for all the props. Best of luck testing and I look forward to the feedback. I really do need more MarvelC test data. Honestly, while I may have a computer science background somewhere in my past I certainly don't regard myself as a developer nor do I regard the work as my own. I'm right there with you scratching my head as to how one could become so possessive of work they've only made a minor contribution to. I feel a great deal more like the guy at the end of the assembly line putting all the pieces together. The people upstream definitely deserve the majority of the credit for producing and maintaining the components. The only real work I've put in thus far was the updated theme and that was just some XML editing coupled with running all the images through the GIMP and scaling them. Once I'm satisfied with the feedback from that effort I plan to submit it back to the TWRP team for use with all 320x480 devices. The rest of my efforts have all been as coordinator and detective trying to track down bugs and find solutions.
[HTC Wildfire S] eoghan2t7:
Have you figured out how to fix the rest of the remaining bug?

P.s. download link wont work
[HTC Wildfire S] WoefulDerelict:
No sir, I'm probably tackling too many at once but, I've not figured out how to resolve the rest of the issues yet. Some of the people I need to talk to are only now becoming available and I've been a bit busy with other projects.

As of this writing I was able to access the files and spot an anonymous user accessing it as well. I'm not sure why you would have issues with the link. Sorry.
[HTC Wildfire S] king_lud:
Just flashed this to my A510e without any issues and made my first backup. Was impressed at how much faster than CWM it is!

Thanks for all your work!
[HTC Wildfire S] WoefulDerelict:
2.2.1.5 Drop

Dees-Troy, one of the TWRP developers, just dropped some changes that he hopes will address some of the issues with sd-ext. I'll have some new builds available once I've had a chance to test them.

Update: Dees-Troy has picked up a HeroC for testing and is finding many of the same issues. Recent changes fix the backup issue. None of the new changes fix the SD-EXT issues and there haven't been any updates on the kernel front. I'll have the files up for users before long.
[HTC Wildfire S] iH8ra!n:
ROM Manger

Hi Dudes, is that TWRP with ROM Manager compatible? Means, can you choose in ROM Manager "Save this ROM" and it will automatically work with this Recovery or does it say "You hav no compatible CWM installed, would you like me to install for you?" ? I ask because the unofficial CWMR 6.0.0.3 wasn't compatible, fixed with 6.0.0.7.
[HTC Wildfire S] WoefulDerelict:
Wrong thread!

This is a support question and does not belong in this thread. If you follow this link over to the support thread you will find your answer there.
[HTC Wildfire S] WoefulDerelict:
Offmode charging fixed.

Kalaker managed to quickly spot why offmode charging wasn't working. A quick change to the new init.htc.rc created back on 17/7 fixes the problem. As you can see it's been disabled, removing that line fixed the issue.
[HTC Wildfire S] eoghan2t7:
Could you mirror the marvel version on a different server Google drive doesn't work for me :(
[HTC Wildfire S] WoefulDerelict:
Do you have a suggestion? I'm just using what I have available that's friendly. No weird pop-ups, ads or other ****e. Does Dropbox work for you? I can mirror it there with ease.
[HTC Wildfire S] eoghan2t7:
Yeah db works for me thanks
[HTC Wildfire S] WoefulDerelict:
Glad it works for you. I'll try to keep builds mirrored there.
[HTC Wildfire S] eoghan2t7:
I have tested this for the fast few days and so far so good no formatting problem for me my SD-EXT formats properly for some reason. my sd-ext is formatted to ext4 in case you want to no ;)
[HTC Wildfire S] king_lud:
I just notice in the OP that the latest items in the Changelog have the wrong dates - they should be August, not July.

Hope you don't mind me pointing this out.
[HTC Wildfire S] WoefulDerelict:
Nope, gets it fixed quicker.
[HTC Wildfire S] WoefulDerelict:
Status updates...

I've managed to track the issue regarding corrupted EXT4 file-systems when TWRP is asked to partition the SD Card to it's root. Currently TWRP uses an external script, /sbin/sdparted, to handle the partitioning of the SD Card. This was borrowed from CM and relies on parted to create and format new partitions. As parted lacks support for ext3/4 file-systems the script then calls tune2fs to perform the in-place upgrades to your desired file-system. The upgrade from ext2/3 to ext4 is a bit messy and requires e2fsck to clean up after it. e2fsck is called with the preen option and fails because it believes the work necessary to clean up the upgraded file-system is beyond that scope. Calling e2fsck with the yes option instead results in the operation competing successfully. While this single character change does fix the issue it is unlikely you will see it.

Dees_Troy is currently working to clean up the TWRP code and unify the majority of TWRP functions. It is likely that /sbin/sdparted will be abandoned for internal code. He has already authored code to format the new partitions in TWRP instead of relying on /sbin/sdparted and those are likely the changes users will see.

Dees_Troy believes we have finally found the root of the direct SD-EXT wipe issue. I should know more about that later.

UPDATE: After testing the changes in an image Dees_Troy sent to me I can verify the death of all the SD-EXT bugs. The man has a bit of house keeping he wants to do before pushing the changes to the mainstream code. I'll publish builds once that code is available. It's highly possible the Marvel and MarvelC could become officially supported in GooManager thanks to Modpunk's awesome repo.
[HTC Wildfire S] WoefulDerelict:
TWRP 2.2.2.0 Available later today... AND MORE!

Dropping some good news and a fresh build later on today. Thanks to some amazing work from Dees_Troy and the rest of the TWRP team SD-EXT support has been polished and now behaves reliably. I'll be uploading a build from the latest sources once I finish adjusting the 320x480 theme.

The most compelling news; however, isn't that builds of the newest software will be available here but, that stable builds will be available directly from TeamWin and via GooManager in the very near future. This will make it much easier for the average user to acquire and install TWRP on their Wildfire S. I don't have an ETA as yet but, very soon.
[HTC Wildfire S] edwinrodriguez810:
I know u are a busy person but was u able to release the new updated recovery that u was able to fix ext4?
[HTC Wildfire S] WoefulDerelict:
Sorry.

It will be up a little bit later today. My evening turned out to be busier than I had initially anticipated and I wasn't able to finish working with the XML.

The UI contains over 30 'pages' and 3,500 lines of XML to describe them. The original theme was a near perfect scale of the larger 480x800 theme; however, the design choices initially made with that vertical space don't fit our devices. I've made changes to just about every aspect of the theme as it just didn't look or feel right on the device. rallapag contributed a-lot of helpful ideas but, integrating them into a proper default theme that will properly support all of TWRP's features on any 320x480 device so that it can be merged back into the source is time consuming.

I still need to test and correct issues caused by my changes before releasing the product to the community. I'd check back around 18:00 PST.
[HTC Wildfire S] WoefulDerelict:
2.2.2.0 Preview Release.

This release contains all of the recent upstream fixes and the main portion of the UI updates. I still need to complete the UI overhaul for many of the interstitial confirmation and action pages as well as the file manager and pseudo-terminal features but, the main pages have been finalised and are ready for testing and feedback. It's very easy to test this image without flashing it to your device using the fastboot command with the boot option. Remember TWRP offers a simulation mode under Settings for theme testing.

I will try to integrate as many suggestions into the final 2.2.2.0 release as possible. It should be ready soon.
[HTC Wildfire S] WoefulDerelict:
Attention MarvelC Users.

I'm in need of a few MarvelC users who are passionate about bleeding edge software and would like to access to early release builds from me and TeamWin. You will need to have a functional set of android debugging tools, be able to follow an English test script, be willing to incur the wear overhead on your NAND and SD using the partition, wipe and install features.
[HTC Wildfire S] faZevoLv:
Are the kernels different between the marvel and marvelc? because I ported CWM 5 from the htc hero cdma (heroc) to the hero GSM by simply replacing the kernel with the latest hero GSM kernel from within the .img file and it worked perfectly!:)

Hope that helps and gives marvelc users TWRP quicker;)
[HTC Wildfire S] WoefulDerelict:
It isn't a problem of getting TWRP built for the MarvelC it's an issue of proving that the builds work as no one on the team has a device to test on. We'd like to verify the build works in every way that it should before releasing it via GooManager.

CDMA users have been rather quiet but, I'd figure one of them would say something if the build I'm offering wasn't working. A quiet nod of ascension; however, is not proper grounds to release a crucial piece of software to the general public. At least, not in the eyes of this team and I'm just fine with that.
[HTC Wildfire S] faZevoLv:
Ah right it doesn't matter then:)
[HTC Wildfire S] edwinrodriguez810:
Ill try it out
[HTC Wildfire S] eoghan2t7:
looks like we got added to TWRP devices page http://teamw.in/project/twrp2/111 and is installable via goo manger
[HTC Wildfire S] king_lud:
'Official' status is great news - congratulations to all involved in the development :D
[HTC Wildfire S] WoefulDerelict:
It's very nice. I should have probably posted the link to the Marvel page but, I figured people would find their way there. MarvelC should be available and have a web page of it's own very soon.
[HTC Wildfire S] insink71:
Be happy to test for you WD.. have both VM USA & Metro PCS wfs devices. And if it shan't work on one marvelc variant or the other (us cellular is same device as vm USA).. willing to donate some time too; I always like learning.

Rob

PS. Only issue I have ever had with (well-made) marvel recoveries.. would be assert roms. Have to rewrite board references to marvelc. I know some say there are "major differences" but haven't seen them recovery wise.. Rom wise, inc framework, radio, etc wise yeah major differences, but alquez's recovery worked (better than official marvelc for a time).. so it would be fun peeling back the layers and seeing what recovery differences there are.
[HTC Wildfire S] csoulr666:
Fair Warning

I just wanted to give a warning to users who want to update to v2.3.1.0(it's on the official Team Win website)......You wont be able to flash old flashable zips with the new version..
[HTC Wildfire S] eoghan2t7:
all zips i have flash perfectly so far so hopefully its only a glitch ;)
[HTC Wildfire S] caseyatbt:
I get errors using 2.2.2.0, 2.3.0.0 and 2.3.1.0.
[HTC Wildfire S] SulthanSuperTramp:
tried to download 2.3.3.0 from teamwin site but the download is stuck at 99.9 %
[HTC Wildfire S] icu64:
Use goo manager
[HTC Wildfire S] ScardracS:
With twrp 2.2.1 and newer you can't install some script like int2ext

Powered by my Thunderbolt (This isn't spam, this is my signature)
[HTC Wildfire S] SulthanSuperTramp:
i use 2.2.2.0 and int2ext 4+ works :D
[HTC Wildfire S] ScardracS:
I try to install in2ext, int2ext+, int2extV2+ and i can't install them

Powered by my Thunderbolt (This isn't spam, this is my signature)
[HTC Wildfire S] csoulr666:
Happens with me as well.....so I had to manually push it and give it permissions......it isn't hard that way either
[HTC Wildfire S] :
Anyone able to update it to 2.6? Official stopped at 2.3

Verstuurd van mijn HTC Wildfire S A510e
[HTC Wildfire S] Olivier:
Nope, I'm still using v2.2 and I don't think we'll get more updates.
[HTC Wildfire S] :
Its just a matter of compiling it. I can't cause I don't have the tools and I'm lazy :p

Verstuurd van mijn HTC Wildfire S A510e
[HTC Wildfire S] Olivier:
Me too. :laugh:
[HTC Wildfire S] izi501:
I can but I need a guide because I never did that I my life :P

And I would love to get TWRP 2.6 too :)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 et Tapatalk 4 ;)
[HTC Wildfire S] crazy4creationstudios:
Thank you for the download! And thanks for using a good download server as well

Sent from my backup phone (Huawei M835 running stock Android 2.2)
[Galaxy S II Q&A, Help & Troubleshooting] bazz7777777:
My home button sometimes sticks down, I want to change it, I have ordered parts off eBay, the black button and also the button ribbon cable that gos underneath, I've been watching strip down videos on YouTube, it looks like you have to remove the whole screen to remove the home button, I just wonder if anybody has any experience on replacing the home button, any help will be appreciated
[Galaxy S II Q&A, Help & Troubleshooting] miisterlim:
I didn't replace my home button, but I did replace my broken screen. My advice to you would be to watch those YouTube tutorial videos thoroughly and make sure you know the steps involved. And also take extra care when prying the screen off, you don't want to break it. Just take your time and good luck.
[Galaxy S II Q&A, Help & Troubleshooting] bazz7777777:
Thanks did you take your screen off with a heat source and how strong is the glue that holds the screen on ?
[Galaxy S II Q&A, Help & Troubleshooting] bazz7777777:
Is there no one who can help, before my parts come and I may *uck up my phone ;-)
[Galaxy S II Q&A, Help & Troubleshooting] eddyecb91:
I just changed my housing keeping the original lcd screen today, i used a hair dryer for heat and a guitar plectrum to pry up the screen, you just gotta be verrrryy careful and it will eventually come off the housing, just keep heating then prying, then heating then prying until it comes off the housing.
[Galaxy S III Accessories] cgardnervt:
Hey Everyone!

From day one I had installed a Moshi iVisor screen protector from ATT. While it went on easy with no bubbles I am warning you not to use it. ATT installed it for me and today when I took it off I had some small scratches in the glass. My bet is some dust got inside and never found its way out. It is a static cling screen protector. So if you have it make sure its always clean. I ony had it on for about a week or so.

Again this is just what I saw and like anything...it could have been my fault for letting ATT do it! :P

So today I installed a ZAGG shield. In hopes I no longer scratch my screen.
[Galaxy S III Accessories] Gadgetz:
So your theory is that people shouldn't use this protector because it allowed a scratch to get through it, onto the screen? :good:
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] kicsrules:
I've had some good and bad experience with some roms, right now i have 2.3.6 ddq8 rom, it's good .. has some pros and cons ... has anyone tried both,, 7.2 rc3 cyanogen and 2.3.6 ??? which is better....??

need to work properly:

- battery

- speed

- camera

- gps
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Cryss:
Last KTM Spain Stock rom is better than DQ8 and has lockscreen bugs fixed.

Battery is (from what i've tested) better

Speed ... better

GPS ... good, like DQ8
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] kicsrules:
thnx will try that one...
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] Cryss:
U will not regret it ! :P
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] kicsrules:
report back in a while ...
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] dxppxd:
Tried them both, still prefer cm7.

I don't care that much about battery life, and the customization is insane. Daily use Apocalypse rom, very stable if you don't overclock it.
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] -Meteor-:
You can't really compare them, as they are to different things

CM7:

-Speed

-Themes

-More features

Stock:

- IT JUST WORKS:cool:

BTW:MY FIRST POST ;)
[Galaxy Ace S5830 Q&A, Help & Troubleshooting] ROMFlasherAce:
The cm7 ROMs r not quite speedy now after the release of recent stock ROMs :p:p:p

Btw, i personally think that CM7 ROMs excel at sound quality becoz of the libs, the stock music quality sounds awful