yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Mike9966:
No, thanks. I will use TWRP-3.1.0 from other developer that works correctly and faster...

I hope that you can fix problems in yours recovery.
[ONE Android Development] keen36:
What problems? Ext4 formatting is apparently fixed now, was there something else?

Edit:

I think i will just install and see for myself
[ONE Android Development] Mark5:
Hi Daniel, am using either 3032 or 3103 and though aroma runs, the debug overlay appears over the top of the aroma screen which makes it awkward to use. Both versions have this error. I am not using any themes in TWRP and I have deleted the .twrps file to test.

BTW I am using the team blackout aroma file for theme ready gapps so I can use the domination substratum theme, in case you want to test.

Thanks again...
[ONE Android Development] danieldmm:
Tested with open gapps aroma zip file, the debug overlay does not go on top of the aroma screen. Will try to test over the weekend the one you talk and see if could be the team black aroma engine different from open gapps.
[ONE Android Development] Magnum_Enforcer:
Thread cleaned.

Remember, this is a development thread. Treat it as such, and follow the forum rules.

Consider yourselves warned.

Cheers,

Magnum_Enforcer

FSM
[ONE Android Development] danieldmm:
TWRP 3.1.0-4-TugaPower

Fixed slow formating

Fixed encryption

https://www.androidfilehost.com/?fid=457095661767146241

MD5: 4e94a26287480b6e21153e1f975fec1d
[ONE Android Development] Mark5:
Thanks Daniel...

Does this also fix the aroma issue on the team blackout zip, do you know?

Cheers
[ONE Android Development] danieldmm:
Can you post the link? Will need to test and compare something with the open gapps aroma since with open gapps aroma it's all fine.
[ONE Android Development] Mark5:
I believe it is this one:

http://teamblackedout.com/Gapps/GoogleApps-ThemeReady-LP-MM-N-v31.0-Aroma.zip

Cheers
[ONE Android Development] ashwin.kj:
Wanted to let anyone interested know that this one is able to successfully decrypt data partition if you are encrypted.

Thank Daniel
[ONE Android Development] danieldmm:
Aroma gapps seems to use aroma engine 2.70 RC2 , team black uses 3.00 b1 , try to talk to team black to make a build test based on 2.70 RC2 aroma engine to see if work like it should.

Its the only thing can see its messed.
[ONE Android Development] yijinsa:
Flash Aroma gapp sometimes works sometimes caused reboot
[ONE Android Development] Timmmmaaahh!:
This is the good stuff! Been stressing out 3.1.0-4 and it's holding up great on OPO. Copying a rather large TiBu backup folder over USB while creating Nandroid backups is probably not the smartest idea but hot dang it works like a charm on this baby. Thanks for keeping your Tuga builds alive, [MENTION=1427327]danieldmm[/MENTION]!
[ONE Android Development] danieldmm:
Thanks mate, 3.1.0-4 it's definitely daily driver...
[ONE Android Development] DjDiabolik:
I have a possibly stupid question :

I can use flashify on Tugapower n27 for flash this 3.1.0-4? Flashify it's working whit Magisk su?
[ONE Android Development] xlollomanx:
1) yes, I'm using flashify since kk if I'm not wrong.

2) I don't know l never used magisk, maybe you can try it and see if flashify work with it or say you're not rooted.

Sent from my Oneplus One
[ONE Android Development] DjDiabolik:
Yeah i know i can use flashify.... Although I have always used until we use SuperSU. I would not like now with magisk has created some incompatibility about the usage of Flashify..... if the flash fails for some reason I would get a heavy paperweight instead of a smartphone :)
[ONE Android Development] xlollomanx:
Sorry, I'm not explained well. What i want to say is if flashify has been able to get root access or not, because i think is this the problem.
[ONE Android Development] ichigo696:
I'm on tuga n28, magisk root, alla working fine
[ONE Android Development] DjDiabolik:
Oh ok boys.......... i have using flashify right now from N27 to flash 3.1.0-4...... all goes whitout any problems!
[ONE Android Development] kewinhw:
This recovery is the best! Rock solid and faster than official twrp
[ONE Android Development] FullWipe:
Something goes wrong when i try to download the last version...
[ONE Android Development] danieldmm:
Try again, probably some AFH glitch, tried right now and no issues, mirrors are found.
[ONE Android Development] Lither:
Which version is the most stable?
[ONE Android Development] Hunting_Party10:
[MENTION=1427327]danieldmm[/MENTION]

I'm having a small problem with the recovery ,the restore times are very long about 4 GB data takes around 700 sec to restore compared to standard twrp which take about 300 sec

