yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] fonfox:
Flashed boeffla kernel with new 3.0.0-1 cant see difference in speed to v3.0.0-0 thats works great.

But only flash kernel will See next time
[Galaxy S III Original Android Development] SdtBarbarossa:
can someone provide me a log of this "slow flashing" ?
[Galaxy S III Original Android Development] :
That's right. First (yellow) release is good but 3.0.0-1 is very slow. I don't know why
[Galaxy S III Original Android Development] Kippy51:
Yea, Black Focus is talking about the 3.0.0.1 version.

Sorry: 3.0.0-1 (new numbering ...)
[Galaxy S III Original Android Development] H4RTI3:
Thanks for the new build, the blue color looks great:)

I flashed some updates (boeffla, xposed, SuperSU) and everything was normal and fast except for SuperSU which was very slow.

Maybe it has sth to do with RD compression method in SuperSU.
[Galaxy S III Original Android Development] :
Ok it seems to be only with supersu Yes. With 3.0.0-0 everything was ok
[Galaxy S III Original Android Development] Scorpionea:
Oh good then, was about to flash new update but I think will stay on first release until slow flashing is resolved [emoji2]
[Galaxy S III Original Android Development] SdtBarbarossa:
thanks for the hind... do you know wich exact compression it uses?
[Galaxy S III Original Android Development] H4RTI3:
[MENTION=6248658]SdtBarbarossa[/MENTION] Seems to be gzip

But Chainfire says he's working on it to support other RD compressions.
[Galaxy S III Original Android Development] SdtBarbarossa:
yea i have lzma... that should be the reason
[Galaxy S III Original Android Development] GrayJack:
Is me the only who cannot find any mention about f2fs in 3.0.0-1 anymore?

Отправлено с моего SM-P605 через Tapatalk
[Galaxy S III Original Android Development] SdtBarbarossa:
yep f2fs is offline atm due to new kernel.... i need to reimplement it completely... i just wanted to make all twrp3.0 bringups complete before doing this.... so if im done with taoshan and mint then i come back to i9300/5 and reimplement f2fs ... this will only be possible when official cm also implements f2fs because twrp server does directly upstreaming the kernel from there (only with my kernelconfig)

btw f2fs partitions can also not be mounted in 3.0 !
[Galaxy S III Original Android Development] :
Flashing GApps (open GApps pico) takes a very long time, too with 3.0.0-1
[Galaxy S III Original Android Development] X301:
Hi there. Congratulations for 3.0.0-x release

Well first impressions are positive, TWRP looks much, much, much better comparing to 2.8.7.3

on 3.0.0-x Things like Poweroff actually poweroff device and at pressing power button it boots the device into CM13 unlike 2.8.7.3 it went into TWRP, so those are the good news.

The bad news... Sorry there's a few but they are bad.

Performance wise 3.0.0-1 is probably 2x slower flashing cm-13.0-20160209-NIGHTLY-i9300.zip on the S3 intl comparing to 2.8.7.3

Flashing open_gapps-arm-6.0-nano-20160208.zip package is 20x to 30x slower maybe even slower, this took nearly 10 minutes just for Gapps nano process from start to finish.

TWRP even though Im sure I flashed 3.0.0-1 it still says 3.0.0-0 just like previously in 2.8.7.3 it ignored the 3, rather pointless also even if its just cosmetic it makes ppl wonder if something is wrong imo.

The S3 gets HOT not in a good way

So not sure whats going on really but there you are
[Galaxy S III Original Android Development] SdtBarbarossa:
thank you for the bugreport :)

the slow flashing is not really device related... almost all smdk4x12 devices got it and some more samsungs....

the hotness can be related due to long flash... set the brightness to minimum will help
[Galaxy S III Original Android Development] X301:
Thanks for reply, I take it these are known and fixable? Instead of asking when its going to be fixed ;) I'll probably revert back to the previous version temporarily and await the patching of those issues with great anticipation.

Great work though, keep it up.
[Galaxy S III Original Android Development] X301:
Another issue (albeit cosmetic) is while flashing the cm-13.0-201602xx-NIGHTLY-i9300.zip the process hasn't completed but the progress bar completed prematurely at Patching system image unconditionally has finished.

The progress bar should complete at around Script succeeded: result was [0:200000] so this means 4 steps earlier then TWRP 2.8.7.3

edit

