yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] leokook:
ADB BackUP

Using the latest version of your recovery.

But not being able to use:

adb backup --twrp

I really want to backup my files from recovery, but it does not work. Device is connected to pc while using TWRP, it shows the message: "adb: unable to connect for backup: device '(null)' not found"

Drivers work perfect since I flashed your recovery 10 min before.

Does anyone know anything about this ?
[ONE Android Development] danieldmm:
Last time tested it was working, will have a look when at home latter tonight.
[ONE Android Development] danieldmm:
Advise you to check again your drivers, tested and no issues.
[ONE Android Development] leokook:
Thank you Sir.

Would you mind sharing your adb driver with me? I've test so many different versions but still no luck.
[ONE Android Development] danieldmm:
My ADB/Fastboot it's the ones from Google SDK

Cheers
[ONE Android Development] leokook:
For some reason I had to install the Google USB Driver as: Android Composite ADB Interface in order to use the ABD in recovery. Thank you.
[ONE Android Development] danieldmm:
Windows stuff :D , good you have it working.
[ONE Android Development] leokook:
Sorry to bother your again, I'm facing a new issue while trying to backup using your TWRP.

When it hits the 100%, it shows the "creating digest" but after a minute the phone restarts to OS.
[ONE Android Development] danieldmm:
TWRP 3.1.1-3-TugaPower 2017-09-17

Remove duplicate entries & Improve Chinese translation

Fix typos / inconsistencies in German language

SHA2: Enable in landscape and watch xml

Show scrollbar on TWRP Settings

twrpTar: Fix uninitialized current_archive_type

https://www.androidfilehost.com/?fid=961840155545596336
[ONE Android Development] danieldmm:
TWRP 3.1.1-3-TugaPower 2017-09-17

Remove duplicate entries & Improve Chinese translation

Fix typos / inconsistencies in German language

SHA2: Enable in landscape and watch xml

Show scrollbar on TWRP Settings

twrpTar: Fix uninitialized current_archive_type
[ONE Android Development] danieldmm:
-3 removed, problem wiping cache

Stick to -2 for the time being
[ONE Android Development] danieldmm:
TWRP 3.1.1-4-TugaPower 2017-09-17

Fixed slow format of cache

https://www.androidfilehost.com/?fid=673368273298986645
[ONE Android Development] lbaty:
I am unable to decrypt my data partition using 3.1.1-3 or 3.1.1-4. Works OK with 3.1.1-2.

Anyone else having this problem?
[ONE Android Development] danieldmm:
Already confirmed, think know what's going on. Stay tunned for -5 probably today at night if all goes well. Till then for encryption stick to -2
[ONE Android Development] kurtextrem:
Got no search results when I entered "Material", so I'm gonna ask:

Has anyone tried installing the material TWRP theme? It tells me version is not compatible, although I'm using the 311-x theme version.
[ONE Android Development] danieldmm:
2 pages back, you should search for theme word xD

https://xdaforums.com/showthread.php?p=72934732
[ONE Android Development] Feske:
Tried this recovery and something isnt good guys.. i was on twrp 3.1.1-K3 and now tried this one and i m not satisfied. I dont wanna blame, but wipping all for clean install took me 15 min and little scared me.

I dont know is this problem or not, but i m sharing my experiance.
[ONE Android Development] danieldmm:
Can you try -2 version and see if it's the same?

https://www.androidfilehost.com/?fid=961840155545580435
[ONE Android Development] Feske:
i already installed latest tuga build with k3 twrp.. have some work to do, maybe i ll reflash today and let u know.
[ONE Android Development] danieldmm:
That's why asking you to try -2 version, if you installed latest would be -3 ( removed ) or -4
[ONE Android Development] Timmmmaaahh!:
"Formatting Cache using make_ext4fs" took about 5 minutes, way longer than usual.

MTP was enabled (if that matters) but not connected. Log attached.
[ONE Android Development] danieldmm:
TWRP 3.1.1-5-TugaPower 2017-09-19