Any fixes for this ?
[ONE Android Development] Timmmmaaahh!:
You're probably confused as OP states "TWRP 3.1.0-4-TugaPower its on test and bugs can happen." but in my experience it's rock solid. Haven't spotted a single glitch and been wiping/making backups/flashing quite a bit with it. If you've got some time to kill and wouldn't mind a tiny heart attack experience, I suggest 3.1.0-3, which can hang for over 20 minutes on formatting System =D
[ONE Android Development] danieldmm:
Need to update OP, -4 already passed the Quality Assurance :D
[ONE Android Development] :
Is there any reason why this project is not open-sourced? This is my 3rd time asking politely, the other 2 times my posts got deleted. No idea why...
[ONE Android Development] Lither:
I have bought a second hand OnePlus One, is it safe to format system and internal storage using this TWRP? As I heard formatting internal storage might corrupt EFS partitions or brick the phone
[ONE Android Development] Anghirrim:
Just follow the global information thread from the OPO General section to backup you efs using fastboot/adb.

Then do everything you want with TWRP.

This TWRP is really stable and good, but flashing things onto a phone can always corrupt something (the risk is extremely low but exists anyway).
[ONE Android Development] Timmmmaaahh!:
Hi! I just read an interesting statement in the RR Bacon thread:

Now, I won't judge about the tone in that message, that's not in my nature, but the claim has me wondering: shouldn't partition naming be exactly the same as official TWRP? Perhaps the claim isn't true. If it is, this could break a few things if someone switches versions and attempts to restore a "foreign" backup, no? If this is a silly question or I shouldn't bring up another unofficial TWRP in here, please forgive my ignorance :)
[ONE Android Development] danieldmm:
That user already caused trouble enough in this thread, will not even answer about that. My TWRP follow the oficial twrp naming cheme. That's all.

Cheers
[ONE Android Development] Timmmmaaahh!:
Thank you anyway, Daniel. I suspected as much :)

Cheers!
[ONE Android Development] Kutep0v:
That's funny. I wouldn't mind seeing this scheme, considering that the official TWRP for our device doesn't to make backup EFS and doesn't have corresponding lines in fstab. If you decide that your way with "modem_stX" is official, then here it is pointless to argue, master Daniel.
[ONE Android Development] danieldmm:
It uses the same cheme [MENTION=3814731]katinatez[/MENTION] used back when he maintened the unnonficial twrp for our device, if you decide to change the name, it's up to you, if change now the name cheme, consequences would be the same, with people not being hable to restore. Will not change the efs name just because yours have a different name. Also try no to be sarcastic.
[ONE Android Development] Kutep0v:
I was about to expect such an answer. First you told tales about the official version, which has nothing to do with EFS, and now smoothly moved to an unofficial one. It's brilliant.

Well, since when did the unofficial scheme become official? Usually in fstab is used a real partition name, but you have nonexistent modem_stX, where modemstX is mounted. Now you say that I'm to blame I changed name... I fixed incorrect name and improved backup with the addition of one more important partition. You can to follow the old scheme to the detriment of logic and any improvement, I'll also stick to my course. There is no point in maintaining the old scheme. People knew what was coming. If they made a backup EFS on a obsolete version, let it be restored there, and don't climb with this garbage to new versions.
[ONE Android Development] danieldmm:
Whatever mate...

Cheers
[ONE Android Development] danieldmm:
TWRP 3.1.0-5-TugaPower

Fix reboot when no OS is present

Complete support for project pathmap

Improve automatic detection of QCOM RTC fix

Adopted Storage: backup keys but do not wipe them

ADB Backup: fix adb restore issues

https://www.androidfilehost.com/?fid=745425885120730074
[ONE Android Development] dragoi90:
Just flashed Twrp 3.1.0-5 but when i wanted to flash latest RR it presented the error-7.And it said it cant be flashed because of the newer os.I made a full nand before the flashing!Can you it please?Thanx!
[ONE Android Development] counterfeit187:
Will this path stuff fix doing OTA update on official lineage builds? The last time I tried to install ota it just rebooted to TWRP and I have to do the flash manually. That was May 1st update.
[ONE Android Development] danieldmm:
Error-7 normally means a bad zip file, try re downloading the zip again and check its md5 to confirm the integrity.

It seems lineage changed the location of the download OTA to /data/data/org.lineageos.updater/app_updates , this is probably the problem because data partition it's not automatically mounted on TWRP. Will have a look at that to confirm if the issue is that. But please try next OTA with -5 to see if same happens.

