yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] gavin-phelan:
Re: [RECOVERY] TWRP 2.3.3.0 touch recovery [2012-12-19]

Heres a direct link for i9300

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

Sent from my GT-I9300
[Galaxy S III Original Android Development] jonny68:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

+1 much easier to have Flash able zip
[Galaxy S III Original Android Development] Yank555:
Here you go...

If it's not OK to publish this, please let me know or have this post deleted.

JP.
[Galaxy S III Original Android Development] mattiadj:
R: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Is sudden death fixed in this latest?

From universe with my gs3
[Galaxy S III Original Android Development] Yank555:
First line in the OP ;)

JP.
[Galaxy S III Original Android Development] mattiadj:
R: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Totally blink yank sorry!

From universe with my gs3
[Galaxy S III Original Android Development] v3n3:
1 or 2 Pages back there has been a question related to MassStorage Mounting for the i9300, with the later on required files to accomplish this.

Has this been merged ( / fixed ) yet ?

Would really love to use TWRP, but since it doesnt have this function :-x
[Galaxy S III Original Android Development] qwerty12:
No, it hasn't, and when I'm ignored, it makes me wonder why I donated.

EDIT: Since I'm probably going to get **** on for that, I do not expect an instant release with the feature added in. What I do expect, however, is acknowledgement, either in the form of "yes, it will be added in a future release, to be released next week or next year" or "no, you can add it in yourself".
[Galaxy S III Original Android Development] beardymarrow:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Donated ! = purchased :P
[Galaxy S III Original Android Development] Perka:
You donate for work that has been done, not for future work ;)
[Galaxy S III Original Android Development] ArbiterGR:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