Fixed encryption

https://www.androidfilehost.com/?fid=961840155545597147
[ONE Android Development] danieldmm:
Can you try -5 ? On my device is working as before, encryption also working ( tested )
[ONE Android Development] Timmmmaaahh!:
Success! Mere seconds this time. Here's another log to compare. Can't speak for encryption, not using that.
[ONE Android Development] brainvision:
thanks man, I had problem flashing the open gapps aroma package with the official latest TWRP (3.1.1) (the infamous transparent background on Aroma UI) and I solved it flashing your version, great work!
[ONE Android Development] lbaty:
Thanks - confirming encryption working for me also with 3.1.1-5 :)
[ONE Android Development] bmark240:
Could anyone help me?

On Tugapower TWRP 3.1.1.5 I encountered Error 255 on my Nandroid backup. I am unable to clean flash or install any ROM on my device. I have even downgraded to version 3.1.1.2 but this throws the same Error 255. Before I 'upgraded' my backups worked fine. Is there a simple workaround?

Thanks!
[ONE Android Development] danieldmm:
Start the nandroid restore, when it error, copy the recovery log and attach here, you find the option on advanced, take also a screenshot of the error when restoring with the error and attach also here. Also don't write before upgrade my backups worked right because flashing TWRP will not mess up your old nandroids.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Anghirrim:
Just to confirm, I clean flashed the latest PA 7.3 this morning without problem and made a nandroid backup of my previous AOSPExtended install without issues.

So for this, 3.1.1-5 seems tonwork fine.
[ONE Android Development] bmark240:
I found out the problem. It was whilst I downloaded AOSPA 7.3....

I forgot that one of my partitions was f2fs & obviously AOSPA only likes Ext4.

I couldn't get back into my backups as they were f2fs. No matter what I tried, I couldn't get back into TWRP. Luckily I had recently installed Oreo build and from here I was able to use my phone.

Unfortunately though, I was unable to access Root because of lack of TWRP & the build didn't have inbuilt Root.

I finally managed to access ADB (no mean feat on Windows 10!!).

From there I managed to get into Fastboot & install TWRP through ADB command.

Phew!

Next I managed to reboot to TWRP to start to fix the mess of f2fs on System.

I tried to Mount Data. The partition was inaccessible. I then ran a repair & change file system to Ext4 everything got deleted.

Not good!

Finally I downloaded Resurrection Remix ROM & put the zip on USB Memory drive.

I dug out a OTG cable & connected it to both USB drive & Phone charge port...

I clicked Mount->OTG->install from OTG!

Joy!

Got up & running without GApps until I copied Resurrection Remix ROM & latest GApps package onto Downloads.

Rebooted to TWRP & checked mount on everything.

Wiped cache, Dalvik, Data, System.

Installed ROM.

Installed GApps.

Rebooted...yay!

"Houston, we have landed!"

TL...DR:

Fixed.

Moral of story:

Different ROM have very different file systems. Stick with Ext4 NOT anything else!!

I hope this read was at least entertaining if not too boring!
[ONE Android Development] danieldmm:
Well, you could easly restore f2fs on ext4, you just need to tick the option on twrp to not convert partition but instead make a wipe without formating. That would fix your problem.

Just saying :D
[ONE Android Development] bmark240:
Problem was the partitions affected were not able to be mounted. When I changed file system, the files were wiped ?
[ONE Android Development] danieldmm:
Again, will repeat the solution, convert partitions to ext4, then tick the option in twrp to use wipe instead of format, then restore your f2fs nandroid, it will restore on ext4 and keep that FS
[ONE Android Development] danieldmm:
Obviously converting data partition would format all your internal sdcard, so, prior to that you only need to copy the nandroid to pc, convert to ext4, copy again the nandroid to phone, and restore over TWRP with the ticked option to use wipe instead of format.
[ONE Android Development] bmark240:
Mission Accomplished.