Enviado do meu ONEPLUS A3003 através de Tapatalk
[ONE Android Development] Timmmmaaahh!:
Backup /system & /data (250 sec, ~5.1GB), /modem, /EFS & /boot (few secs) went smooth on -5, kernel flash too. Flashing ROM whenever update is available. So far so good.
[ONE Android Development] danieldmm:
Thanks for the feedback...
[ONE Android Development] dragoi90:
I redownloaded the rom and tried again to flash it!The same happened as the other time!I made a screenshot about the problem!
[ONE Android Development] xlollomanx:
I use your same ROM and this recovery. On my device it flashed without any problems. How large is your ROM zip file? It should be about 356mb.

Have you checked the md5?

Sent from my Oneplus One
[ONE Android Development] dragoi90:
Of course i checked the MD5,its like a habit now!Although i use the 02 May Build.I will check LineageOS and reflash 03 May build!Will keep you informed!
[ONE Android Development] danieldmm:
The text explain the issue. You are installing a der rom on top of a new one.
[ONE Android Development] dragoi90:
I flashed LineageOs(the last one) and i booted it fine!I then tried to flash the latest RR and still had the same problem!I dont know if its a recovery problem but i want your help here!Thanx in adwance!
[ONE Android Development] danieldmm:
It's not recovery, it's the script in RR, my advise its you to post the issue over the thread of your rom maintener.
[ONE Android Development] dragoi90:
Thank you danieldmm!Sorry to disturb you!
[ONE Android Development] danieldmm:
You did not disturbme mate. Just tell the dev to check its script installation. Something should be wrong there.
[ONE Android Development] counterfeit187:
Yeah, still just rebooted to recovery and I have to manually select the file to flash on May 8.
[ONE Android Development] danieldmm:
Can you tell me since when it stopped working? That way will try to track on LibeageOS source what it's causing that. Probably LineageOS changed how Lineage OTA dill with files.
[ONE Android Development] C4SCA:
That issue happened to once in a while with every recovery. Fixed by redownloading the rom from OTA updater and right after it finished to download clicked update. Worked just fine, may 8 update, -4 recovery
[ONE Android Development] danieldmm:
Need someone to confirm if the same happen on -5
[ONE Android Development] counterfeit187:
Sorry I don't know how far back this goes. I was using your rom until your vacation.
[ONE Android Development] danieldmm:
Did you clean flashed oficial LineageOS?
[ONE Android Development] counterfeit187:
Yes , of course I actually wiped all my internal storage and everything
[ONE Android Development] danieldmm:
Mean while, try cyandelta to update LineageOS oficial rom. It should work without issues.
[ONE Android Development] danieldmm:
More people with problem updating trough oficial LineageOS OTA app?
[ONE Android Development] gqukyo:
LOS update worked fine on -2, updated to -5, still worked fine. Just updated to the 5/8 build
[ONE Android Development] Timmmmaaahh!:
Both dirty and clean flashing of RR on -5 very successful here!

Sizzled with Bacon ?
[ONE Android Development] hb17:
No problems with flashing, restoring whether dirty or clean on Validus, -5 working just fine.
[ONE Android Development] asalikhov:
[MENTION=1427327]danieldmm[/MENTION] twrp-3.1.1.0 is out :)

https://dl.twrp.me/bacon/
[ONE Android Development] phillibl:
How does it compare?
[ONE Android Development] asalikhov:
[MENTION=4597400]phillibl[/MENTION] you can find changes here: https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
[ONE Android Development] danieldmm:
If you look to differentes you will notice most of stuff from 3.1.1.0 its already present on 3.1.0-5

Will still build based on the new sources.
[ONE Android Development] HannibalLecter:
you've been doing a great job. :)

Ahead of the official and being great at it. :good:
[ONE Android Development] phillibl:
Thanks, keep up the awesome work. I'll probably just stick with your builds for the time being, you update so much quicker than official.
[ONE Android Development] danieldmm:
TWRP 3.1.1-0-TugaPower

fix logic of TW_USE_MINUI_CUSTOM_FONTS

etc: remove "." from LD_LIBRARY_PATH

mtdutils: Fix mounting partitions by-name

gui: fix line wrapping in terminal, issue #876

3.1.1

https://www.androidfilehost.com/?fid=673368273298956349

Run a couple of tests and all seems be working as usual. Altough its not tested like the -5 version, if something its not working for you guys please let me know.

Cheers
[ONE Android Development] Romhunters:
Need help regarding device detection in TWRP on PC.

