yashsingh1/xdaforums huggingface dataset:
[Android Software Development] JayaneshTG:
Lineage OS 14.1, based off of Android Nougat 7.1, has been ported to the Intex Aqua 4G+ by Me and HemanthTG

INSTALLATION PROCESS::cool:

* Reboot to TWRP Recovery using Vol Up and Power button

* Wipe (System, Data, and Cache)

* Install the ROM from SDcard using TWRP recovery.

* Flash GApps

* Reboot and Enjoy!!!:good:

DURATION:

Flashing : 10 mins

Booting : 10 mins

Total : 20 mins

DOWNLOAD LINKS::)

* LineageOS 14.1 by JayaneshTG and HemanthTG : https://www.androidfilehost.com/?fid=457095661767140277

* Gapps: http://opengapps.org/

* TWRP Recovery by JayaneshTG and HemanthTG : https://www.androidfilehost.com/?fid=457095661767140285

* Stock ROM :

https://docs.google.com/uc?id=0B1pkZ6xT684gRVpkdGxvLUtEdjA

BUGS:

1. Touch to focus

2. No sound in calls (Loud speaker works)

3. Double tap to awake

4. Sensors

CONTACT: (If any problem)Me:Facebook : https://www.facebook.com/JayaneshTG

Hemanth:

Facebook : https://www.facebook.com/TGHemanth

If this ROM is useful hit the Thanks button.

XDA:DevDB Information

Intex Aqua 4G+ Custom ROMs, ROM for all devices (see above for details)

Contributors

JayaneshTG, HemanthTG

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

Based On: Lineage

Version Information

Status: Beta

Current Beta Version: v1

Beta Release Date: 2017-02-26

Created 2017-02-26

Last Updated 2017-03-03
[Android Software Development] SRIHARI_GUY:
Don't create multiple threads of the same . You might be banned or your threads might be deleted by the Mods for multiple threads of the same ;)
[ONE Android Development] Kutep0v:
​

Features

Increased backup/restore speed. Restore is three times faster than on other TWRPs.

Improved EFS and Firmware backup. Backups are incompatible with other TWRPs and vice versa.

Improved AROMA hack. Almost all (or all?) AROMA archives should work fine.

LED Manager. Monitor the battery level and charging state.

Source code

Recovery

Device

Kernel

DOWNLOAD​

XDA:DevDB Information

TWRP 3.3.1-K1, Tool/Utility for the OnePlus One

Contributors

Kutep0v

Version Information

Status: Stable

Current Stable Version: 3.3.1-K1

Stable Release Date: 2018-06-01

Created 2017-04-11

Last Updated 2019-06-01
[ONE Android Development] Kutep0v:
Testing

There are currently no test versions
[ONE Android Development] Kutep0v:
Frequently asked questions

Q: Why backups are incompatible with other TWRPs and vice versa?

A: Some components have been improved or simply is not supported in other versions.

EFS backup is not supported in the official version. Other unofficial versions don't backup one important partition, which is also part of the EFS.

Firmware backup is not supported in the official version. Other unofficial versions uses an unreliable method of modem partition backup.

System Image is not supported in the official and other unofficial versions.

Q: What is the difference between System and System Image backup?

A: Different backup methods.

System – files method. Create usual archive by packing all files from a system partition. Not available since version 3.2.1-K2.

System Image – dd method. Create exact partition dump by reading every single block from a system partition.

Same backup/restore speed, but different backup size. In the first case, the backup size corresponds to size of the contained files in system partition. In the second case, the backup size always is fixed and corresponds to size of the partition.

Q: Charging LED broken in this recovery too?

A: No, it works. Since 3.2.0-K1 release included LED Manager. Logic:

If the battery status is "Charging", then:

— If the battery capacity is "Low" (1-14), then turn on the red LED.

— If the battery capacity is "Mid" (15-89), then turn on the yellow LED.

— If the battery capacity is "High" (90-100), then turn on the green LED.

If the battery status is "Discharging", then:

— If the battery capacity is "Low", then blink the red LED.

— If none of the cases is true, then turn off LED.

If the battery status is "Full", then turn on the green LED.

If none of the cases is true, then turn off LED.
[ONE Android Development] Mr.Ak:
Bery nais :)
[ONE Android Development] Kutep0v:
Well, let's compare the restore speed.

What do we have? 5504MB backup and two different TWRPs. Time:

TWRP 3.1.1-2-TugaPower: 616 sec.

TWRP 3.1.1-K3: 198 sec.

Conclusion: TWRP 3.1.1-2-TugaPower is three times slower than TWRP 3.1.1-K3. Really "flawless".
[ONE Android Development] Mr.Ak:
Okay,looks promising.