At least I figured out an almost impossible task (to me)...I had to downgrade Windows 10 ?

Lesson learnt from a Master ?

Maybe I should have stuck with Tugapower ROM.

I hope to see your excellent Oreo build on my phone soon! ?
[ONE Android Development] Klewe:
Unable to Mount storage

Hi,

yesterday my phone freezed and I got stuck with a black screen. I've done a restart by pressing power button 10 seconds. Phone rebootet and got stuck after booting logo at a screen saying "starting Android". Let it there for the whole night, nothing, still "starting Android".

Booted to recovery, tried to wipe (for restoring nandroid afterwards) and it says "E: unable to mount storage". What can I do now? Tried to repair data (f2fs) and system (ext4) partition, but didn't solve the problem.

I can still install the rom from scratch and boot it up, but it won't install root and Magisk, therefore I can't even install new version of TWRP with flashify. Mine is 2.8.7.0

Please help!

Thanks
[ONE Android Development] Leoxur:
Lucky you, same problem yesterday after updating latest lineage, look in the official lineage thread :laugh:

Anyway you should update the recovery, download the img file and flash it throug 2.8.7.0
[ONE Android Development] pritambhadane:
[MENTION=1427327]danieldmm[/MENTION] TWRP 3.2 released
[ONE Android Development] Timmmmaaahh!:
Did 3.1 stop working? ;)
[ONE Android Development] danieldmm:
I know 3.2 is out, will try to build soon with the usual changes to add more backup options and better aroma support if it's possible. No eta as usual.

Cheers
[ONE Android Development] pritambhadane:
U r awesome
[ONE Android Development] danieldmm:
Litle advice, tried the new TWRP and got problems restoring nandroid, the restore process would not even start, the nandroid was done with new twrp also.

Is someone here using the new TWRP and facing same issue? Trying to restore a nandroid would not even start.
[ONE Android Development] Shadowghoster:
Not on OnePlus One, but on by SM-T580 I faced the same problem. Sometimes restoring worked, mostly it didn't.
[ONE Android Development] danieldmm:
On official thread of TWRP for OnePlus One there is already confirmation off this issue. It's affecting more devices it seems. For the time being better stay on my latest TWRP build
[ONE Android Development] danieldmm:
TWRP 3.2.1-1-TugaPower 2017-12-10

ADB Backup: Fixup

adds /persist/time/ as Qualcomm time fix source

Process AOSP wipe commands prior to encryption check

Please report some problems if you find since its first release.

Nandroid restore should be working since its fixed on TWRP source

Stuff that need to be tested:

wipe cache and dalvik and see if its slower then before or same as before, test restoring nandroid, test nandroid backup, test flash rom, see how aroma its working, test encryption

If someone go trough this tests please report how its working. ( doing nandroid as we speak and going to restore an older nandroid)

Wipe cache and dalvik for me it seems fast enought but more opinions its welcome.

https://www.androidfilehost.com/?fid=817906626617951858
[ONE Android Development] danieldmm:
OK, nandroid backup it's tested, restore its tested altough it take little time to format system prior to initiate the restore, just need to be patiente and the format will be done and the restore process start. Flashing zips its fine. Seems all good for now.
[ONE Android Development] Timmmmaaahh!:
Recovery running stable but please work a bit on speed. Full wipe (data+system+cache+dalvik/art) took 17 minutes. Just formatting cache (using make_ext4fs) after ROM flash took another 4-5 minutes. Those are tiny heart attack moments :D Full nandroid (system+data+EFS+modem+boot) was about 6-7 minutes, which is acceptable for 5 something Gigs. Flashing went smooth in every way, no remarks there :)

Keep up the great work and thanks again!
[ONE Android Development] danieldmm:
All the issues will be addressed, probably for people that is a heavy user on TWRP is better for now to stick with older version -5
[ONE Android Development] pritambhadane:
Latest twrp updated ?
[ONE Android Development] danieldmm:
Did not have time to pick this again, will see over next weekend if manage to update.
[ONE Android Development] bmark240:
Just an update:

Tried clearing Cache only on my Resurrection Remix ROM through

TWRP 3.2.1-1: Took over seven minutes. Had a cold sweat as I thought my phone was going to be unbootable. ?. Managed to reflash TWRP 3.1.1-5 and boot back into ROM - it took a few minutes to boot back into working ROM again: almost a panic attack there too!

I think I will wait for a stable fixed version before I 'update' .

¯\_ (ツ) _/¯
[ONE Android Development] Ruvy:
Any planned update in upcoming days ?

Does the old and tested version-5 flashes Oreo Roms fine or do we have to get the latest one ?
[ONE Android Development] danieldmm:
For the time being my advice is to use latest oficial one, at least till get time to update this one.
[ONE Android Development] Timmmmaaahh!:
Really? Your TWRP 3.1.1-5 is working just fine and is – IMHO – way better compared to official TWRP.
[ONE Android Development] danieldmm:
Talking about flash my Android Oreo 8.1.0 builds and possibly other Android 8.1 Oreo builds out there...
[ONE Android Development] Timmmmaaahh!:
Also flashing just fine on my end. Flashed yours, LineageOS and AOSP 8.1. No complaints ?
[ONE Android Development] bmark240:
[MENTION=1427327]danieldmm[/MENTION]:

Has this TWRP now been abandoned?

It doesn't flash a few Oreo 8.1 builds with newer firmware (c6 & c7).

Even using the MrShme Frankenstein I get Error 7.

It doesn't seem to get on with the TZ Data.

I tried using official but had errors backing up st1 modem & incompatible with your TWRP backups.

So rolled back to your 3.1.1-5.IMG.

Ended up with no TWRP on my system.

Had to flash TWRP through ADB Fastboot to resolve the issues.

Any pointers for future builds?
[ONE Android Development] danieldmm:
Since when oficial twrp backup modem or efs over bacon?

Need to manage some time to pick this again, will try over weekend but no promises.

You can flash trough fastboot the recovery.img file.

fastboot flash recovery recovery_file.img
[ONE Android Development] Timmmmaaahh!:
Really? I've been using 3.1.1-5 since it released and it's still flashing everything perfectly. I have already flashed several versions of 5 different Oreo ROMs (AOSP, LOS (unof.), Candy, Tuga, DU) and none of them showed a single error.

Of course, an update would be nice, but no pressure :)
[ONE Android Development] bmark240:
Yeah. Doesn't seem to like jgcaap 15 Oreo.

And the backup was Resurrection Remix ROM 5.8.5 final.

That's how I got TWRP back as I said.

Flash TWRP through ADB.

Still kept the backup.

I really want to use this version as I consider it the best! [MENTION=1427327]danieldmm[/MENTION]!
[ONE Android Development] danieldmm:
Use the same twrp you used for the backup, then restore will probably go just fine
[ONE Android Development] bmark240:
[MENTION=1427327]danieldmm[/MENTION], [MENTION=4841620]Timmmmaaahh[/MENTION]:

Just tried the latest Tugapower Oreo & got Error 7 there too...

Clean flash (all but internal & OTG)

And TWRP 3.1.1-5

Using this firmware:

bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
[ONE Android Development] DjDiabolik:
Because you still to use a old version ?

*EDIT*

Read the last two or three pages..... problably this:

Has suggest to not use the very last.........
[ONE Android Development] Timmmmaaahh!:
He's using the correct version, [MENTION=5919577]DjDiabolik[/MENTION]

[MENTION=7672643]bmark240[/MENTION] Your device isn't recognized somehow... Try resetting TWRP settings to default. You may want to share your flash log here. If it remains unsuccessful, you could delete the asserts lines from the updater script, which will bypass the device check. Do be careful! If you flash a ROM for another device, it will flash and (soft?)brick your phone! Triple checks advised ^_^