First of all thanks for this super stable recovery. Now coming to issue that I have is when I connect my device to PC while in recovery, the device doesn't gets detected in PC which I desperately need in order to clean flash a Rom wiping everything including the internal partition. previously this used to work fine but recently I don't know where it got messed up. When connecting the device to PC in recovery, the usual windows USB connecting sound comes but with no effect. Even the remove device section shows the device to eject as A0001 but the MTP option doesn't works at all and the device doesn't gets detected in PC. While when I boot to the system the device connects to the PC in MTP flawless and I can transfer everything to and from. I'm clueless, help appreciated.

ADB USB debugging enabled.

ADB driver properly installed.

Device driver properly installed

Windows 10.
[ONE Android Development] Timmmmaaahh!:
By that you mean it doesn't return anything when using "adb devices", right?

Is your adb.exe up to date? Sometimes a newer version can help. You can find it officially by Google without having to get the entire SDK here:

https://developer.android.com/studio/releases/platform-tools.html
[ONE Android Development] Romhunters:
Command "ADB devices" works fine. The issue is while in TWRP recovery when I connect my device to PC, I can't transfer files to and from since my PC can't find the device as storage device. Strangely when I boot to system, everything works flawless.
[ONE Android Development] Timmmmaaahh!:
Oh, then my expertise ends here. I could still venture a wild guess: did you attach an OTG device recently? Perhaps, when 'Select Storage' is still set to "USB-OTG" (in the 'Mount' menu), the Internal Storage won't be detected on the PC. That's just a wild guess, I'd probably reset to default when that's not it :p
[ONE Android Development] Romhunters:
Recently I tried to install Multirom but something was weird as the Multirom menu never booted while booting to system. Thus I uninstalled Multirom and again switched back to the last Tuga recovery from Multirom recovery.

Tried to install Multirom version V33b and V33e by nospamdan yet both strangely had the same issue, thus reverted.
[ONE Android Development] danieldmm:
Still with problem?
[ONE Android Development] danieldmm:
TWRP 3.1.1-1-TugaPower

Fix incorrect 'unlink' return value check

twrpDigest refactor

Fix minui issues for some build trees

ors: Update doc

Improve decrypted partition logging

adbbackup: write smaller reads less than 512 bytes

Fix various memory errors

cryptfs: Remove dm-crypt device on failed table load

https://www.androidfilehost.com/?fid=961840155545577222
[ONE Android Development] pritambhadane:
I have flashed this latest tuga recovery and flash the latest hdpi light play theme but twrp fails to theme

Please look in to this
[ONE Android Development] danieldmm:
Point me to the link of theme (thread)
[ONE Android Development] aocboe:
Can you remove the twrp app and related options and tips? We don't need it,thx.
[ONE Android Development] Ruvy:
Are you high ?
[ONE Android Development] evronetwork:
just wondering ..in recovery the charging led(if you charge the phone) is still "broken" ? or it stays lit as it should be
[ONE Android Development] aocboe:
No, I don't drink. Maybe the problem is in my poor English(¯―¯٥)
[ONE Android Development] pritambhadane:
[MENTION=1427327]danieldmm[/MENTION]

https://www.androidfilehost.com/?fid=817550096634777637

Thread https://xdaforums.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
[ONE Android Development] pritambhadane:
[MENTION=1427327]danieldmm[/MENTION] r u busy if not why u r not replying
[ONE Android Development] danieldmm:
Sorry for not answaring, on my mind did answered, at least tough so.

Its easy why it fails, you need to ask to the dev of theme to update the theme to newest TWRP version, if you dont want to wait, just open the theme zip and edit the ui.xml file

Line 9

<themeversion>2</themeversion> and change to <themeversion>[COLOR="Red"]3[/COLOR]</themeversion>

Then flash again the zip, it will work.
[ONE Android Development] pritambhadane:
Thank you for your reply i have done the same as you told still i m not able to theme it would you please share the modified zip here

Thank you in advance
[ONE Android Development] JG:
See this post

Thanks [MENTION=2719389]z31s1g[/MENTION]
[ONE Android Development] danieldmm:
TWRP 3.1.1-2-TugaPower 2017-07-09

backup: fix return handling when no digest is being created

libtar: Fix restore of e4crypt policies

https://www.androidfilehost.com/?fid=961840155545580435
[ONE Android Development] Younex:
There's a + next to the battery percentage in TWRP when charging, I think it does the job just fine ^^
[ONE Android Development] PlasmaPump:
[MENTION=1427327]danieldmm[/MENTION] have you been able to try the auto-reboot not working I mentioned in the other thread?