There is no progress increment started when the verification progress starts/ends, the animation of the progress bar is alive but theres no progress increment marked at all, so I guess the verification at beginning or end isnt accounted as progress at all, in 2.8.7.3 everything was accounted.
[Galaxy S III Original Android Development] Scorpionea:
Just a reminder for all who flashes new TWRP 3.0

Dont flash new 3.0.0.1 (blue theme) as it has issues since it's based on new sources

Flash first release of 3.0.0.0 (Yellow theme) and u will not have any issues
[Galaxy S III Original Android Development] X301:
Is there a difference in source in between 3.0.0-0 and 3.0.0-1 except for the theme?
[Galaxy S III Original Android Development] SdtBarbarossa:
in source? yes a lot....
[Galaxy S III Original Android Development] X301:
Well if the CM13 nightly for today gets built Ill test TWRP 3.0.0-0 to see and report back.... they should really add changelogs for these things a lot to me, means nothing ;)
[Galaxy S III Original Android Development] SdtBarbarossa:
these changes a lot are in source only... yee gerrit for detailed changes ( if you can read source )
[Galaxy S III Original Android Development] 2phazt:
What issues?
[Galaxy S III Original Android Development] jukyO:
Eg

Took me 10 mins to finish flashing SuperSu.
[Galaxy S III Original Android Development] rp158:
Cannot confirm low speed: flashes, backups, restores aren't slower than in 2.7 or 3.0 yellow here.
[Galaxy S III Original Android Development] X301:
I suppose this one http://xdaforums.com/showpost.php?p=65246668&postcount=1354 though Ive not had a chance to test

---------- Post added at 17:05 ---------- Previous post was at 17:04 ----------

Then you arent flashing Gapps, it takes forever and a day to flash Gapps nano for instance. somthing like 30 times longer.
[Galaxy S III Original Android Development] rp158:
Right. I'm happy without such crap since months :)
[Galaxy S III Original Android Development] X301:
If you dont need Google play thats fine but yes things are slow indeed on even the smallest Gapps package.

Im not sure however if using v 3.0.0-0 over 3.0.0-1 is ideal either, without seeing changelogs or actual code changes, its hard to know what important fixes went in to TWRP and how it may affect the end result of the flash.

Its bad enough Cm13 is on nightlies, I for one dont want some bug arising from issues while flashing (if its even possible with the 3.0.0-0 TWRP)
[Galaxy S III Original Android Development] SdtBarbarossa:
TWRP3.0.0-0 should not lead to flashing errors.... also 3.0.0-1 also shouldnt lead to errors.... we have investigated more and the results are the same... even if 3.0.0-1 needs more time to flash.... the main-error hinds within android 6.0 code (all affected recoverys can be fixed while building under 5.1 ) so we need to find out what exactly its causing it...

also like i said before if you want to see the changes look at github... its all opensourced
[Galaxy S III Original Android Development] yoahmad1995:
Installing latest opengapps file with twrp 3.0.0-1 is taking forever. Anyone can confirm this?
[Galaxy S III Original Android Development] :
Yes
[Galaxy S III Original Android Development] Scorpionea:
Revert back to 3.0.0.0 build and you will not have issues anymore [emoji6]
[Galaxy S III Original Android Development] X301:
I know the code is at Github, but none of the changes at https://github.com/TeamWin/android_device_samsung_i9300/commits/cm-13.0 you can exactly tell which belong to 3.0.0-0 or 3.0.0-1, If I had to guess (and thats just a guess) is that initial commit at 5th Feb was 3.0.0-0 and the two commits at 8th Feb was 3.0.0-1

Thats what I said, idk how you infer from that flashing errors, I was merely asking/wondering if the end result may be better or worst with one or the other or if it doesnt matter. Iif the changes between the two would affect that stability (not errors) to the be worst or better due to the differences between sourcecode changes from -0 or -1.

Other users claiming thers less issues with 3.0.0-0 due to yellow theme just confuses this even more for regular folk who dont understand or read sourcecode.

IM indeed a fan of TWRP and your work so looking forward to slightly more mature release and fully understand the hickups (I read the news https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html) so good luck. :good:
[Galaxy S III Original Android Development] achkap:
I backed up my rom and I changed the name before starting but when it finished the name was the default. I am on 3.0.0-0. It's a bug?
[Galaxy S III Original Android Development] SdtBarbarossa:
well good Point! all 3 commits are from 3.0.0-1 ... i forgott that i made a complete bringup.... so well you cant read all changes.... but we are SURE that the change causing it is in smdk4x12-common repo

quick changelog:

- fixed the color issue (inverted color)

- some stuff in kernel configuration (because of lzma )