[MENTION=1427327]danieldmm[/MENTION] What could be causing TWRP to recognize his device as 'empty'?
[ONE Android Development] danieldmm:
Its probably the way how partitions are mounted on Oreo.
[ONE Android Development] bmark240:
Hey guys.

I cannot post recovery log here because it's too big ?

I provide a Google Drive link instead:

https://drive.google.com/file/d/1teOI7b-HD3vNUA_ULqsvtoHwt82UPvDL/view?usp=drivesdk

Thanks [MENTION=4841620]Timmmmaaahh[/MENTION]h & [MENTION=1427327]danieldmm[/MENTION].
[ONE Android Development] danieldmm:
Acess to file request sended...
[ONE Android Development] bmark240:
Granted.
[ONE Android Development] bmark240:
I have swapped to twrp-3.2.1-K2-bacon by Kutep0v and all the LOS 15.1 ROM including Tugapower Oreo build are working.
[ONE Android Development] danieldmm:
What exactely are you having? Because your log only have NandroidBackups done, no flashing of zip files.
[ONE Android Development] bmark240:
Well the KuteP0v k TWRP has sorted the problems as I said. I didn't need to change assert files.
[ONE Android Development] danieldmm:
But still not getting what issue was you having because there is no error over your log, and you say swaped *k2 to other, K2 is not my TWRP, over you log you was using TWRP TugaPower *-5
[ONE Android Development] bmark240:
Well. You have a better idea than me.

Don't sweat the small stuff. I'm sure your next TWRP will be even better than -5. Sometimes its hard to figure out errors when they don't present themselves easily.

I still think your TWRP is the best build as is your Browser.

I shall look forward to some awesome Tugapower Oreo builds in the future.
[ONE Android Development] Timmmmaaahh!:
Heya! Here's a TWRP Tuga log of me trying to flash RR O. This is the first time it didn't flash, all other Oreos went fine so far. I also switched to K2 to get RR running and it worked. Looking forward to a new Tuga version whenever you have the time. Peace ✌️
[ONE Android Development] danieldmm:
Aware of that error, that's why with new twrp does not occur, that only occur on older twrp.

Either way, trying to release a new build of TWRP over the next 2 days, if no release it will be hollydays, maybe middle of April. Let's see how it goes
[ONE Android Development] ctrlaltca:
It looks like TWRP (both vanilla, Tuga or K2) is not able to corrently decrypt an encrypted data/ partition since the last february's security patches for Oreo roms. TWRP will propose to decrypt the partition and ask for the sequence/pin, but fail to decrypt even if the correct one is provided.

Some background here: https://www.reddit.com/r/LineageOS/comments/82wjpe/how_to_install_los_151_without_twrp/ and here: https://xdaforums.com/pixel-2/help/twrp-decryption-password-2-2018-update-t3746095

I found this out while trying to upgrade my device from TugaPowerO7 to TugaPowerO10, and the best workaround i found was to sideload the rom using adb.
[ONE Android Development] QuantumSingularity:
I've got the same problem. Thnx for the workaround with adb.
[ONE Android Development] tofu:
Same issue here!
[ONE Android Development] nonzeropossibility:
It works now, false alarm
[ONE Android Development] asalikhov:
[MENTION=1427327]danieldmm[/MENTION] an update has been posted to TWRP website. If it's important, please, update your build.

https://twrp.me/site/update/2018/07/01/twrp-3.2.2-0-released.html
[ONE Android Development] achuth20:
If for whatever reason i have to change back to the official twrp build for this device,can i just flash the recovery image through the preexisting tuga twrp i have installed? [MENTION=1427327]danieldmm[/MENTION]
[ONE Android Development] TriboDoP:
Yes
[ONE Android Development] danieldmm:
It does not support ntfs, use usb pen as fat32.

