yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] danieldmm:
Not on my side, at least think not, but on the week-end will pick again TWRP project and make some tests, same time double check if miss something relative to my older builds or if something can be make to speed up a little more.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] deepu458:
Thank U Buddy. I really appreciate ur effort & passion in the work. At Least this time i had made sure that the speed this time was 8mb/sec. im confident last time it was much faster than this.
[ONE Android Development] TonySuperPony:
[MENTION=4021423]ketut.kumajaya[/MENTION] Is development dead? Or are you just busy, I'm not asking an ETA, just want to know what your plans are. If you don't want to answer this, I also understand.

Thanks for all your work on our beautiful device ;)
[ONE Android Development] DjDiabolik:
I have made a similar question about two weeks ago but nothing info about this................. the 3.0.2-Tugapower it's working whitout problems apparently :)
[ONE Android Development] danieldmm:
Finally arranged time to make the nandroid test speed, on my device the speed is not an issue.

Almost 7Gb nandroid size, no compression, all default options, it took 390sec. Cannot complaint :)

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] rerevene:
HTC
[ONE Android Development] :
the problem is when u use compression for backing up any partition. Take a look at before and after pics of compression off then on https://imgur.com/a/652Lu
[ONE Android Development] danieldmm:
You want the backup time to be the same using compression? That's not possible. Is normal that compression will slow down a lot the backup/restore.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] :
okay, but using v 3.0 compression time is better and thus people were saying slow speed and after ur post i tried to indicate that compression speed had been slowed not whole twrp to all.
[ONE Android Development] deepu458:
The only thing i can see the difference i have enabled the Compression option for the Backup. So do u think tht might be the one that causes the lag in Backup?
[ONE Android Development] danieldmm:
Would not say lag, but is normal using compression it takes more time. Because is not straight backup, it must compress files first.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] deepu458:
Thx next time i will try to make backups with & without compression enabled and see how much of a space am i saving. But if u dont mind can u try to reduce this Compression time anything better as u r Master in it.

Sry dont mind if its something really hard to do.
[ONE Android Development] HaTrED_:
That would be awesome mate! I'm still using TWRP's 2.8.6.0.6 cause it's extremely fast and reliable! :good:
[ONE Android Development] :
would u pls upload speed when compression enabled for comparison
[ONE Android Development] deepu458:
Hey i had cross checked it today with Compression the speed was 8mb/sec but without compression the speed was double of that.
[MENTION=1427327]danieldmm[/MENTION], buddy i think this slow backup speed bcase of compression is only happening in 3.0.2.0. But when i use 3.0.1.6 the speed with compression is faster than this.

One more question sir, does this twrp speed and other things related to TWRP depends on the CPU Governors that we set in ROM? the reason i ask is i use some battery savings settings CPU governor in ROM.
[ONE Android Development] :
gov and other kernel settings would have no effect as they are part of os and even implemented after boot up and what does it mean that compression not work on the twrp version u stated
[ONE Android Development] HaTrED_:
There's no much doubts about it...
[ONE Android Development] :
thx and i see the a diff of good 4 mb. idc if dev takes care of this or not though. Just wanted to report and counters check this speed issue
[ONE Android Development] Orphee:
Hello,

With TugaPower version, adb is broken, with official TWRP, adb works... did I miss something ?

Thank you !
[ONE Android Development] danieldmm:
adb sideload?

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Orphee:
adb shell
[ONE Android Development] DjDiabolik:
Apparently i have tryed and adb working whitout problems......... i have tryed to connect usb to my pc and using adb devices........ all it's working.
[ONE Android Development] Orphee:
Just tried again

3.0.2 TugaPower :

C:\Windows\System32>adb shell

error: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

C:\Windows\System32>adb devices

List of devices attached

5616442c unauthorized

3.0.2 official :

C:\Windows\System32>adb shell

~ # ←[6n

~ # ←[6n

~ # ←[6nexit

C:\Windows\System32>adb devices

List of devices attached

5616442c recovery
[ONE Android Development] danieldmm:
Did you try adb kill-server? Will try latter on my pc to see if it give the same error.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Orphee:
Yes I tried all options I found on Google, even wipe appdata folder to rebuild rsa files.
[ONE Android Development] DjDiabolik:
"unauthorized" it's simply the problems i thinks.