But what about Twrp 3.0.3-6 tugapower?

Anyways going to try out your recovery now to see the difference.

---------- Post added at 06:22 PM ---------- Previous post was at 06:08 PM ----------

@Kutep0v

Is lineage os 13.0 in your folder official?
[ONE Android Development] Kutep0v:
Umm... nothing. Last available 3.0.3-2 version, 3.0.3-5 broken (as always). If the 3.0.3-6 will be released, we will test.

Of course not. This is my releases for another forum. I try to maintain LineageOS 13.0 for OnePlus One.

Works update over the air. Kernel contains all CVE fixes from cm-14.1 branch.

Kernel

Device tree
[ONE Android Development] Mr.Ak:
I asked because I haven't saw your lineage os 13.0 thread on XDA.Anyways,the recovery is really fast! Thanks!

Edit: what is the difference between 'system' and 'system-img' backup?

See attachments.
[ONE Android Development] Kutep0v:
System – files backup method. Files from system partition will be packed to tar archive.

System Image – dd backup method. Partition dump. It's required in some cases.

Same backup/restore speed, but different backup size. In the first case, backup size corresponds to size of the contained files in system partition. In the second case, backup size always is fixed and corresponds to size of the partition.
[ONE Android Development] David_J96:
Queue

Can u add the ability to view the flash queue before flashing? That would be super useful.:D
[ONE Android Development] leokook:
EFS backup was not working for me on TWRP by Tugapower. I guess i will give this a try.
[ONE Android Development] f41lbl0g:
Has anyone tried flashing arise (aroma) with this twrp?
[ONE Android Development] deadlyindian:
Yes and it works (display gets kinda messy) just once, flashing any aroma zip on second try results in a reboot.
[ONE Android Development] Kutep0v:
I think, it's necessary to ask TWRP developers. For example, Matt Mower or Dees Troy.
[ONE Android Development] Gawd:
The physical buttons also get activated in the recovery. I would prefer them to stay off (no functionality+no backlight) since we already have the on-screen navbar.

Thanks.
[ONE Android Development] rolarocka:
Working awesome here, thx for this.

OnePlus One - Tapatalk
[ONE Android Development] mustang_ssc:
+1 about this
[ONE Android Development] Gawd:
Also, AROMA installer works better on Tuga Recovery. It would be great if you could also make that work just like that, nothing more.
[ONE Android Development] TbMa:
Good job, waiting for build with working decryption.
[ONE Android Development] Syaani:
You are in the wrong place. This recovery is for OnePlus One.
[ONE Android Development] thaidroid:
Yup, I re-read his post where he linked this thread. It actually said "this is what you can expect...." ;);)
[ONE Android Development] Piypoo:
Can I apply theme on this TWRP k2 ?
[ONE Android Development] bdwilk:
https://xdaforums.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692/post72966111

https://xdaforums.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692/post73355785
[ONE Android Development] Kutep0v:
TWRP 3.1.1-K3

Backup and restore a little bit faster

Charge LED (request)

More debuggable

Fix typos/inconsistencies in German language

Show scrollbar on TWRP Settings

SHA2: Enable in landscape and watch xml

twrpTar: Fix uninitialized current_archive_type

P.S. As always, I can't verify the decryption. Write to me in case of problems. :confused:
[ONE Android Development] HannibalLecter:
its ok. download finally finished
[ONE Android Development] LPW00:
Edit: ****. The upload went wrong.

Sry, I tried to attach it but XDA labs shows network errors
[ONE Android Development] HannibalLecter:
np buddy. Download finally got done.
[ONE Android Development] Kutep0v:
LED Manager

In the previous release was added the simplest Charge LED, which only lights the yellow LED when charger is connected. It seemed to me interesting and I decided to develop this idea further.

Repeatedly my device was completely discharged in TWRP because I didn't pay attention to the battery level. Quite an unpleasant situation. It would be nice to report a low battery charge with an LED. I managed to implement the behavior of the LED as in the Android... so LED Manager was born.

Logic:

If the battery status is "Charging", then:

— If the battery capacity is "Low" (1-15), then turn on the red LED.

— If the battery capacity is "Mid" (16-89), then turn on the yellow LED.

— If the battery capacity is "High" (90-100), then turn on the green LED.

If the battery status is "Discharging", then:

— If the battery capacity is "Low", then blink the red LED.

— If none of the cases is true, then turn off LED.

If the battery status is "Full", then turn on the green LED.

If none of the cases is true, then turn off LED.