Wich version are you using? My latest version does not backup firmare. Only EFS and normal partitions are available for backup. If you flashed my TWRP, and before you have others. Please delete the file .twrps inside TWRP folder and then go again to TWRP.

Cheers
[ONE Android Development] funCrash93:
yes I had another TWRP on board that supported '/firmware', I guess there shall be no problem restoring?

I know of FAT32, just thought it would be sweet to have NTFS supported as well ;)
[ONE Android Development] danieldmm:
TWRP 3.0.2-4-TugaPower

Added modem and recovery also as backup partitions

minui: Fix gr_set_font() build issue on cm-13.0 tree

NTFS-3g: migrate to PLATFORM_SDK check instead

Gui: replace pow() function

wait for cryptfs device node to come up

Add git revision to startup message in recovery.log

GUI: Use standard routine for auto-reboot

Fixup reboot after install variables

GUI: Add countdown & cancel to install auto-reboot

Finish creating disable_free_space_check variable

Allow running of a custom script after factory reset

Add build flag for forcing single buffer mode

Make input whitelist and blacklist work for mouse devices too

recovery: allow usage of TARGET_CRYPTFS_HW_PATH

bigbiff - Fix md5 creation from adb backup patch

adbbu: fix include path

Optimize and reduce size of PNG files

Add typecode to sgdisk for proper detection in Android

Remove curtainClose() remnants

Remove unused identifier from NotifyTouch

Move cursor after appending date to backup name

gui: fix Enter key in terminal

ADB: Add adb backup for TWRP

Increase EIO retry count

Check the results from applypatch

applypatch: Don't call inflate() when it expects zero-length output

Log source/target build version to last_install

Black screen patch for some HiSilicon devices (FBIOPAN_DISPLAY)

recovery: Make wear recovery more customizable

Link:Removed for the time being, need some analysis.
[ONE Android Development] danieldmm:
Try with my latest build, its modem backup/restore enabled...
[ONE Android Development] chikiro:
Thanks for the update.
[ONE Android Development] TonySuperPony:
Hey, could it be possible for twrp to automatically flash zips in a folder? That would be awesome, like when I Ota a rom, and after the Ota zip is flashed, the zips in a special folder also flash..

This would make an Ota much simpler.

If it isn't possible, no problem! You are an awesome developer :)

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Android Development] Sukarn:
You can try my unofficial Resurrection Remix OTA app. Just set it to 'Manual ROM' instead of 'Latest RR' if you are using any ROM other than the official RR builds. It can do more than what you are asking for.

You would need to install both apk files from here: https://drive.google.com/folderview?id=0B4q2Ez1yS1rKNVBIQU9KQmQtWEU

Edit: clarifying that I'm the author of that app.
[ONE Android Development] funCrash93:
updated now to latest *-4

will be waiting for the NTFS support :p
[ONE Android Development] DjDiabolik:
upgrade to -4.... thanks for continuing developing :)
[ONE Android Development] danieldmm:
Since some people are reporting some efs problem when restoring modem backup decided to remove the -4 version till further investigation. Only tested the backup of modem, did not tested the restore. Just to be on the safe side. Make sure you have a EFS backup done and isolated. If something goes wrong you can easily fix. Will check all the stuff on my device over the following days.

Cheers

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] DjDiabolik:
mmmmmm... wait for -5. for now i don't think to turn back to -3 right?
[ONE Android Development] danieldmm:
Yes, just avoid making nandroid with modem included and restore the nandroid also with modem. Will test on mine. Only then can confirm the issue. And like said, be sure to have at least a EFS backup done. Just to be on the safe side.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Paradox:
efs corrupted...continuous reboot with no baseband and imei after restoring full backup (efs problem). I tried fastboot clean flash, coloros, qualcomn recovery method but none worked. Any suggestions???
[ONE Android Development] akhenaton27:
I've passed through this and the only ROM that restored correctly my EFS was OxygenOS 1.0.0. Follow this guide for the correct steps http://xdaforums.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793