yashsingh1/xdaforums huggingface dataset:
[Sony Xperia P, U, Sola, Go] ntduyphuong:
Playstation Ceritified is the name of a program started by Sony, to assure that the Android device is able to run the content from Playstation Store smoothly.

So, it's kind of a certification, not an installable application.
[Sony Xperia P, U, Sola, Go] poo-tang:
The certification are just permission files in system to enable download of ps suite content. They will only add them to devices that are powerful enough to run there content smoothly.

If no ps apps or framework came with your firmware you can install them with my CWM zip package located in the apps section. Just flash in recovery if have it. If not and locked bootloader still you can flash a different regions 73 FTF with flashtool that has the apps and framework pre-installed

CWM package http://xdaforums.com/showthread.php?p=25085326
[Intercept General] RuneMason1:
Okay, so i recently rooted my Intercept so i could remove the crapware. I also tried to tether it so i could use my nook tablet everywhere. I tried https://play.google.com/store/apps/details?id=com.googlecode.android.wifi.tether

this one. and i tried barnacle. I realize now that one problem was that these apps make ad-hoc nets, and some devices don't see them. I didn't get barnacle working, and the other one worked the first time then got errors every time i tried to start it after. Now i've uninstalled those apps and i can't use my wi-fi normally. The check mark is unchecked in the settings and it says Error below it. I click it on and it doesn't work. Help? Any hints? Did i do something stupid?

Mason
[Intercept General] dosangst:
Are you using a rooted ROM?

I've had luck on the Intercept using both Wireless Tether for Root Users and Widgetsoid and adding the widget to the screen with the Wifi Tether Icon.

I've always just done the settings changing the SSID to AndroidAP with open/no security. Using these settings I've had no trouble tethering devices from my TF101 to Windows and Ubuntu laptops.

If you are still having issues, drop me a line and I'll walk you through.

Cheers!
[HTC Wildfire S] eoghan2t7:
Hi guys i would like to release the first beta release of TWRP (Team Win Recovery Project)

This recovery does everything that CWM does but better and quicker here are the features of the recovery

Key Features:

Touchscreen driven with real buttons and drag-to-scroll

XML-based GUI that allows full customization of the layout – true theming!

Settings are saved to the sdcard and persist through reboots

Ability to choose which partitions to back up and which to restore

Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)

What's new in 2.1:

Zip queuing as seen in TWRP 1.1.x is back

Slider control (swipe to confirm most actions aka swipe to wipe)

Lockscreen (with slider to unlock)

Basic file manager (copy, move, delete, and chmod any file)

Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)

Displays sizes of each partition in the backup menu

Added listbox GUI element (currently used for listing time zones)

Updated stock XML layouts to be more consistent and easier to port to different resolutions

XML layout files are significantly smaller

Partitions available backup are more accurate for some devices

Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)

Fixed a bug with blkid detection code

Fixed bug where a blank line was inserted between every line of text during zip installs

Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install

Added setting for themers to toggle simulation mode to make theming easier

New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy

Added support for .jpg images in the theme engine

Changed images for stock tablet theme - makes tablet builds about 500KB smaller

Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller

Screen Shots

Download:

Recovery.img

Hboot Zip

XML For translations

Tranlate only the tags inclosed in please.

Installation:

Reboot into bootloader and flash via fastboot command:

fastboot flash recovery recovery.img

linux

sudo fastboot flash recovery recovery.img

Credits:

Core twrp 2 development team: agrabren, Dees_Troy, ViViDboarder, and AssassinsLament

Special thanks to Dees_Troys For all the help via IRC and PM in porting this ;)

If you like this recovery please donate as it will help me do more and update it as offten as possible ;)

​
[HTC Wildfire S] eoghan2t7:
Reserved ;)
[HTC Wildfire S] rezo609:
I realy dont thank people but this is amazing :)
[HTC Wildfire S] Deleted member 4526420:
Is it full touch control? Or can it also be controlled with hard key buttons?