Try to disable and re-enable the debug usb on your rom and you need to re-obtain the authorization appears on screen of your opo.

Otherwise on cos12.1 i don't have problems... i obtain device attached....
[ONE Android Development] Orphee:
I already tried every possible things. Off course i tried this. adb works on OS without any issue and work official twrp. Only tugapower 3.0.2 fails on adb.
[ONE Android Development] alroger:
ADB shell in TWRP

Guys, excuse me. Let me step in.

I'm not sure everyone is talking about the same thing, so I would like to clear it up.

Before Android M, I was able to ADB shell into the TWRP recovery. Simple. Nothing to to with adb sideload, nothing to do with the ROM's adb, which some ask for authorization to allow your PC in. (Tuga doesn't ask that)

In todays TWRPs, I get this when trying to adb shell into TWRP:

alroger@phenom:~$ adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.

I didn't say anything before because I don't miss it.. but I have used it a lot in the early days.

OBS: I might be mixing memories from bacon and my old p1 Tab... but I have used adb shell in recovery a lot, including for resizing partitions before flashing.
[ONE Android Development] DjDiabolik:
[MENTION=1427327]danieldmm[/MENTION] when you can.. confirm if you have problems whit adb........ i have tryed and i can obtainthe adb devices and i can see my opo attached....... it's possibly it's releated to rom ? [MENTION=4101982]alroger[/MENTION] have a rom android m...... [MENTION=813614]Orphee[/MENTION] you ? Lollipop or M ?
[ONE Android Development] Orphee:
COS 13 official for me. Of course as I said, I only have issue under tugapower recovery. When phone booted on android, it works. And works too with official twrp. I'll do some more tests when possible.
[ONE Android Development] danieldmm:
Will try to check this tonight on mine...
[ONE Android Development] unavix:
Hi.

Can anyone advise me how to restore Nandroid backup when I got this error - E: extractTarFork () process ended with ERROR = 255

I use unofficial twrp Recovery 3.0.2.0 from [MENTION=1427327]danieldmm[/MENTION].

The restoration also does not work with official twrp 3.0.2.0.
[ONE Android Development] danieldmm:
It gives error but it should be hable to finish restore. Did you try reboot after the restore ended?
[ONE Android Development] unavix:
Restoring Nandroid will not start at all. I tried to install Temasek pure rom, omnirom all have the same problem. Wifi does not work or sim card. Neither the new installation slimsaber rom does not work properly. Also bug with wifi and sim. Finally, I tried installing CM 13. After installing the CM everything works correctly.

This is very strange. CM13 use yet, but I want to go back to slimsaber. How do I do it?
[ONE Android Development] Odysseus1962:
The ADB shell issue may be related to the conversion from busybox to toybox in Marshmallow and in turn the latest versions of TWRP. It is well known that there are some issues and differences between these two as they are not drop-in replacements for each other. I believe that when one issues the ADB shell command the instructions are then run off of the device instead of the host computer. Perhaps that is the area where one should look for solutions. Just a suggestion, as I haven't never had the need to use these commands myself.
[ONE Android Development] danieldmm:
Not relative because my TWRP uses busybox still, it have the binaries present in sbin.

Being really busy at my work, sorry for not updating things, will try to check things this week-end.
[ONE Android Development] danieldmm:
Did tested right now, no issues, although it was tested with TWRP_3.0.2-1-TugaPower, will post here as soon is tested flashing rom if is ok.

Cheers
[ONE Android Development] danieldmm:
TWRP_3.0.2-1-TugaPower

Fixup reboot after install variables

libenc: migrate to android_system_core

ADB: Add adb backup for TWRP

Note how to use ADB backup:

Using adb backup on the client side you can backup the partitions TWRP knows about.

On the client side you can do the following:

adb backup -f <filename>--twrp <options> where options are

--compress: compress data

system: backup system

cache: backup cache

data: backup data

boot: backup boot

etc for each partition.

You can string multiple options,

i.e. adb backup -f <filename> --twrp --compress cache system data

To restore the backup use the following convention:

adb restore <filename>

twrp: remove liblz4-static dependency

Improve greek translation

Languages: Add font for Japanese

Languages: Update Japanese translation

Restore TW_SCREEN_BLANK_ON_BOOT functionality.

Fix decrypt of odd number length PIN on hardware crypto