- a new custombootimg.mk

thats it... im searching actually in smdk4x12 repo to find the issue
[Galaxy S III Original Android Development] X301:
Thank you ;).

There was a rather large f2fs drop tonight merged into android_kernel_samsung_smdk4412 not the common stuff where you say the issue is, I wonder if that will have any bearing on the flash slowness. but that would need a rebuilt TWRP to find out no? idk how it works or if it matters but I was wondering about https://github.com/CyanogenMod/andr...mmit/aa8ad5b19ec0e09a1238b537fbf49b59d8770cfd specifically. (reading the commit message)

Also were you able to reproduce the progress bar being out of sync with the actual progress issue?

Good luck, I wish I could help fix these things, but alas this is mostly "Jeberishanese" to me ;)
[Galaxy S III Original Android Development] Sigi_cz:
While charging the phone with TWRP 3.0.0-0, if the system crashes (CM13 in my case), it doesn't start up again. Instead battery graphics is shown for while. I have to disconnect usb cable, and start system with power button.

With TWRP 2.8.7.3 if the system crashes while charging, it starts again by itself. (expected behaviour for me)
[Galaxy S III Original Android Development] 2phazt:
I don't think this i recovery related - seems more to be a kernel thing.
[Galaxy S III Original Android Development] Sigi_cz:
recovery is the only thing I changed.

kernell is Boeffla 5.0 beta6
[Galaxy S III Original Android Development] X301:
That kernel what rom have you got? if its cm then thats not the right kernel.

Im on CM13 nightly and twrp 3.0.0-1 and it doesnt crash while charging at all.
[Galaxy S III Original Android Development] Sigi_cz:
I'm not saying it crashes because of TWRP. But when it does while charging, with older TWRP system starts up again and with 3.0.0-0 it just shows me charging status.

CM13 20160104, Boeffla 5.0 beta6
[Galaxy S III Original Android Development] 2phazt:
Update rom and kernel and check if it is still the case.
[Galaxy S III Original Android Development] brettmurf:
Used TWRP manager to update to 3.0.0.1, booted to recovery and it showed 3.0.0.0 I had been on a REALLY old version, so I think it is just a version number issue and not showing the .1 at the end.
[Galaxy S III Original Android Development] Kippy51:
When your theme is yellow/orange it's 3.0.0-0. If it's blue/gray it's 3.0.0-1 (AFAIK).
[Galaxy S III Original Android Development] X301:
In an Ideal word yes, but not Where TWRP is concerned. See below.

I also reported that earlier, that though seems to be a trademark of TWRP apparently, 2.8.7.3 also displayed 2.8.7.0, which defeats the purpose and confuses ppl who dont know any better.

The filenames get a version bump but the internals apparently dont.

Would be nice now that TWRP has a new versioning scheme0 that some attention to detail would be exacted. hint hint ;)

Really O think the issue is that TWRP itself code stays the same, while the device specific code changes

For e.g. https://github.com/TeamWin/Team-Win-Recovery-Project/commit/b7e8b98ce6641ec5b6a10e91277f3b045e981508 is where TWRP marks version, that whole source code is for TWRP only.

For me my device is GT-I9300 and the source is on a different project altogether https://github.com/TeamWin/android_device_samsung_i9300 which that has no versioning control whatsoever.

Silly really, but that explains why the device source can change and twrp itself doesnt have to. IMO you should have TWRP version/Device version in independent strings in respective repositories.
[Galaxy S III Original Android Development] vijer:
Team Win Sleeping?

GooManager doesn't seem to work and neither does the Odin install. Has Team Wind been sleeping?:p

---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------

Did you just zip the TWRP 2.3.1 file from Team Win's site?
[Galaxy S III Original Android Development] JJEgan:
Goo manager works and downloads correct verion .

Possible you need to update GM ???

jje
[Galaxy S III Original Android Development] Perka:
this works for me in odin

https://dl.dropbox.com/u/18787285/roms_etc/TWRP.i9300.2.3.1.0.tar
[Galaxy S III Original Android Development] Oldpapa49:
I have update to TRWP 2.3.1.0 and tried a nano recovery of CM10. It actually erased or made webos non boot-able.

Comes up with a triangle and a ! in the center..

I have tried this 3 times... every time it need to do webosdoctor..

Is there away to go back to 2.2.2.1 or the last of the 2.2 series..

I see this after is say restore folder.Restoring 3 partitions...

Formatting System using make_ext4fs...

Done. Restoring System...

etc..