At the moment it looks like everything is working. If there are no problems, this will be included in the next release. I don't know when this will happen, but definitely not in the near future, as there are no serious changes in the TWRP repository, and there's no point in updating specifically for this feature.
[ONE Android Development] Mr.Ak:
The next we'll see is "compiled with lineage os 15 source" :D
[ONE Android Development] J.E.N.O.V.A.:
Hello, I flashed the twrp 3.1.1-K2 version in recovery. After that I rebooted to the K2. Then I changed my mind and flashed the original twrp over K2 recovery. Then I tried to reboot to recovery, but it got stuck on the android logo ( the "powered by android" text disappears to. Everything else like the os and fastboot works. But I have no recovery at all anymore... And I can't flash via fastboot a new recovery. And i am not rooted

please help me
[ONE Android Development] Kutep0v:
Have you checked the checksum before flashing another recovery? Recovery can flash any image without checking it. Your new recovery could be corrupted when downloading.

Why? Bootloader is locked? In this case, you can't flash through the system without root.
[ONE Android Development] J.E.N.O.V.A.:
Nope. My bootloader is unlocked and the file I flashed is not corrupted because it is the same recovery file I flashed before without a problem.
[ONE Android Development] Kutep0v:
So why you can't flash via fastboot? You can try to clear the TWRP settings, but I'm not sure that this will help.

Edit: Couldn't reproduce your problem. I flashed the official 3.1.1-0 via 3.1.1-K2, works fine.
[ONE Android Development] seansin123:
I'm interested in using this version of TWRP.

Just like to find out if it can be used to backup/restore CM13 based ROM like jgcapp CM13?

Thanks!
[ONE Android Development] Kutep0v:
A bit strange question. Of course, you can backup any ROM based on 5.0 and newer. You should know that backups are incompatible with other TWRPs and vice versa. More info in the FAQ. For outdated KitKat, I still recommend using the old TWRP 2.8.6.0 version.
[ONE Android Development] Lisko:
Hi after updating to k3 I tried to clean flash latest aosip rom but twrp gave me error: 7 and didn't flash anything. Reverting to k2 did the trick. I will make further tests asap
[ONE Android Development] Kutep0v:
I downloaded the latest AOSiP...

Recovery newer than your ROM. You can install ROM builded after August 21 or without a strange check as below in updater-script.

(!less_than_int(1503244183, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sun Aug 20 11:49:43 EDT 2017) over newer build (" + getprop("ro.build.date") + ").");

This useless check appeared in March and was removed in May on many 7.1 ROMs. Should prevent users from "downgrading" builds, but instead of checking the build date of the ROM, updater-script checks the build date of the recovery. It works on the ROMs that comes with the recovery, but not in our case. As a result, "downgrading" is still possible, and installation of the ROM, if the recovery is newer than it, is impossible.

It's surprising that it still remained in the AOSiP, many other projects have long abandoned this check. Developers should merge a fix (commit) so that this no longer happens. I can advise you to wait for the AOSiP update before moving to 3.1.1-K3 or manually fix the updater-script in the current ROM archive.
[ONE Android Development] Mr.Ak:
[MENTION=7296006]Kutep0v[/MENTION]

What does "digest" means? Just curious because I saw it for the first time.
[ONE Android Development] JJohnson1988:
Another word for checksum. Usually MD5 or SHA1 algorithms.
[ONE Android Development] qqss:
可以可以
[ONE Android Development] Kutep0v:
[MENTION=5599724]JJohnson1988[/MENTION] is right.

Were changed string MD5 everywhere to use digest or Digest instead. SHA2 is default and better for digest creation due to decreased collision space compared to MD5 and SHA1. See https://en.m.wikipedia.org/wiki/SHA-2.
[ONE Android Development] Kutep0v:
Hello! I need help with testing. If someone really wants to help, click on the LINK. Details on the same link.

Testing is over. Thank you! ;)
[ONE Android Development] Mr.Ak:
So those changes will be included in next release?
[ONE Android Development] Kutep0v:
Yes, and also something else.

I did not receive any error reports. Еverything is fine... at least I want to believe in it. I've been using test recovery for a week and haven't found any problems.
[ONE Android Development] david72262:
I used it on aosp8.0 and no errors I've found yet.
[ONE Android Development] Mr.Ak:
Hmm,something else,I'm all ears. :)
[ONE Android Development] Kutep0v:
Nothing more, just the latest changes from the TWRP repository. I always try to update having at least one feature from me, so this feature will be is LED Manager. :eek:

I doubt that K4 will be released in the near future. There were no changes in the TWRP repository, and I don't want to release an "empty" update. But who knows, maybe something will change during this time. Honestly, now I have no more ideas how to further develop my recovery.
[ONE Android Development] bageraz:
Hi im interested to use this version of twrp but im stuck with cwm because half of my screen (top side) is broken and i need to use navbar navigation to flash & update rom. Any solution? Tq
[ONE Android Development] Kutep0v:
Hi. I think this is a bad idea. You can't use TWRP with a half broken touchscreen. Of course, you can control with the mouse via USB-OTG, but it's very inconvenient. CWM is the right solution in your case, since you can use the volume buttons to navigate. :confused:
[ONE Android Development] bageraz:
Tq for the answer. It kinda ok to be able to use mouse via usb-otg but yes not very inconvenient if emengency
[ONE Android Development] Silvered:
Hi! After I restore a backup with twrp 3.1.1-k3 I can't copy files in system partition, both with Recovery(copy and backup doesn't work) and with File manager (like MiX or Solid). Tryed with restore from AOSPA to XOS and XOS to XOS
[ONE Android Development] Kutep0v:
Any logs? On which TWRP was the backup done? Backups are incompatible with other TWRPs and vice versa.