Partition: Fix parsing of several twrp fstab flags

Update spanish translation

Update hungarian translation

translate install reboot option to dutch

Greek Translation from the updated en.xml

https://www.androidfilehost.com/?fid=4996503000517181989
[ONE Android Development] kanyazsombor:
I figured it out! The problem is that you made a full nandroid, or at least included firmware in the backup. When you tried to restore the nandroid (including firmware) the twrp showed the error and in the mean time borked your firmware on the phone. So after you didn't have mobile reception...

Installing cm13 helped because it has the firmware. Any other rom usually doesn't have it.

So I assume that twrp302tugapower can't restore the firmware correctly.

My solution was to reflash the firmware from zip (using the same twrp302tugapower), than restore the nandroid backup BUT UNCHECKED THE FIRMWARE! This way the restore worked, and didn't loose the mobile reception.

Hope it helps for you!

DirtyLightningBacon
[ONE Android Development] danieldmm:
Don't think so because did tested the firmware backup and restore. Compared sha1 values and they match so it could not be the case.
[ONE Android Development] Sukarn:
[MENTION=1427327]danieldmm[/MENTION]

Bug in 3.0.2-1:

Any time zone set to UTC+N, except UTC+0, is treated as UTC+N+1.

So UTC+1 in settings is treated as UTC+2.

UTC+2 In settings is treated as UTC+3.

Try it. There's a jump of 2 hours between UTC+0 and UTC+1.

[Tested with 30 minute offset and 0 minutes offset]
[ONE Android Development] DjDiabolik:
Great a new version... tomorrow i flash immediatelly :)
[ONE Android Development] P1nGu1n_:
Without having tested it, that actually sounds like Daylight Saving Time.
[ONE Android Development] unavix:
[MENTION=3673203]kanyazsombor[/MENTION] you're right.

I tried to recover SlimSaber without restoring the firmware. Restoration is complete. But WiFi and Sim not working.

Which firmware should I then upload? Can you give me a link.

Touch 1+1
[ONE Android Development] Sukarn:
You're right, of course! What a horrible oversight on my part. I've never bothered looking at DST settings in any software before, because my time zone doesn't have any DST.
[ONE Android Development] kanyazsombor:
http://xdaforums.com/showthread.php?t=3300907

That is a firmware collection thread. I'm using the oxygen one, but make some reading and choose yours.

Alternative, and maybe easier way to flash the most recent cm13 nightly, because it contains the firmware files. After flashing it you don't need to boot it. In the same twrp session wipe cache, dalvik, system, data and flash your rom, or make a nandroid restore.

DirtyLightningBacon
[ONE Android Development] eris23:
Progress bar didn't move. Files counted accurately, but was showing trillions of MB and hundreds of thousands percent.

Question: does this build have the decryption fixes of TWRP-3.0.2-0-bacon-with-decryption-cm13-AtAM1 ?
[ONE Android Development] danieldmm:
Yes, it have the fixes but the 3.0.2 does not work with cm13. Even the official one. It was tested. Check the official TWRP topic. Also for the count? Backup or restore?

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] eris23:
Backup. I've been using it on sultanxda's cm13 rom. Until now I've had no problem with it (but I don't use encryption).
[ONE Android Development] unavix:
I was able to eventually restore the backup slimsaber rom. But the procedure is breakneck.

1 - I backed up all data on the SD phone to pc

2 - flash stock rom cyanogen 12.1 via fastboot

3 - update ota 12.1 to 13.0

4 - flash stock twrp 3.0.2.0 via fastboot

5 - flash twrp @ danieldmm unofficial twrp 3.0.2.0

6 - start system. Connect your phone to the PC and copied back to your phone's SD all the backed up data

7 - Reboot into recovery. Wipe Dalvik / cache, data and system.

Flash CM firmware SNAPSHOT March 2016. Wipe Dalvik and cache

Nandroid restore slimsaber (no firmware)

During restore Nandroid backup in twrp displays buzz - Warning! ext4 backup was performed. If you restore the data to ext4, the phone will not boot (warning text color yellow)

8 - restart the phone. Long waiting. SlimSaber rom running. Everything works ok - wifi, sim mobile data. I'll have to test if everything is correct. So far everything seems to be ok.

Another way I failed to restoring Nandroid backup slimsaber rom. I also tried other versions twrp, stock and unofficial versions from 2.8.7.0 to 3.0.2.0. No version of the work for me.

Please excuse my bad English. Maybe this procedure may help other users who will have the same problem.

Thank [MENTION=3673203]kanyazsombor[/MENTION] idea for repair. :good:
[ONE Android Development] danieldmm:
Crazy, just crazy :D

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] kanyazsombor:
Why didn't you do it just from nr 7 in twrp302tugap?

Anyway glad that it works now [emoji106]

DirtyLightningBacon
[ONE Android Development] PlasmaPump:
[MENTION=1427327]danieldmm[/MENTION] Flashed TWRP 3.0.2-1 TugaPower, did a backup without compression and MD5 to be generated. Backup went ok but even though it said Generating MD5 it didn't save one. I checked the log and it confirms the line to save the MD5 is missing.
[ONE Android Development] Sukarn:
3.0.2-1 TugaPower

Backup through openrecoveryscript failed. Same backup options, performed straight through TWRP worked.

Also, when the scripted backup failed, it said that it was cleaning up backup folder, but you can see in the logs that when the manual backup started, there was much less free space than before.

Logs: https://drive.google.com/file/d/0B4q2Ez1yS1rKV1k0cDc1a282M2s/view?usp=drivesdk
[ONE Android Development] danieldmm:
Will check this on mine. Although no ETA ...

Wich app are you using to send the openrecoveryscript to TWRP ?
[ONE Android Development] Sukarn:
It's my own custom app for OTA updates to ResurrectionRemix and OpenGApps. At this moment the app is useful and available only to users of ResurrectionRemix on OnePlus One.

The commands are written to /cache/recovery/openrecoveryscript in standard openrecoveryscript format, and then it reboots to recovery.

It has been working fine on 3.0.0-6, 2.8.7.0-x and 2.8.6.0-6 materialized.

This is the first time I faced a problem with it, and the problem occurred in the very first step of the script while running this command:

backup SDCBO

Other commands sent later on in the script:

install [multiple times for ROM, gapps, user-selected add-on zips]

wipe cache

wipe dalvik
[ONE Android Development] danieldmm:
Just for testing, did you delete the .twrp file inside TWRP folder? If not delete, boot one time TWRP and repeat the test of openrecoveryscrypt. I'f still fails please install lattest official one and check if it works please. Report after that please.

Thanks

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Sukarn:
Yes, after flashing this version of TWRP, I had deleted .twrp and then booted into the recovery two times, but only changed the time zone, reduced vibration intensity and reversed navigation bar layout. No other action was taken directly from TWRP before the script was run.

Trying it with the official version will have to wait till tomorrow. It's very late in the night here.

If you want, I can make the app generate the exact script that it had written and post it here.
[ONE Android Development] danieldmm:
Please test tomorrow with official one. No need for openscript, if it fails at the first command. The backup FLAGS line is all good. Test please with official. It it's good, will try something and when ready will pm you to test. But please try first with official.

Cheers and take your time.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Lisko:
On tugapower recovery i can make firmware backup but restoring always fail with tar errorcode 255 even if the backup is not compressed.
[ONE Android Development] danieldmm:
Did you try only with firmware as selection?

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Lisko:
Only with firmware and with multiple selections

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] danieldmm:
And always fails? Tomorrow will have a new build.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Sukarn:
Ouch. I had posted a reply to this post. I have no idea why it didn't show up here.

Yes, official TWRP 3.0.2-0 did work with the exact same openrecoveryscript.

The error in 3.0.2-1 tugapower was something about tar split error 255.
[ONE Android Development] Lisko:
Always...

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Android Development] Crazy_Oni:
Professor Snape?

Gesendet von meinem A0001 mit Tapatalk
[ONE Android Development] Upu:
I found little Bug [emoji3] this percentage and MB

Version: 3.0.2.1 TUGA

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] danieldmm:
TWRP_3.0.2-2-TugaPower

Fix flash of img files introduced on 3.0.2-1 ( boot / recovery )

Revert: Fixup reboot after install variables

revert: libenc: migrate to android_system_core

revert: ADB: Add adb backup for TWRP

revert: twrp: remove liblz4-static dependency

Wait to mount until after fstab processed

Remove char/string conversions in fstab processing

Rewrite FS fstab flag processing

Rewrite TWRP fstab flag processing

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

For the ones that have problems before ( backup/restore/openrecoveryscript) , try 3.0.2-2 please and report if its fixed...

Changed slightly the way things are handled
[ONE Android Development] kuteng:
is there any new release by ketut.kumajaya or katinatez?
[ONE Android Development] PlasmaPump:
[MENTION=1427327]danieldmm[/MENTION] MD5 generation is fixed on this build... at least it works on the cache partition i just tried, no time to do others right now, need my phone.

Thanks!
[ONE Android Development] Tn_wijaya:
I tried to flash TWRP_3.0.2-2-TugaPower from the previous version but failed with a message of "unable to find partition for path '/TWRP_3.0.2-2-TugaPower". I tried to reflash with TWRP 3.0.2 but no success with the same message.

Please kindly help.
[ONE Android Development] danieldmm:
Did you read the changelog at least?

3.0.2-2 fixed bug intruduced in 3.0.2-1 for the built in recovery/boot flash image file. Just use fastboot on pc to flash the new recovery or use some third app capable of flash recovery image files. There are a few on PlayStore.

Cheers

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Tn_wijaya:
Yes, it is okay.

Sorry that I did not carefully read the changelog.

Thank you for your support.
[ONE Android Development] Acxjet:
I got a problem. I can't change the cache partition to EXT4 from f2fs. It says it has been done, but it still shows f2fs. Any help?
[ONE Android Development] KaszasM:
you should be able to revert to ext4 with every other twrp, or fastboot
[ONE Android Development] danieldmm:
Remove the tick on settings for use of rm instead of format.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Acxjet:
Which was the fix. Thanks man
[ONE Android Development] danieldmm:
TWRP 3.0.2-3-TugaPower

GUI: Use standard routine for auto-reboot

GUI: Add countdown & cancel to install auto-reboot

HACK: Fix AROMA Graphics

updater: Add LZMA support to blockimg

Allow restore to read-only partition, part 2

Move force_rgb_565 up

crypto: remove redundant convert_key_to_hex_ascii call

https://www.androidfilehost.com/?fid=24580917854994496
[ONE Android Development] DjDiabolik:
Installed right now on my opo.....
[ONE Android Development] akuma48465:
thanks
[ONE Android Development] Mike9966:
This version not backup/restore partitions of firmware-radio. Why?
[ONE Android Development] danieldmm:
Because you can have firmware zip of any firmware. This files are the same on all devices. Don't see the need for that. You just need to download the firmware you want and keep it on phone.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Mike9966:
Many people want to backup/restore partitions of firmware radio... Please back this possibility.
[ONE Android Development] danieldmm:
Again, why they don't use the firmware zip instead? What's the difference?

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Mike9966:
Because they want to have this possibility for any custom ROM building on old version of Android (4.4.4) that not include firmware-radio in zip. People want backup/restore partitions of firmware-radio. Simply they wants :)

For me not need. I like latest version of Android...
[ONE Android Development] danieldmm:
That's the same thing, firmware files are not changed unless you flash firmware files. If you need firmware from 4.x , 5.x, 6.x just download the firmware zip for that version and flash. That's all. You gave thread here with all the modems.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] vivmar:
[MENTION=1427327]danieldmm[/MENTION]

hi,

latest version of your build, can make a EFS backup?

thx
[ONE Android Development] xlollomanx:
Yes, you can backup efs

Sent from my Oneplus One
[ONE Android Development] ketut.kumajaya:
I just uploaded my own build. No much change from my side except https://github.com/kumajaya/android...mmit/283ed9eded008a6f7e62c2ca53934754ae7f10ce and rebase device tree changes to the last bacon update https://github.com/kumajaya/android_device_oneplus_bacon/commits/cm-13.0-twrp
[ONE Android Development] ketut.kumajaya:
If you too lazy to check my commits, my recovery have double tap to wake feature now :laugh:
[ONE Android Development] Adduu:
Thank you for latest build.
[ONE Android Development] danieldmm:
Why only now the DTW? Its been there for quite long time on TWRP :D

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] ketut.kumajaya:
Maybe I missed something but I write https://github.com/kumajaya/android...mmit/283ed9eded008a6f7e62c2ca53934754ae7f10ce initially for Mi 4c but will be working for every device that use TARGET_TAP_TO_WAKE_NODE flag.