Any fixes coming for that?

Thanks!
[ONE Android Development] alroger:
It works as usual. Maybe it's the script created from the app in question.
[ONE Android Development] PlasmaPump:
I'm flashing ROMs and IMGs that rebooted with version 3.0.2-2 but don't auto-reboot even though the option is selected on version 3.0.2-3. So it has to be TWRP, nothing else has changed, I even tried flashing TWRP 3.0.2-3 again. If I go back to 3.0.2-2 it auto-reboots.
[ONE Android Development] counterfeit187:
Never had problems with auto reboot here. Using cm updater works fine, installs and reboots. Using 3.0.2-3

What are you trying to install that isn't rebooting correctly?
[ONE Android Development] danieldmm:
Tried this weekend on 3.0.2-3 and no issues mate, all working fine. Phone rebooted after flashing zip file.

Are you using some theme ?
[ONE Android Development] WyldWolf:
I get error 7 even after reflashing full COS13.0 and even redownloading the cm-bacon-64003595ee-to-ced5430fc0-signed.zip. Should this version be able to flash this incremental without error 7 and how do I get it to work?
[ONE Android Development] danieldmm:
Don't think twrp it's compatible with COS, if you Google a little the results are in front over the first page. Kmow someone did made some twrp compatible, don't remember where read that, you must find by yourself. Sorry

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] DjDiabolik:
twrp it's fully compatible whit cos rom... but you can't use every incremental zip. you can use and handle only full zip rom...
[ONE Android Development] danieldmm:
But since user was talking of incremental that's why my answer.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] monyozt:
im running lastest build official rom on my OPO. cm-13.1-ZNH2KAS254

flashing TWRP_3.0.2-3-TugaPower via ADB, but when i boot into recovery, im back to stock recovery, anyone know?

flashing for the 3rd time, after flashing success, i turn off my phone manually, and now my phone totally dead, no charging LED, can't boot into recover or fastboot. help me
[ONE Android Development] danieldmm:
You have bootloader unlocked? Also you must disable the stock recovery flash on developer options, that's why you flash and stock recovery is always there after reboot. The recovery flash it self won't brick the device. Try disconnecting from pc and then reboot to fastboot or recovery.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Mike9966:
After

fastboot flash recovery TWRP.img

type

fastboot reboot

and hold volume down ~ 3 seconds when show logo "1+" for boot TWRP.
[ONE Android Development] WyldWolf:
Do you guys even read what this build is?!? Tuga is a oneplus guy and the biggest thing about this (his) TWRP mod is that is DOES apply the COS OTA incrementals on a oneplus. BTW, lots other having this prob and I found a solution posted on the oneplus forums that worked for me too which was just to chain the full COS 13.0 signed + the incremental both in one install operation and when I did that it worked just fine and dirty flashed the OTA without losing anything. Not sure if I have to do that every incremental or now that I reflashed the full dirty using this TWRP that now all future incrementals until a major COS 14 will work without that error 7?
[ONE Android Development] danieldmm:
Thanks for quoting my post :D

Did not tested COS flash with my TWRP, assumed it needed something else, or maybe confused with O2, either way, thanks for the feedback...

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] DjDiabolik:
And i can confirm... i have flashed cm-13.1-ZNH2KAS254-bacon-signed-9fbe6186fd.zip whitout any problems on my OPO over previous ZNH2KAS1KN whitout any problems and whitout any error.

The only things we can't use whit twrp or whit any custom recovery it's the only incremental zip..... the incremental zip it's only flashable by stock cm recovery.
[ONE Android Development] WyldWolf:
Simply not true. I have since successfully flashed the incremental using Tuga's TWRP. As long as you've flashed the full then the incremental in the same operation, it works absolutely fine for dirty flash with zero data or app loss.
[ONE Android Development] DjDiabolik:
Have you read my reply ? what you don't understand when i say only ?

and i'm quote my self:

There's only one way:

If you want to use an incremental zip you need ever to flash first the previous full zip rom......... simply as i already says, you can't use ONLY the incremental zip :)
[ONE Android Development] madcom8888:
Can I flash TugaPower .img file directly from official twrp 3.0.2.0?
[ONE Android Development] Mike9966:
Yes.
[ONE Android Development] funCrash93:
does it support NTFS for OTG USB? (quite handy to make the nandroid to an external USB device ;) )

---------- Post added at 03:46 PM ---------- Previous post was at 02:56 PM ----------

got "Unable to locate '/firmware' partition for backup calculations." while nandroid.