You sir are totally wrong. Donating to a dev, is a form of saying "thank you for the awesome work dude!" you can't demand or expect anything.
[Galaxy S III Original Android Development] qwerty12:
[RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

To clarify: I am aware that a donation does not entitle you to work (and, truth be told, if I wanted code written for me I would've paid more than I did); however, when I've taken the time to find the information that was being asked for (since nobody else bothered), and I've not leeched this work by supporting it a little in the past, then I tend to get annoyed when I'm ignored. My initial post made it clear that I wasn't asking for anything strenuous, and I don't think what I was asking for is unfair of me. It's time-consuming to produce a new build (which I do constitute as work), I totally get that, but a reply saying "yes, now it's possible to enable this feature; however, I am lacking the time to do this so you may not see the build for two years" or "no, I cannot do this" is not.
[Galaxy S III Original Android Development] sebarkh:
Odp: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

First check what

!=

means.

Then reply.

!= means "NOT equal".
[Galaxy S III Original Android Development] beardymarrow:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

You misunderstand me Sir. I completely agree with you.

---------- Post added at 08:14 PM ---------- Previous post was at 08:10 PM ----------

I understand. I guess it was the "makes me wonder why I donated" that got my goat. I agree with the general sentiment though, if not the choice of words. :)
[Galaxy S III Original Android Development] JDogg1329:
I'd like an answer on the USB storage question too.......
[Galaxy S III Original Android Development] gsw5700:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Wicked, many thanks, now got twrp 2.3 on my s3 and n7. Folks, don't forget to setup the backups as you want them (use external SD card, use compression, backup efs etc etc)
[Galaxy S III Original Android Development] Glebun:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Can we get some comment about the vrtheme issue? is it going to be fixed sometime soon?

switched to PhilZ recovery in the meantime
[Galaxy S III Original Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

http://teamw.in/VRThemes

The theme maker is using an old version of vrtheme. You can fix it yourself as outlined in the link above & ask the theme dev to update. It's a very simple thing to do but there's nothing within TWRP that I can do to easily fix it.
[Galaxy S III Original Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Most of the stuff in here only applies to Android but I will try to throw a build out with a potential fix.
[Galaxy S III Original Android Development] qwerty12:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Not quite. I know it works in the TWRP environment because I actually tested what I wrote. The LUN path is something provided by the stock Samsung kernel (and CM's I imagine because of Oranav's patch) because people were already using it with the SGS3 Easy UMS app and the rest is set in TWRP's init.rc anyway (except only the ADB interface is enabled initially). There's no setprop (as far as I can tell) so init.rc's ability to run commands based on properties changing can't be used, but the USB interface can be disabled and the mode changed anyway with writing to those files to enable USB MSC as well as ADB when desired at any time (well, when it's sensible to do so).
[Galaxy S III Original Android Development] Glebun:
Oh, interesting. So why don't other recoveries have this issue?
[Galaxy S III Original Android Development] Dees_Troy:
TWRP is a dynamically linked recovery with the libraries separate from the binaries. It allows us to run touchscreen binaries from ROMs within the recovery on devices that need that functionality, might save us some space, and may also be part of the reason that we'll be able to decrypt Samsung encryption (decryption depends on using some Samsung proprietary libs). The earlier versions of VRTheme used a dynamically compiled zipalign binary that was linking against /system but because of the way we have the TWRP environment set up, we don't allow linking to /system (if the TWRP recovery binary ends up linking to /system then you can't unmount system to format it).
[Galaxy S III Original Android Development] Glebun:
thanks for the detailed answer
[Galaxy S III Original Android Development] Perka:
Thx :)
[Galaxy S III Original Android Development] Idan73:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Just recently realised that note2 (lte european and North American version at least) twrp has (for few versions already) full ex_fat support. 2.3.1.3 I think.

Any chance we might have that as well?

Apologise if this has been answered recently. I couldn't find any other reference except first page and thought nothing of it till I saw that another twrp actually already supports it.

JKAY DELUXE [I9300 JB 4.1.2]
[Galaxy S III Original Android Development] RoWeKo:
I had a 16 GB ext SD in my GS3. I saved all content to my PC. I formatted a brand new 32 GB ext SD with FAT32 and copied everything back on this (new) card. The phone recognizes it and everything on the phone works as before.

BUT: I tried to do a nandroid backup with TWRP (newest version) but it can't mount my ext SD. Tapping on "use external SD" doesn't work.

Any hints?
[Galaxy S III Original Android Development] corrsea:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Have to tried formatting it on the phone from settings?

ROM Sotmax Ultimate V14

Kernel Yank555.lu-V3.1c
[Galaxy S III Original Android Development] RoWeKo:
That did it obviously. But why? Is formatting IN the phone sth different from formatting on a PC? Strange
[Galaxy S III Original Android Development] corrsea:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

It may well be different or it may be that windows does just not do it very well. With previous phones I always used Panasonic's sd formatting tool for that very reason.

ROM Sotmax Ultimate V14

Kernel Yank555.lu-V3.1c
[Galaxy S III Original Android Development] RoWeKo:
That's why I formatted it under Linux ;)
[Galaxy S III Original Android Development] ralphkaz:
When updating via GooManager on my SGS3 I'm getting version 2.3.3.0 instead of 2.3.3.1 - any suggestions?
[Galaxy S III Original Android Development] BrandoHD:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

Get the latest version a few posts back

That's where I got it
[Galaxy S III Original Android Development] papisky226:
somebody please help me!

guys im sort of new to this. i rooted my nexus 7 a couple of minutes ago had the twrp recovery working it was all fine until i tried to flash cwm recovery. all i did was flash, im guessing that was the wrong way to do it. i rebooted into recovery and twrp is now asking me for a password to decrypt my storage i wiped everything off the nexus 7. and now i do not know what to do i cant flash anything i cannot mount. idk what to do. never did i put a password. someone please help me

---------- Post added at 11:43 PM ---------- Previous post was at 11:33 PM ----------

I wiped everything on the tablet and now it does not ask me for a password but i cannot mount to my computer. i cannot flash a rom to boot into. idk what to do anymore im stuck and cannot do anything. nothing works.
[Galaxy S III Original Android Development] jeebspawnshop:
You'll probably have better luck resolving your issues in the Nexus 7 forums...
[Galaxy S III Original Android Development] papisky226:
please help...

Are you sure? the only reason i wrote it here is because it was the recovery image that was acting up and because of it this all happened. what do you recommend being the best forum for this type of problem ? there are so many. sorry im new to this. thank a lot by the way.
[Galaxy S III Original Android Development] Dees_Troy:
USB storage won't ever work on the Nexus 7:

http://teamw.in/DataMedia

You can use adb push to push a file to it or adb sideload if you prefer. You can also download the fastboot flashable images from Google to return it to stock. USB storage mode is going away so start getting used to adb.
[Galaxy S III Original Android Development] Yank555:
Any chance seeing it on the S3 anytime soon ? It's really a breeze to have access to the external SD this way...

JP.

PS: As I said already, if there is kernel-wise work to do, I'm glad to help where I can. And as I in the meantime have found out, the recovery kernel is a regular kernel, Philz's is using the XXELLA zImage, and it work on that one.

---------- Post added at 05:41 PM ---------- Previous post was at 05:06 PM ----------

OK, so I just took a minute to dig into this ;)

Here's what I did (on stock TWRP 2.3.3.1) :

Based on info in this post by qwerty12 (thanx !) I created the follwing file :

/data/ums.sh :

umount /external_sd
echo 0 > /sys/class/android_usb/android0/enable
echo /dev/block/mmcblk1 > /sys/devices/platform/s3c-usbgadget/gadget/lun0/file
echo 685e > /sys/class/android_usb/android0/idProduct
echo mass_storage,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable

The I chmod'ed it to make it executable :

chmod 744 /data/ums.sh

Then I open an adb shell and typed this :

/data/ums.sh &

And I hit enter, adb shell connection was (obviously) lost (hence the "&") and a few seconds later, I see my external sdcard as mass storage on my Windows PC ! And abd still working.

JP.
[Galaxy S III Original Android Development] Yank555:
Ok, based on this info I quickly made flashable zip that copies two files to "/system/xbin" to add (quick & dirty) support for UMS from TWRP recovery, but it's not the tap to enable kind of thing.

The files added are :

/system/xbin/ums-on.sh

/system/xbin/ums-off.sh

Once you are in TWRP, you need to do the following :

To enable UMS :

tap "Mount"

mount system (if it is not already mounted)

tap "Home" (to get back to main menu)

tap "Advanced"

tap "Terminal command"

go to "/system/xbin"

tap "select" (bottom right)

type "ums-on.sh" and hit "go"

I advise to stay in there (Terminal Command) as long as you use the SD card via UMS.

When you're done :

To disable UMS :

eject the mass storage in Windows (safer !)

type "ums-off.sh" and hit "go"

tap "Home" (to get back to main menu)

JP.

PS: A flashable zip that adds both scripts is attached, as well as a remover.

PPS: I know this is far from a good solution, it's a quick & dirty hack, but this will save me a lot of time when testing. I'll just keep the two flashables on my SD, in need the scripts will be quickly flashed and give me access to the SD without having to remove it from the phone.
[Galaxy S III Original Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

It was already going to be fixed in our 2.4 release that is expected for Tuesday.
[Galaxy S III Original Android Development] Yank555:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

That will make TWRP the

perfect

recovery :D

JP.

Sent from my custom Sotmax V13 / Yank555.lu SGS3 U7 kernel v3.1d Aroma (Linux 3.0.60) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] JDogg1329:
Absolutely agree, it's the one missing feature. Glad to hear it's coming.
[Galaxy S III Original Android Development] galza:
superb tool

my wishful thinking is for the next version to install/wipe\backup a 2nd rom because i use 2 roms.after that it will be perfect in the meantime im using well ofcourse stweaks.

:fingers-crossed:
[Galaxy S III Original Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.3.3.1 touch recovery [2012-01-17]

This would be very specific to each device & out of the scope of TWRP.
[Galaxy S III Original Android Development] ArbiterGR:
Whoa, thanks!! Time to convert my fat32 32gb card back to exfat :)
[Galaxy S III Original Android Development] Safe0716:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Installed 2.4.0.0 (come from siyah) and it only shows folders, not zips etc... Same for internal and external storage why? :(
[Galaxy S III Original Android Development] Perka:
Works fine here, but I dont have ext sd.
[Galaxy S III Original Android Development] qtwrk:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Just wanna make myself comfortable, I assume it contains SDS fix , right?
[Galaxy S III Original Android Development] silverrum:
which is the correct twrp version to download from goo, l see there quite a few..
[Galaxy S III Original Android Development] MIKEMON:
Thank Dees_Troy is a favorite recowery, SDS safe?

thanks for the info: Good:: Angel:
[Galaxy S III Original Android Development] Dees_Troy:
Yep
[Galaxy S III Original Android Development] Idan73:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

#0N565120KC056904R

Here's a few beers for the project and much thanks for ex_fat support.

JKAY DELUXE [I9300 JB 4.1.2]
[Galaxy S III Original Android Development] qtwrk:
possibly BUG

this was what i did:

backup SYSTEM , DATA, BOOT and EFS .

and then go to "reboot" "power off" , but phone didn't go off, just reboot into recovery again , i tried several times, still same.

XXELLA bootloader i think , TWRP 2.4.0.0 , Siyah kernel , Deodex stock XXEMA2 ROM.
[Galaxy S III Original Android Development] Perka:
Works as it should for me.

Stock Insecure Kernel, MA2 FW, 2.4.0.0 TWRP
[Galaxy S III Original Android Development] qtwrk:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

:p

Why ever time I encounter something wrong with me, you just show up ;)
[Galaxy S III Original Android Development] Perka:
I had some spare time today :p

Can you try with stock kernel?
[Galaxy S III Original Android Development] Koetermann:
AW: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Same issue like in version 2.2.3.0 for me. No detection for my ext. SD (Fat32 formatted) :confused:

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] Dees_Troy:
Boot TWRP, via ADB shell run these commands and paste the output:

ls /dev/block

blkid
[Galaxy S III Original Android Development] Striatum_bdr:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Please next time make a text file attached to the post... as a courtesy for poor phone users.
[Galaxy S III Original Android Development] ratatattata:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

I can't seem to able to install any .zips. Recovery won't find any .zip files in the map I store stuff in. In file explorer on device, that is sdcard0/Download, and in TWRP it's just sdcard/Download. Most, if not all, .zips has been changed name, but cwm finds all.

Any idea what the issue might be? I believe this only happened in 2.4.0.0.

EDIT: .zips show up in external sd card and installs from there. Still nothing in internal storage, though.
[Galaxy S III Original Android Development] JDogg1329:
Now that we can mount the external SD is there any way to mount the internal storage?
[Galaxy S III Original Android Development] Sepp0rl:
Re: [RECOVERY] TWRP 2.4.0.0 touch recovery [2013-01-29]

Well I can't see any zip files as well.tried given adb commands but still without any proper outcome. Had to move back to official touch clockwork....
[Galaxy S III Original Android Development] Dees_Troy:
blkid usually detects vfat for sdcards that are formatted to FAT32, but for some reason it's not picking that up for your sdcard. I'll have to work on improving the fail-over between exFAT and FAT32 to work around this issue. Part of the problem is that exFAT doesn't have an ID yet that can be used for blkid detection, so we kind of have to just try it.

Added this to our issues log here:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/92
[Galaxy S III Original Android Development] thecoby:
Hi guys, I made TWRP Holo Light / Dark theme, so you can try if you want it.

Here is link to thread: [THEME] TWRP Holo Theme - Light / Dark (Updated 10.01.13.)
[Galaxy S III Original Android Development] postall:
If anyone needs zips file
[Galaxy S III Original Android Development] Koetermann:
AW: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Thanks for the fast reaction. The issue is now (2.4.1.0) fixed. My FAT32 formatted ext. SDcard is now detected.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] sharingan92:
@Dees_Troy

is it possible to get tablet look on our phone that would be sweet :P
[Galaxy S III Original Android Development] MIKEMON:
THX

For me everything is fine, just missing flash VrtThéme and will be great, probably the best ..: Good:: Prsty-palce:
[Galaxy S III Original Android Development] Dees_Troy:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

No rotation in the recovery graphics engine.

http://teamw.in/VRThemes

Usually theme makers just have to update one file in the zip to make it work with TWRP. It would take less than 5 minutes.
[Galaxy S III Original Android Development] Theshawty:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

This recovery is awesome ^^
[Galaxy S III Original Android Development] Glebun:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Vertumus, creator of the Domination theme, is asking me for the latest vrtheme that has no issues with TWRP. Does he only need to include the updated zipalign from OP?
[Galaxy S III Original Android Development] acerdroid:
Hi guys I just need some info. When I go into recovery to wipe thers an option to wipe system I think it's the one that gives the triangle and says its not necessary to wipe if you do ull lose backups and all that stuff. If I use that option will I still be able able to flash a ROM. Sorry if this is a stupid question but reason I'm asking is I have a 32g internal memory but only shows total space 24 gig I'm using Samsung galaxy note 2 with omega rom
[Galaxy S III Original Android Development] bedtime_with_the_bear:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

If you're hoping to get more usable internal storage, then I'm afraid it's not going to happen.

That 32GB is the total space in the phone, including recovery, boot, preload, system, and user space. You cannot change it by formatting it. While it is technically possible to change, neither Samsung, nor a custom ROM maker will support it as the long term impact will be unknown.
[Galaxy S III Original Android Development] acerdroid:
Thanks for the replay. So where is the twrp recovery stored I don't want to remove it by formatting wrong partition
[Galaxy S III Original Android Development] bedtime_with_the_bear:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

It's stored in its own partition that is not written from the recovery so you shouldn't need to worry about overwriting it.

I've moved back to CWM since Koush implemented external SD and decent batch flashing support, but I don't believe there is any way to overwrite recovery from TWRP.

By all means, ask Dees_Troy for confirmation, but I'm pretty sure I'm right.
[Galaxy S III Original Android Development] acerdroid:
Thanks a million
[Galaxy S III Original Android Development] rexboy:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

Yes. Well whenever I flash a new theme or any zip for a modification like a system ui flash I just change the zip align in the vr themes folder and that's it :)

Sent from my SG3
[Galaxy S III Original Android Development] Glebun:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

I know, but I assumed "the new vrtheme" would mean more than a different zipalign
[Galaxy S III Original Android Development] da.trute:
There is discussion but not confirmation, can you do recovery backup and restore to exfatformatted SD card, you cant with CMR, this would be a good reason to swap to this version.

You could do with a list of features / advantages on the first page.
[Galaxy S III Original Android Development] jwchips:
Failed Script Asserts

Hi Guys,

I've got a recurring issue with flashing MIUI on my i9300 from miuiandroid.com. They use script asserts to ensure users flash the correct zip for their device. The problem is it doesn't work for me! I've verified that their assert script is ok, and my build.prop details also match what the assert is looking for, but I get an 'assert fail' error when flashing. I'm having to manually remove the assert script from the updater-script each week, which is a PITA. MIUI are blaming the recovery, can anyone shed some light on the issue? Is there an issue with script asserts in TWRP, is the function even supported and is there a way to disable it?

The problematic code:

assert(getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0" || getprop("ro.product.device") == "galaxys3" || getprop("ro.build.product") == "galaxys3" || getprop("ro.product.device") == "GT-I9300" || getprop("ro.build.product") == "GT-I9300");

My ro.product device = m0

My ro.build.product = m0

You can see the post I've made to the ROM devs here, that post also has the updater-script and my build.prop attached.

Thanks in advance for taking the time to answer my question, hopefully I can learn some more along the way :)

[edit] I've done some research and remembered that I also have a default.prop located in / and another default.prop in /system. Typing getprop in terminal in rom displays build.prop properties but when I try to call getprop in twrp terminal i get a command not found error.

So which prop file is the getprop command looking at? I would like to learn as well as find a solution to my issue [/edit]
[Galaxy S III Original Android Development] ScottIsMyName:
Date and time seems to be completely off. I think this has existed since the beginning. Is there any chance it will fixed?

Autonaming the backup based on the date leads to confusion since they are way off.
[Galaxy S III Original Android Development] beardymarrow:
Re: [RECOVERY] TWRP 2.4.1.0 touch recovery [2013-02-01]

You just need to set the timezone.

There are only 10 types of people in the world. Those who understand binary, and those who don't.