WFS seems to have a big touch screen issues. Not to mention including mine.
[HTC Wildfire S] eoghan2t7:
Its full touch control ;). What kind of touch problem?
[HTC Wildfire S] junxracr:
Tried to flash in fasboot, but say's FAILED <remote: not allowed>.
[HTC Wildfire S] eoghan2t7:
Are you bootloader unlocked?
[HTC Wildfire S] Deleted member 4526420:
The random screen touching by itself on the lower right and left corner of the screen (I know because I turned screen touches on CM9) when it is plugged via USB or AC, and sometimes even unplugged. Had to lock and unlock the phone to fix it. :cool:
[HTC Wildfire S] eoghan2t7:
Don't think you should get these problems in recovery it uses different code etc
[HTC Wildfire S] aigaming:
Verry nice idea,GJ
[HTC Wildfire S] junxracr:
I was unlocked, but after flashing vm update it now say's locked at the top. I hope it didn't locked my bootloader. I'm still s-off and able to flash rom's and such. By the way I tried this on marvelc.
[HTC Wildfire S] kalaker:
What HBOOT version?
[HTC Wildfire S] rejectedsup:
Yeah your bootloader is locked, i did the same thing earlier today (on purpose).

just got to go back in and redo everything. I used the unlocker on htcdev myself but thats up to you. I just wanted stock on my phone for my upcoming trip.
[HTC Wildfire S] junxracr:
It was 1.09 or something like that. Now it is 1.10 something.
[HTC Wildfire S] intel007:
Don't worry mate, that's normal.

My phone is the same after the latest update, but as its s-off just ignore the locked message in boot loader.

Good job Eoghan
[HTC Wildfire S] *se-nsei.:
Cool. Why is it still in beta, is everything functional?
[HTC Wildfire S] sttugut:
WFS s-off

writing 'recovery'... FAILED (remote: not allowed)
[HTC Wildfire S] eoghan2t7:
You need bootloader unlocked ill be uploading a zip to install via hboot later
[HTC Wildfire S] AceRoom:
There's a small typo in the fastboot command for linux in the OP.

The recovery works well! Thanks! Time to change the sig ;)

Small question. What is Wipe->Rotation?
[HTC Wildfire S] eoghan2t7:
Thanks for the typo information ;) and wipe rotation I don't no unless it resets the accelerometer to default maybe.
[HTC Wildfire S] eoghan2t7:
Most things work apart from mounting sdext during backup you need to mount it via the mount menu
[HTC Wildfire S] daxiaamu:
how to make it into chinese language

how to make it into chinese language？？
[HTC Wildfire S] eoghan2t7:
I'll upload the themes xml for users to modify with there language and make separate versions with there language
[HTC Wildfire S] vatamanyuk:
I can make translations to Ukrainian and Russian languages :)
[HTC Wildfire S] ghekua:
For WFS with S-ON, Bootloader Unlocked, the command to flash should be like this:

Right click in the blank space of fastboot folder, choose open a windows command here, then follow:

If you are on HBOOT-1.08.0099:

fastboot -c "mtdparts=msm_nand:0x00100000@0x1ff00000(misc),0x00500000@0x02fc0000(recovery),0x00340000@0x034c0000(boot),0x10400000@0x03800000(system),0x02300000@0x13c00000(cache),0x09600000@0x16900000(userdata),0x00a00000@0x15f00000(devlog),0x00080000@0x02b00000(hboot)" boot recovery.img

If you are on HBOOT-1.09.0099:

fastboot -c "mtdparts=msm_nand:0x000a0000@0x1ff60000(misc),0x00500000@0x026c0000(recovery),0x00340000@0x02bc0000(boot),0x10d60000@0x02f00000(system),0x02300000@0x13c60000(cache),0x09600000@0x16960000(userdata),0x00a00000@0x15f60000(devlog),0x00080000@0x02400000(hboot)" boot recovery.img

Then u can flash and get full touch recovery control!
[HTC Wildfire S] AceRoom:
The command posted by eoghan works perfectly. I have BL-Unlocked S-ON with HBOOT-1.08.0099.

Unless I'm missing something of course?
[HTC Wildfire S] kalaker:
I don't know if this is a bug or not, but on Marvelc (VMUSA) the permissions fix takes quite a long time (much longer than CWM). After about 10 minutes of no change, I eventually just pulled the battery from my device. I didn't know if that was normal or not.

Other that issue (and the known SDEXT issue) this recovery works very well!
[HTC Wildfire S] xVesica:
Checking this out now. :D
[HTC Wildfire S] mars83:
I can go with Polish :)
[HTC Wildfire S] BigChillin:
Is it to early to ask for the hboot zip?
[HTC Wildfire S] eoghan2t7:
Hboot zip added to OP ;) plus the theme xml for users to translate into there desired language.
[HTC Wildfire S] junxracr:
Thank You flashed perfectly.
[HTC Wildfire S] SanderTheNinja:
In cmd I get this: fastboot flash recovery recovery.img

help?
[HTC Wildfire S] insink71:
Nice. Finally a [working] touch recovery on Wildfire S. Going to flash as soon as I download.

Ok.. thought I'd repost this... If you get some kind of Model ID error [on hboot flashable PG76IMG.zip] , go to your last RUU [or FOTA update], extract the android-info.txt, repack it with recovery.img from OP, et voila [no need to sign even].

Recovery works like a champ :)

Rob
[HTC Wildfire S] kagevazquez:
may I ask why its only bl unlock I thought s-off would unlock everything
[HTC Wildfire S] insink71:
Quick question on your challenge [with s-off], have you checked/unchecked the usb debugging flag in settings -> application -> development? That flag often trips me up when I don't pay it close enough attention.

The only other flag that has rarely [but sometimes] given me grief is the fastboot flag itself under settings->power menu.

Well, those are the only things on the android device itself [udev could be a chapter of support, depending on linux variant &/or build]...

Don't know why you can't flash an .img with [radio] s-off; methinks it should be possible and plausible [but stuff sometimes changes.. like newer encrypted hboots ;) ]

Regards,

Rob
[HTC Wildfire S] theq86:
I can not make a nandroid backup.

ext4 sd-ext could not be mounted. does the kernel support it?

---------- Post added at 05:42 PM ---------- Previous post was at 05:37 PM ----------

That's wrong and has nothing to do with installing a recovery.

These fastboot commands will mount HBOOT as mtd7 and are part of our progress developing a software s-off solution.

You can not harm your device if you issue these commands, since every write access will be rejected. However, there's no need to use them and it has absolutely no effect ;-)
[HTC Wildfire S] eoghan2t7:
You need to manually mount the ext partition in the mounts menu I'm still trying to fix it to auto mount on recovery boot.
[HTC Wildfire S] junxracr:
When I tried to do restore it only showed recent backups, but not the ones from the other recovery.
[HTC Wildfire S] eoghan2t7:
From what other recovery if you came from clockworkmod the backups save to the clockworkmod folder on the sdcard in .img and .tar formats TWRP saves backups in the TWRP folder in .win format. TWRP will not restore backups made form CWM or RZ Recovery, They maybe based off CWM but they are heavily customized version with there own backup locations and therfore are not cross compatible at present.
[HTC Wildfire S] junxracr:
I use alquez 5.0.2.6 unofficial recovery. Thanks for the info.
[HTC Wildfire S] BigChillin:
They're stored in different places. One in clockworkmod/backups and the other in TWRP/backups. They might even be different formats. But move one and try ;)

Edit...I type slowlyyyyy
[HTC Wildfire S] kagevazquez:
I'm still sad this doesn't work for s-off and I'm wondering why
[HTC Wildfire S] kalaker:
Do you mean flashing this in fastboot?

(Like with the command fastboot flash recovery recovery.img)

If so, it's a pretty simple answer (if not annoying): Even if S-OFF, HBOOT (no matter which version 1.09, 1.10, or any other) will not accept fastboot commands if your bootloader is not unlocked. You can flash any PG76IMG.zip, but no fastboot command is accepted. Our best hope would be an ENG HBOOT.
[HTC Wildfire S] kalaker:
What do we do with UI.xml once translated?
[HTC Wildfire S] eoghan2t7:
Send me it ;)
[HTC Wildfire S] honda_hany:
not working for me i get cid error
[HTC Wildfire S] :
i was wondering, is the source up? I know twrp is open source and i kind of wanted to take a look and optimize for cdma variant. In other words, which folder did you use?
[HTC Wildfire S] eoghan2t7:
i used this folder

https://github.com/TeamWin/Team-Win-Recovery-Project

and used this guide

http://rootzwiki.com/topic/23903-how-to-compile-twrp-from-source/
[HTC Wildfire S] rejectedsup:
Used for root on my marvelc(vm) and it worked great! replaced cwm_recovery file with alquez 5.0.2.6 unofficial recovery (had to rename the .img file of course) thanks for all your time put into this made it alot easier.
[HTC Wildfire S] lichong000000:
这个怎么不能刷aroma的rom
[HTC Wildfire S] rezo609:
English Please :)
[HTC Wildfire S] benjamingwynn:
@op could you point me to the sources used to compile this :)
[HTC Wildfire S] eoghan2t7:
heres where i got the sources read the guide 2 or 3 times it got me comfused at points lol
[HTC Wildfire S] KelvinWild:
Hi!

I have wfs a510e, UNLOCKED, s-on, hboot 1.09.0099

fastboot: sending recovery, writing recovery OKAY.

After this when I choose recovery menu the HTC logo comes up and frozes.

any idea?

thank you

---------- Post added at 12:46 PM ---------- Previous post was at 12:42 PM ----------

Can somebody explain plz how to exactly do this.

On totalcommander I cant see such a ,,open a windows command here,, option.
[HTC Wildfire S] sukhjit321:
link down
[HTC Wildfire S] eoghan2t7:
Fixed
[HTC Wildfire S] miso00:
Is it compatible with nandroid backup from CWM ?
[HTC Wildfire S] eoghan2t7:
no not at the moment and im unsure weather the developers will add the support.
[HTC Wildfire S] benjamingwynn:
Hey could you compile this with an option in your prop to make it load zips directly not side load them into /tmp.

You might want to ask for the exact flag on #twrp on free node.
[HTC Wildfire S] eoghan2t7:
do you mean to more or less add rom manager support?
[HTC Wildfire S] benjamingwynn:
No

More like not to move roms to /tmp to install them. This brakes aroma zipa.
[HTC Wildfire S] eoghan2t7:
Sorry I don't understand how it breaks aroma could you explain more please?
[HTC Wildfire S] insink71:
This recovery is pretty darn amazing. Although it works on marvelc, I'd like to help get it to 100% [for marvelc assert roms like cm, etc] if you don't mind the help. Have an idea on the automount as well.

Rob

PS I've installed aroma zips from this [mounts2sd, etc] without issue
[HTC Wildfire S] sidthegreatest:
Any plans to update TWRP to 2.2 ?

Anyways, thanks for this, way better than CWM :)
[HTC Wildfire S] eoghan2t7:
Yes ill be doing verious versions tomorrow for users with different ext formats etc to beat the ext not mounting problem
[HTC Wildfire S] WoefulDerelict:
Oh my, how unexpected. 12 hours you say?

Different ext formats? Different how? Glad there are people working on this.
[HTC Wildfire S] eoghan2t7:
There is mounting problems with users that use data2sd and that the ext partition doesn't backup or restore etc. So I will make different versions for ext running fat32,ext2,ext3,ext4 that way the sdcards second partition will mount and backup and restore ;)
[HTC Wildfire S] insink71:
Different as in ppl may choose to format /sd-ext differently.. ext2, ext3 or ext4.. the auto [detect] setting not playing well, but if you assign one of aforementioned, it plays better.. Challenge then is post diff versions, or keep hacking at the auto setting ;)

Rob
[HTC Wildfire S] WoefulDerelict:
More questions.

... or some kind of try/fail blob that attempts to mount the partition with a predefined type moves on after fail. Certainly a hacky, messy solution.

Is there a lead as to why it's having such trouble auto-mounting? Is this issue isolated to the Marvel platform?
[HTC Wildfire S] eoghan2t7:
Its nothing to do with the marvel platform its the twrp code I just haven't tracked down the sections of code to make it auto mount :(
[HTC Wildfire S] WoefulDerelict:
Gotcha.

Well, now I know where to keep looking. :)

There were quite a few changes between 2.1.8 and 2.2 and I still haven't crawled through all of the new source.

What environment are you using? CM 7.2? Kernel?
[HTC Wildfire S] benjamingwynn:
Could you remove the flag that copies the file to /tmp please? Ask in #twrp :) this is really important to me too. Thanks :D
[HTC Wildfire S] eoghan2t7:
There is no build flag for /tmp I don't think but ill look after I edit the theme because are screen size doesn't support the on screen keyboard.

EDIT: found out how to flash the zips from current location instead of going to /tmp ;)
[HTC Wildfire S] eoghan2t7:
ok that 12 hour deadline will not be the deadline im getting loads of compile errors which i need to fix first :(
[HTC Wildfire S] WoefulDerelict:
You don't say.

Welcome to my club. I'm interested in what you've done with the keyboard... I have a feeling the issues I have with my build of TWRP are related to display errors. Been trying to prod at the mount stuff.
[HTC Wildfire S] KelvinWild:
Still havent got answer for my problem :(
[HTC Wildfire S] WoefulDerelict:
It's broken.

If it is successfully flashing and failing to reboot into recovery you have some kind of low level error causing it to get stuck during boot. This is a really tricky project to build and until all the bugs are worked out I'd suggest using CWM unless you're a developer liking to test and contribute to bleeding edge software.
[HTC Wildfire S] insink71:
The screen freeze is typically speaking a boot.img issue or misalignment. Try reflasing your RUU, updating, and on update.. pulling a copy of the update [from cache] This update file will have an android.info file in it [the rom.zip in the ruu will as well]. But whatever your last applied [android.info archive], pair and pack [just] the android.info and recovery.img into a PG76IMG.zip [no need to sign], place it at the root of your sd card [the fat32 partition] and boot to hboot. It will check archive and ask you to confirm installation. So confirm and Et voila. For some reason the PG76IMG.zips have aligned the recoveries for WFS better than a fastboot flash imo.. don't understand why theoretically but they just have. If you get any other anomolies flashing hboot or update, probably another case of a corrupted /sd-ext which also run rampant for our lil phones.. this is the ext2/ext3/ext4 thing discussed previously. [You can temporarily remove the sd card if this is an issue] Basically boils down to stock kernels support ext2 or ext3 and custom kernels can support ext4 even, BUT the journaling in ext3 or ext4 seem to corrupt the /sd-ext over time.

Hope that helps.

Regards,

Rob
[HTC Wildfire S] kalaker:
Just to add my 2¢, I believe Rob means android-info.txt. Not that it matters much, but some people do take things word-for-word here...
[HTC Wildfire S] insink71:
Heh. Indeed. Thanks for the catch.

Rob
[HTC Wildfire S] faZevoLv:
If i replaced the kernel, could this be ported to the htc hero gsm? or am i being stupid.
[HTC Wildfire S] eoghan2t7:
The ramdisk will need edited but I can compile it for your device after I fix the compile errors
[HTC Wildfire S] faZevoLv:
Thankyou so much, this looks great, id love to try it:D
[HTC Wildfire S] eoghan2t7:
No problem I half to finish off too other kernels for other devices then ill get to work on twrp does your phone have any source code on github?
[HTC Wildfire S] faZevoLv:
Im not sure sorry, i dont build from source, just port:)
[HTC Wildfire S] eoghan2t7:
Link me to you device forum please
[HTC Wildfire S] faZevoLv:
http://xdaforums.com/forumdisplay.php?f=512

cheers
[HTC Wildfire S] kiruiy:
"这个怎么不能刷aroma的rom"

maybe it means “ I Can't use this to flash aroma's rom”

---------- Post added at 01:08 PM ---------- Previous post was at 12:48 PM ----------

Would you give me a hand? I want make translations to other languages but not Ukrainian and Russian languages

---------- Post added at 01:17 PM ---------- Previous post was at 01:08 PM ----------

Would you give me a hand? I want make translations to other languages but not Polish
[HTC Wildfire S] Senthamil:
I Have CWM 5.0.2.8 now with CM9 Alpha 7. I'm interested in this Touch Recovery.

I've gone thru this thread but totally confused...!!

Can I take backup and restore as usual...?

Can I Flash ROM & other things as usual..?

How is that coping with ROM Manager....?

Is there any drawbacks????....
[HTC Wildfire S] insink71:
Rom Manager is built by ClockWork Mod. It is built to utilize hooks in CWM recovery.

Koushik (pronounced kush) is the one of the most widely known (and esteemed) recovery gurus and a main cog at ClockWork Mod (and CyanogenMod). He has contributed to several projects though including TWRP.

TWRP is a different open source recovery. Its kind of like choosing a different style car. Will Rom Manager's hooks all work? Most likely not. Is it a customizable touchscreen recovery? Yep sure is. Does it work? Yep. Perfectly? Honestly what does work perfectly? There is always room for improvement.. thus the beauty of open source ;)

It works solidly enough from what I tested. If you like the roms database that Rom Manager affords you, stick with cwm.. all depends on taste.. chicken or hamburger.. you get the point. :)

Rob

PS You can make backups and flash roms.. the backups aren't neccessarily going to be the same as cwm bc its a different recovery (ie I wouldn't restore a cwm nandroid with twrp or a twrp backup with cwm.. it may work, but I just run a fresh backup so I know its compatible with whatever recovery I might be currently using)

Any recovery should flash a rom.. thats one of their purposes.. to recover.. (when rom flashing is not thought of as a favorite candy) recovery has to flash a base rom or restore a backup or it wouldn't retain its name.. maybe stranded partition if you got an awful one ;) but all the 101 aside, this TWRP was good when I tested it.
[HTC Wildfire S] eoghan2t7:
for up to date builds please go to this thread [RECOVERY] TeamWin Touch Recovery v2.2.2.0 for the HTC Wildfire S as WoefulDerelict has teamed up with the TeamWin team to get this recovery as bug free as possible ;)