This happens not only on our device and specifically this TWRP. There is no information. It's known that a bit more often happens with 7.1 ROM, and only the fact that TWRP can't open addon.d, because it's not a directory (??!) while backup. Earlier saw on OnePlus 3, that addon.d directory, for unknown reasons, became a bold file. It will help reinstall the ROM and create new backups.
[ONE Android Development] Ngadhnjim:
on XOS are wr problems
[ONE Android Development] Ngadhnjim:
cant say in this dont have bug
[ONE Android Development] Kutep0v:
TWRP 3.2.0-K1

3.2.0 version

LED Manager

NTFS support for USB-OTG

Fix compile error with IGNORE_MISC_WIPE_DATA in some trees

Fix more compile errors in bootloader_message_twrp

Better compatibility across 8.0.0 trees

minui: Fix building graphics_overlay.cpp

minui: Move graphics_overlay.h down that we have all structs defined

minui: Add missing <linux/ion.h> for 'struct ion_handle_data'

minui: Only include graphics_adf.h if we do not build with MSM_BSP

minui: Do not overwrite previously set CFLAGS

Fix build error in old 5.0 tree

ADB Backup: fix compilation error for remove

vold_decrypt: FDE Keymaster 3.0 support

FBE for Pixel 2

Fix issues building with LineageOS cryptfs_hw

Support v2 fstab format

ADB Backup: Fix gzip backup and restore

ADB Backup: add ability for TWRP GUI to restore

Improve greek translation

Improve automatic detection of QCOM RTC fix

Fix compile error in bootloader_message_twrp on 6.0 tree

Auto detect possible use of legacy props

Fix mkfs.f2fs build error

Fix 'No OS' on System_Image restore after wipe

Fix a few build errors

Add libraries needed in 8.0 for e2fsck and tune2fs

Make legacy props an option disabled by default

Update to AOSP 8.0 base

DO NOT MERGE Android 8.0 stuff

Remove duplicate entries & Improve Chinese translation

Decryption not verified. (as always)
[ONE Android Development] Mr.Ak:
Nice! :)
[ONE Android Development] keen36:
Decryption works :good:
[ONE Android Development] pratikone1:
Great work my friend. Restoring and backing up roms requires 1/3 of time taken by official twrp. Awesome work. Using it since 3.1.1 k1 version.
[ONE Android Development] Sandeshbhau_7:
Great work thanks:good:
[ONE Android Development] Kutep0v:
I heard that on the official version 3.2.0 some get errors when backup. I couldn't reproduce them, but if someone has similar problems, write here, I'll return the previous version. :confused:
[ONE Android Development] xlollomanx:
I backed up in restored twice...no problem on my device.

Sent from Oneplus One
[ONE Android Development] Gawd:
Did this thread got moved from 'One Original Android Development' to 'One Android Development', or is it just me?
[ONE Android Development] LThMT:
Thank you so much! You're really fast with this update, it's much appreciated! Anyways, I've done a backup with no problems. Haven't tried restoring anything yet.
[ONE Android Development] DeadFox-xda:
Nope, it was always on non original... I think
[ONE Android Development] Kutep0v:
TWRP 3.2.1-K1

3.2.1 version

Default to device backup/restore vs. adb backup/restore

Fix the inconsistencies in the spelling of SD card

Fix stuck on 'black' screen entering recovery