Is it formatting the wrong area?
[Galaxy S III Original Android Development] czar22:
what to do ?

i flash a -MOD- [like one this http://xdaforums.com/showthread.php?t=1995320 ]

and nothing flash after flash

what to do

thx
[Galaxy S III Original Android Development] kasperok:
..taken from link you posted above:

READ CAREFULLY!

● Download and flash via CWM Recovery. Don't forget to make a backup (at least SystemUI.apk if using deodexed rom or SystemUI.apk and SystemUI.odex if using odexed)!

● if you're TWRP user - http://teamw.in/VRThemes Thanks to prdog1 for his finding!

You have to fix zipalign binary in mod archive to use it with TWRP.

Bye
[Galaxy S III Original Android Development] czar22:
thx
[Galaxy S III Original Android Development] cammel:
I can see on the website that there is a new 2.3.2.0 update of TWRP, but if I choose the I9300 still is on the 2.3.1.0 version.. Isn't the update available for the S3 yet?

Thanks!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Dees_Troy:
Most of our recent changes only affect devices that have 4.2, which, so far is pretty much just the Nexus phones. We'll move to update all the rest of the devices soon.
[Galaxy S III Original Android Development] cammel:
Awesome!! thanks!

This will be my first time using this recovery, I'm used to wipe data, cache, dalvik and then format system, data and cache (under mounts and storage) before changing the rom on my phone when using cwm recovery, the thing is that I saw on TWRP that there is no format system under mounts option.. How can I do this when using TWRP? Which are the recommended wipes when flashing a new rom with this recovery?

Thanks a lot in advance for the help!

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] nazfalas:
There is the possibility to format system under "Wipe". For flashing a new ROM I'd recommend using "Factory reset" which you can find under wipe, as well (wipes data, dalvik cache and cache).

Usually ROMs wipe system anyways when installing through recovery so it's not actually necessary.
[Galaxy S III Original Android Development] fidorulz:
Do we know if this will ever be changed to be done automatically?
[Galaxy S III Original Android Development] rexboy:
True is the only niggling thing about this recovery otherwise it's great.

Yeah you can change the zip align via a pc our or phone which I do but it would be much easier if this could already accommodate it.

Sent from my SG3
[Galaxy S III Original Android Development] d8389:
probably not recovery, but GooManager problem:

Can't use external SD to select file for flash.

Some functionality of CWM Manager still missing.

Backup/Delete Backup/Flash zip start from Android (not from recovery) and reboot after operation complete. Without user action (user sleeping, device backing up, but alarm clock at morning must work)

One more minor thing:

Using ansicon but still

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell

~ # ^[[5;5Rexit

And one more:

can you add .nomedia file into backup directory automatically ?

exit
[Galaxy S III Original Android Development] iarapilot:
Very good recovery app....Thanks! 1.77GB backup on Criskelo ICS in 230 sec.
[Galaxy S III Original Android Development] hazri1974:
Why no more update for this great recovery on our device?...Note2 now TWRP 2.3.2.3......ours still v.2.3.1.0
[Galaxy S III Original Android Development] Codekrypt:
There are no problems in the current version so I don't see any rush. Please be patient. Dees Troy mentioned updates to other devices will come soon.

Sent from my GT-I9300
[Galaxy S III Original Android Development] sharingan92:
Hope update comes soon as paranoid android 2.99 will require the latest TWRP when its released as its the only recovery confirmed to install PA properly due to andtoid 4.2 support

im what Willis was talking about
[Galaxy S III Original Android Development] Kung-Fu-Tse:
on homepage I read this and when will it comes???

What's new in 2.3.

2

.0:

- Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)

- Fixed a bug with deleting a backup with a space in the name

- Added highlights on keyboard key presses

EDIT:

or TWRP 2.3.2.3 touch recovery ?

I use Samsung Rom Android Based on XXELK4 Android 4.1.2 (Date: 08/11/2012)
[Galaxy S III Original Android Development] deepphrozen:
Great recovery, i love it.

Good job guys.
[Galaxy S III Original Android Development] X301:
Personally I dont see that as an issue even though you do. An issue for me is for e.g. on previous TWRP you use to press power off *(from within TWRP) and at any stage after from total OFF if you pressed the power button, it booted into TWRP, to me that made no sense as it should not do that, now it behaves as expected and boots system as normal.
[Galaxy S III Original Android Development] ThePzyDuck:
I was on TWRP 2.8.7.3 and flashed TWRP 3.0.0.1 till that all good, i clean flashed a rom, and when i re enter recovery to flash a zip, TWRP is still showing new desing, but it says version 2.7.8.0 ... dafak? haha someone else with this bug? its a title bug or im really on 2.7.8.0 with new design lol
[Galaxy S III Original Android Development] Kippy51:
I'm on 3.0.0-0 (the yellow one) and I just checked, but both on the splash screen and in the title bar it says '3.0.0-0'.

Maybe you have to re-flash?
[Galaxy S III Original Android Development] ThePzyDuck:
Hmm its strange, its the new interface but in the title bar it says 2.7.8.0.. how could be that possible? i mean i HAVE the new interface and the recovery works just fine
[Galaxy S III Original Android Development] negativman:
Ever going to solve the problem of a very slow install, a firmware update?
[Galaxy S III Original Android Development] rp158:
[MENTION=2760849]negativman[/MENTION]: ever realizing, that it's totally negative, man, to demand this? Use 2.8.7 in the meantime.
[Galaxy S III Original Android Development] negativman:
I don't require, I ask! If there is nothing to respond, don't respond generally better!
[Galaxy S III Original Android Development] galen2:
Before to ask you could read, developer said a few post ago that he its triying to solve it.
[Galaxy S III Original Android Development] negativman:
I badly know English language. I find it difficult to follow the message in the subject! Thanks for the info!
[Galaxy S III Original Android Development] rpdroky:
1'st: Please note that the developers are doing this in theyr FREE TIME! so stop being rude with stuff like "when they will fix it" , use a older version or help them out if you think that yre smart enough , if not at least wait paciently til the fix will come :)

2'nd: The device is old already and you shoul'd be greatful that they keep mantaining it in the little time they have , as you already know i9300 development is kinda EndOfLife

ALL THE RESPECT FOR TWRP TEAM!

Cheers :highfive:
[Galaxy S III Original Android Development] SdtBarbarossa:
as i cant find the issue (and im bussy with XT cm13 bringup) the master Dees_Troy himself(herself?) will have a look soon :) so lets hope the fix will be found ^^
[Galaxy S III Original Android Development] rpdroky:
Take all the time you need guyz , TWRP 3.0.0-0 is stabe enough :)

Cheers :highfive:
[Galaxy S III Original Android Development] X301:
One explanation is youre not using the official TWRP but some 3rd party one which is 2.8.7.0 based with the same theme.

Another explanation is you did some odd flash or something that dindt overwrite the complete recovery.

You claim that it works properly, but that is based on what? You fully tested all functions without fail?

From my end and understanding the spirit of Opensource all I can say is, Thumbsup.

Awaiting fix with great anticipation. :)

See http://xdaforums.com/showpost.php?p=65365787&postcount=1382 (my understanding of versioning as is)

[MENTION=6248658]SdtBarbarossa[/MENTION] Do you have any idea if the device specific version bumps can actually be reflected on the TWRP version that we see onscreen?
[Galaxy S III Original Android Development] SdtBarbarossa:
1. so the issue seems to be with busybox ( thx [MENTION=1162986]Captain_Throwback[/MENTION] who got it on another device ) so we will have a "fixed" version soon

2. well in unofficial builds you can easyly change it in portrait.xml .... but in official builds that file comes from android_bootable_recovery ... and therefor we cant change it device-specific... so no way atm ;-(

so now you could say "hey lets get a boardconfig flag for version controll" but then we would need to change it all day long with commits (thats really not a way to do it )
[Galaxy S III Original Android Development] X301:
Good news indeed ;)

Many softwares use a git hash these days for version (via git describe) so TWRP could be 3.0.X and the device would be a hash of latest commit + device ID (3.0.0-fe3fgj5a-I9300)

Easier said then done in any case you have no device specific version control (aside from the filename changes only) hence the version shown is only from twrp not device. If I knew how to implement that it would be done.
[Galaxy S III Original Android Development] ZjemCiKolege:
Maybe you can add f2fs format option? 3.0.0-1 only probably removed ;-;
[Galaxy S III Original Android Development] X301:
[MENTION=5429359]ZjemCiKolege[/MENTION]

I would imagine that TWRP has to be built with F2FS support

Im not sure if this is related (seems to) http://review.cyanogenmod.org/#/c/132978/

maybe someone who knows more can clarify this point in a more informed manner than my wild guess.
[Galaxy S III Original Android Development] SdtBarbarossa:
no this one has nothing to do with it! i removed it because of a different kernel that did not support it.... but f2fs support is back so i will include it in next update