If you are on the 3.2.0-K1 version, it's recommended to update to prevent possible errors.
[ONE Android Development] arjun:
is 3.2.1 officially released ??
[ONE Android Development] Kutep0v:
Yes, 19 hours ago. https://github.com/omnirom/android_bootable_recovery/commits/android-8.0
[ONE Android Development] DeadFox-xda:
Omg, huge love for you, that one click download link... Best thing ever (not joking)
[ONE Android Development] pratikone1:
There were problems while flashing nougat ROM. It gave error 7. Then I rolled back to previous version and everything was alright again.
[ONE Android Development] Kutep0v:
If something like "Can't install this package over newer build", then this is not recovery problem. Just recovery is newer than your ROM, wait for the next ROM update.

Edit: already discussed earlier.

https://xdaforums.com/showpost.php?p=72298277&postcount=136

https://xdaforums.com/showpost.php?p=73581096&postcount=197
[ONE Android Development] DeadFox-xda:
With kind respect, could you make it backward compatible? Like for example darkobas marshmallow gives error 7, could you do some magic to make it work? Of course people are busy so I'm not forcing you :)
[ONE Android Development] Kutep0v:
I can try using the fake build date in the next update... or you can remove build date check in the updater-script of your ROM.
[ONE Android Development] DeadFox-xda:
Hmm will have a look later on
[ONE Android Development] sr.arenisca:
One quick question, if I update my 3.1.1-k3 the backus are going to be still compatible and I will be able to restore it?

Thanks :)
[ONE Android Development] Kutep0v:
Of course.
[ONE Android Development] sr.arenisca:
Thanks I know that is a noob question but with all the people saying that the have problems restoring their backups... I prefered to ask first HAHAH
[ONE Android Development] pratikone1:
It was dot os 1.1......by Mr. aK....but older recovery solved the problem. Just flashed the newest recovery. Awesome work. Thank you
[ONE Android Development] HannibalLecter:
download incredibly slow though. Could you please mirror?

Urgently needed :P sitting in recovery with everything cleaned.
[ONE Android Development] :
Just tested. Download finished in 8 seconds...
[ONE Android Development] DeadFox-xda:
Would mirror but out right now and can't really use my data. If someone could please help him out? I'll give you a thanks :)
[ONE Android Development] HannibalLecter:
location difference I guess. But thank god, it finally finished in 10 mins here.
[ONE Android Development] Kutep0v:
Any idea what to use as a mirror? Android File Host is the worst hosting I know. Earlier I tried to make a mirror there, but most of the time the site just did not work. I can try use github as mirror. :confused:
[ONE Android Development] HannibalLecter:
I guess Github will be the best mirror.
[ONE Android Development] Kutep0v:
Done. DOWNLOAD has two links. Schematically it looks something like DOWNLOAD where blue is Bitbucket and green is GitHub.
[ONE Android Development] HannibalLecter:
Like your sense of design here. Very minimal and very effective.

Its really nice.

Wish you could add this color scheme to the OP also.

I see in the OP DOWNLOAD is the same single Orange color.
[ONE Android Development] Kutep0v:
I tried, but the color of the link doesn't change. I can make inscriptions in small font on the sides...
[ONE Android Development] HannibalLecter:
Cool.
[ONE Android Development] Kutep0v:
I'll leave it as it is, but in the future I'll think about how to do it better. Inscriptions on the sides look ugly...
[ONE Android Development] Paulo_Silva:
I guys,

sry 4 the noob question but WHERE should i flash it?

I ask this cuz i never saw this before on other recovery flashes.

Thx in advance :good:
[ONE Android Development] LPW00:
U want to flash a recovery. So now take a second to think about in which partition the recovery might be stored... Is ur recovery a system image? Or a boot image? Or maybe, just maybe, ur recovery.img is actually a recovery image..... Whoaaaa *mind=blown*
[ONE Android Development] Paulo_Silva:
I realized that but i just wanted to be sure.

Like i said, a noob question, no need to be sooooo sarcastic but anyway thx for the help. :rolleyes:
[ONE Android Development] Mr.Ak:
There's a reason he changed his username for. :p
[ONE Android Development] Kutep0v:
Hi,

I want to take away the ability to backup the "System" and leave only the "System Image". Perhaps you will have questions like "You're crazy?", but I have reasons for this. First, this option is more reliable and accurate. Secondly, this option will prevent the possible errors when backup and restore. Thirdly, this option is a little bit faster. The side effect is to increase the backup size by ~500 MB. Of course, backups will remain compatible.

What do you think about it?
[ONE Android Development] kewinhw:
What is stored in system and what is stored in system image? :angel: I made a backup of cos13.1.2 with all the partitions avaliable will it still be able to restore it? And will it then only restore the system image partition and skip system partition?

Edit: obviously they are system partitions but how are they different I have have been thinking about since I started using your awesome recovery :cowboy: