yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Yes it sure does. I noticed the SGS3 is having twrp issues similar to this device. I'm gonna look into that soon as this one is all corrected. Which github has the twrp device files used to compile twrp? I can't really find much for any device and alot of the cm device files are too cumbersome to use building twrp. I'm sure some will disagree with that last statement but it's just the truth.
[AT&T Samsung Galaxy Note I717] bigbiff:
Yeah, I just maintain my own combined usually because of finding stuff. But for AOSP roms point of view it's easier for them when dealing with multiple devices in the same class to combine multiple settings into common trees.

You can look for quicyatt on TeamWin github to see my old device configs. Check your kernel config to make sure UMS is enabled in the msm8660 kernel from cm.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm almost 110% complete! Things are working great so now I'm gonna add otg support for those who use it. I have all the mounts setup properly & got rid of the extra mount but I believe that it was a storage area for storing TWRP settings so I may add it back or users can just store them elsewhere. I mean recovery is awesome but "most" people don't spend much time in recovery. Lol They wouldn't need a phone if that was the case. :good:

Edit: Is the vibrate aspect something hard to get working? I forgot that it doesn't work, not a big deal to me tho but the option is there so it would be nice if it worked too.
[AT&T Samsung Galaxy Note I717] bigbiff:
Currently we are using sysfs to set it. Can you do this from the command line? I am trying to find how the sysfs is set.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm not really following you with the command line 100%. I went to the twrp irc last night but it was kind of late & Dees_Troy asked me to come back this morning to chat about the vibrations. My source is up & 1000% running great from a fresh build using cm11 msm8660-common kernel & the rest of cm11 device trees as well. My source again so you're not searching for it. I have built this several within my build environment so it looks like you should be G2G.
[AT&T Samsung Galaxy Note I717] bigbiff:
Looks like this is where it's pulling it from: https://github.com/omnirom/android_bootable_recovery/blob/android-4.4/minuitwrp/events.c#L117

I am guessing if you can find out what VIBRATOR_TIMEOUT_FILE should be set to, you can set it in BoardCommonConfig.mk.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Ok I'll check it out. I'll let you know what I find. Thank you.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
The path was missing as well as the vibrator.ko file and the script for init.recovery. At any rate everything seems to be up to par on my end. I have some feedback so far and folks seem to be delighted. Here are the device files you would need to fork. Most of them have additions to incorporate twrp.

Kernel

quincy-common

quincyatt

qcom-common

msm8660-common
[AT&T Samsung Galaxy Note I717] bigbiff:
I am going to try to build it in the omni tree.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Sounds great man! You should not have any issues. I've cleaned my source and built it several times now. Thanks for explaining that vibration stuff to me also.
[AT&T Samsung Galaxy Note I717] bigbiff:
Hmm, am i missing something or I don't see where you have the TWRP flags?
[AT&T Samsung Galaxy Note I717] developweb:
[quote name="developweb" post=51271716]Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?

No it was not. I've been waiting on more feedback from the update or any of my twrp builds. Now that I'm aware of it, I'll look into that so we can get it official in Bigbiffs twrp thread. I think it's close enough for him to release it as an official but this is my personal feelings. It'll be a couple days maybe before I get back to it since I've spent the last week concentrating on this, it's time for me to move on to other things for a moment.

Just copying our discussion from the unofficial quincyatt twrp thread.

Edit: fixed in latest. Thanks.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
These are just the last commits I made so you'll have to dig deeper. What are you trying to do, add the commits into twrp source? If so you can pick the last commits from quincy-common & qcom-common. The msm8660-common will need a few more commits to be picked. 4 to be precise starting with the oldest first. These could be cleaned up & moved around a bit but I haven't had the time to do so yet.

Here Here & Here
[AT&T Samsung Galaxy Note I717] bigbiff:
I am just trying to build the device in omni, but you removed the TWRP config settings?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm not sure what you think is missing? The quincy devices have been commonized and all my files are on/in my github account, that's why I linked them all. Have you browsed thru my git at all or have you just looked at the commits I posted before? Most of the twrp additions are in the msm8660-common device file. I don't have omni source on my pc currently. My old pc just can't handle much more than what I already do unfortunately.
[AT&T Samsung Galaxy Note I717] :
2.7.0.0: Restore of backup failed, returning to 2.6.0.0 and restoring works. :confused:
[AT&T Samsung Galaxy Note I717] disconnecktie:
I have heard of an issue before where old recovery backups wouldn't work with the new versions of the recovery. Does making a new backup and restoring it seem to work OK with 2.7? If it does maybe make a titanium backup of the apps and data from the ROM you want to restore to, flash the 2.7 recovery, flash the ROM and set it up, and then make a fresh backup with the new recovery. This is simply a workaround until maybe a solution can be found for the old backups not wanting to restore.
[AT&T Samsung Galaxy Note I717] :
Well, the steps I were this:

1. Flash TWRP 2.7.0.0 from CWM 6.0.4.4

2. Boot into TWRP 2.7.0.0

3. Make Backup

4. Flash P0llution's patch (kernel borked Phone app)

5. Reboot into TWRP 2.7.0.0

6. Restore

7. Instantly, somehow it reboots TWRP 2.7.0.0

When I flashed TWRP 2.6.0.0 the backup worked and restored properly. :confused::confused::confused:
[AT&T Samsung Galaxy Note I717] disconnecktie:
Hmmm and there was no error output in the terminal window while you were restoring. A log would help a lot to figure out this problem.
[AT&T Samsung Galaxy Note I717] developweb:
Pollutions ROM patch borked my phone as well when flashed with 2.7 enhanced and 2.7.beta from gimmeitorilltell and backup could not be restored effectively from 2.7 enhanced but could from 2.7 beta. Individual video patch flashes fine as well. Which scenario would you like a log for. I'll have to charge up again to test. Lol.
[AT&T Samsung Galaxy Note I717] disconnecktie:
So the enhanced version couldn't restore the backups but gimme's could?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Both versions are mine. Enhanced is with working vibrator. I can restore from any of them but I don't have any older backups.
[AT&T Samsung Galaxy Note I717] bigbiff:
Working on fixing it now with gimmeitorilltell.
[AT&T Samsung Galaxy Note I717] bigbiff:
I can't find the TWRP board settings. It looks like they all have one branch but I didn't see them at all. Sorry can you point me to the correct board file?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm afraid that it's going to take more than just the board settings for twrp to mount and flash properly running kitkat. I can try and isolate my work into one device source but it will have to be in the msm8660-common source. I see no way to get past editing the fstab.qcom for this to function. Give me a bit and I'll cleanup and isolate things the best I can.
[AT&T Samsung Galaxy Note I717] developweb:
http://xdaforums.com/showthread.php?p=51320428

is a link to logs in the other thread. ROM being backed up was candykat with sweetener applied. Device is an SGH-i717d (telus). Hope these help or shed some light as to why beta works on my device.
[AT&T Samsung Galaxy Note I717] weedolo9y:
This recovery will not install any suggestions
[AT&T Samsung Galaxy Note I717] disconnecktie:
Unzip it and use the app called flashify to flash just the img
[AT&T Samsung Galaxy Note I717] x111:
hello,

is any plan to add an awesome feature lock recovery by password ?

like it was done in PhilZ Touch - 6.47.4 : Recovery LOCK, F2FS
[AT&T Samsung Galaxy Note I717] bigbiff:
Here is our current stance: http://teamw.in/securetwrp

However, we would code review anyone who submits this feature to Omni Gerrit to allow this to happen. My time is short and I am working on other features currently.
[AT&T Samsung Galaxy Note I717] mocoyombiflash:
i've flash the odin flashable version but it gets black screen when booting into recovery i'm 4.1.2 MD3
[AT&T Samsung Galaxy Note I717] bigbiff:
I have been waiting forever for help to get this going again on i717. Anyone else out there that can help with TWRP? I haven't had this phone since note 2.
[AT&T Samsung Galaxy Note I717] developweb:
What recovery do you use now? Are you on stock or custom ROM? Exactly where do you need to start? The "everything" thread is a great place to start. Plenty of folks on here willing to help.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] bigbiff:
:silly:

I meant someone to help me port recovery to the newer firmware since I do not have the device. Guess you didn't realize I am OP?
[AT&T Samsung Galaxy Note I717] developweb:
Yes. Silly me, I didn't read the name, just the post. I'm using gimmeitorilltell's version of TWRP and it has no issues for me on i717?

http://xdaforums.com/showthread.php?p=51194722

So I believe it's already been ported/built for i717? But I also see you've been involved with gimmeitorilltell so I'm misunderstanding.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] bigbiff:
You mind testing an official version for me? He has limited time for testing.
[AT&T Samsung Galaxy Note I717] bmunday:
state of F2FS support?

I am unable to mount either /data or /cache formatted to f2fs with TWRP 2.7.1.0.

No one is asking about it? It must be butter for everyone...

Validus 6.1 for note has a kernel from AD5GB that attempts to support f2fs.

Anybody successful?
[AT&T Samsung Galaxy Note I717] dparrothead1:
Don't mean to hijack this thread or be disrespectful, but if you use 2.7.0.....you shouldn't have any problems.
[AT&T Samsung Galaxy Note I717] developweb:
I can try some tests later in the week if required. I have limited experience so you will need to let me know "specifically" what you want me to do/test and how. I can then post back my experience and/or logs if it will help.

2.7.0.0 is actually the version of gimmeitorilltell's that I'm presently using and the buttons vibrate. ;) I haven't tried the latest as of yet as it was geared to f2fs and was undergoing development for new ROMs/kernels that had not been released at the time. I had stopped trying new versions, as this one had made me a very happy camper. .

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] bmunday:
maybe i'll try to revert. [MENTION=3798079]dparrothead1[/MENTION] - are you confirming mounting f2fs /cache and or /data on i717 with 2.7.0.x? That'd be good news... Although my understanding re: gimmieitorilltell's 2.7.1.0 was the same.. laying the platform for kernel drops. BTW, are you using f2fs under Validus 6.1, with their custom Uber?
[AT&T Samsung Galaxy Note I717] dparrothead1:
No, I don't use f2f. And I don't know who built the TWRP, but I got it from TWRP official site on Goo on advice from AD5GB. BTW, he builds the Validus ROM for the i717.
[AT&T Samsung Galaxy Note I717] Helios909:
I don't know if anyone else is having these issues, but with 2.7.1.0 I have tried flashing the ZIP, and downloading the TAR with ODIN and as soon as this is flashed, I get a continuous bootloop and cannot even get into recovery. With 2.7.0.0 both the ZIP and the TAR work and I can boot into recovery, but TWRP doesn't function properly - it can't restore as it seems to reboot TWRP, it can't wipe data as it does the same thing, and it fails installing ZIPs. The only thing it can do is MAKE a backup. For now I have gone back to 2.6.0.0 and 2.5.0.0 and to install newer 4.4.3+ ROMs I flash CWM. Anyone have a solution to this? I tried someone's suggestion to flash the stock samsung recovery and do a wipe/reset with it, and then put TWRP back on - but it had no effect.
[AT&T Samsung Galaxy Note I717] Helios909:
Just to note, I installed gimmeitorilltell's version of 2.7.1.0 and it works perfectly. Guess he's got it figured out.
[AT&T Samsung Galaxy Note I717] bigbiff:
Just not part of the official build process.
[AT&T Samsung Galaxy Note I717] developweb:
Finally tried. I received the same results as Helios909 with a boot loop. (Panicking) :eek: . Flashed working recovery via Odin :sly:. Reflashed gimmeitorilltell's version 2.7.0.0. :D

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] bigbiff:
Yes, I still would need to make the test build for you to try...
[AT&T Samsung Galaxy Note I717] developweb:
No worries.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] skyungjae:
2.7 & 2.8 have been giving me boot loop issues regardless of install method.

Edit: I flashed 2.6 via Odin and zip installed gimmeitorilltell's 2.8, and it works fine.

Hmmm... I'm curious what's causing my issue.
[AT&T Samsung Galaxy Note I717] youngunix:
Okay, it seems that everyone (myself included) is having issues with TWRP causing infinite boot-loops.

ISSUE = "caused the boot-loop"

First, flashed TWRP 2.8.0.0 using TWRP 2.7.0.0, $ISSUE.

Second, used odin to flash CWM then flashed TWRP 2.8.0.0, $ISSUE.

Third, did the same thing but this time I flashed TWRP 2.7.1.0, $ISSUE.

Fourth, flashed both TWRP 2.7.1.0 & 2.8.0.0 using Odin, $ISSUE.

I don't know exactly what's the problem with the latest TWRP but hope it gets fixed.
[AT&T Samsung Galaxy Note I717] bigbiff:
You will have to use the unofficial until (or if ever) we get the updates from [MENTION=4779996]gimmeitorilltell[/MENTION] into the teamwin codebase.
[AT&T Samsung Galaxy Note I717] egandt:
Verbose debugging and logging, how do I enable something like this

I'm encountering many-many issues flashing zips, for instance nothing happens, I'm sure that TWRP is hung somewhere, but I need a way to see what is happening, how do I enable verbose logging so that I can attempt to debug what is going wrong with the flash. In one case the flash of a 233meg zip (which tested fine) took 20+ minutes until I was forced to hard reset the phone, at which point System was corrupted as a result. Normally the first thing I'd do is enable verbose debugging and monitor what is happening, but after a number of Google searches I can not locate any way to enable such logging.

Thanks,

ERIC
[AT&T Samsung Galaxy Note I717] developweb:
Did you read the above posts. This is official TWRP. This does not work at present on quincyatt devices. It says to use gimmeitorilltell's version. If you indeed understood that and used that version then you are reporting your problems in the wrong forum thread. Just pointing this out because most people having problems are using the wrong versions of recovery not realizing there are different builds available. Just search for unofficial twrp quincyatt.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] bigbiff:
adb pull /tmp/recovery.log in TWRP
[AT&T Samsung Galaxy Note I717] javelinanddart:
We have the latest official TWRP!

https://twrp.me/devices/samsunggalaxynote1att.html

https://dl.twrp.me/quincyatt/

Personally tested by me and [MENTION=6034212]TeamAndroid14[/MENTION]

This should be 100% working and it also includes F2FS.

If you're theming, use 1080P Themes (just like [MENTION=4779996]gimmeitorilltell[/MENTION]'s Unofficial TWRP)

Enjoy guys!
[AT&T Samsung Galaxy Note I717] TeamAndroid14:
https://s.basketbuild.com/devs/z31s1g/800/
[AT&T Samsung Galaxy Note I717] developweb:
Is there a flashable zip?

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Not with the official but you can use an app like flashify or Rashr to flash it from your device.
[AT&T Samsung Galaxy Note I717] zacutesz:
Can i use this twrp for lenovo A6000+ device??
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
It's built and designed for the SGH-I717 Samsung quincyatt. If you have that device then you can use it.
[AT&T Samsung Galaxy Note I717] bigbiff:
There are a couple things you can do.

First I would install CWM restore your ROM, install twrp then backup in twrp. Then you can delete your old CWM backups.

Otherwise you can just install CWM when you need to restore certain backups, then flash over to twrp.

HTH
[AT&T Samsung Galaxy Note I717] wase4711:
thanks man, thats probably the best way to do it..

I don't see a CWM flashable zip anywhere; the ones I have found have dead links, except for that "touch" version, which screwed up my evo3d, so I avoid any touch CWM like the plague..

and, I am an all Mac house so Odin is a PITA for me
[AT&T Samsung Galaxy Note I717] bigbiff:
The touch version of CWM on the note hasn't given me any problems.
[AT&T Samsung Galaxy Note I717] th3g1z:
Just letting you know I have put the 5/23 release on three Notes so far and did a backup on all 3. I've restored that backup on one just to test and working well here. OnlyOne ROM flashed fine on two of the notes as did juggernaut aokp. Good job so far so good.

Thanks!

+1
[AT&T Samsung Galaxy Note I717] abduleo77:
Problem with accessing external sd card

Hi Guys,

First thing I would like to say is this recovery tool is way better than CWM and I am thoroughly enjoying using it because of the easy user interface.

The only issue I am having is accessing my sdcard. For some reason when I go to instal then navigate to my sdcard its empty. But when I go to my emmc I can view all the folders and files on the internal storage. So in order to flash anything I am having to move it to internal storage first and then flash.

I know its only a minor issue but for those out there that fill up their internal storage fast this can be an issue.
[AT&T Samsung Galaxy Note I717] ridikolous:
You have to select SD card from the mount menu
[AT&T Samsung Galaxy Note I717] 21productionz:
Awesome work guys I love it!

FJ pimped my pride
[AT&T Samsung Galaxy Note I717] Apo11on:
my File Manager inside TWRP cannot see the contents of SDCard or external_sd - both appear to be empty. I've tried to toggle Mount/Unmount setting for both on the mount page and reboot recovery, but it made no change...Would appreciate some insight how to fix this. Thread search didnt come up with anything useful
[AT&T Samsung Galaxy Note I717] StaticMatt:
Whichever SD card you decide to mount (internal or external) show up in emmc. Took me a few minutes to figure that out. Hopefully that can be fixed at a later date but works as it is for now.
[AT&T Samsung Galaxy Note I717] Apo11on:
Did some playing around with it, based on your suggestion. What I found out is that mutually exclusive Internal/External setting is not for mount - its the default location where the backups are created at.

The mount points are actually created by checking the checkboxes and you can mount both internal and external at the same time. If you do that, \sdcard is indeed mounted under \emmc like you said, and \external_sd is mounted under \sdc

Hope this saves time for other people

---------- Post added at 03:37 PM ---------- Previous post was at 03:30 PM ----------
[AT&T Samsung Galaxy Note I717] bigbiff:
I will update the OP to be more clear. Hopefully. :D

Also my md5 code has been submitted into baseline TWRP. I will add reboot to download mode and release a new update for testing soon. The md5 code should now allow apostrophes in the filename. :o
[AT&T Samsung Galaxy Note I717] StaticMatt:
And it does. Makes much more sense that way, thanks for pointing it out.
[AT&T Samsung Galaxy Note I717] Apo11on:
My Note reboots to recovery using different methods just fine. It works through the extended power menu in my rom (see signature), Goomanager, Quick Boot app and Rom Toolbox Pro. In fact, JRummy explicitly stated in his latest 5.0.2 release TWRP support has been added
[AT&T Samsung Galaxy Note I717] bigbiff:
LOL. Guess that's what I get for blanket paste from eyeballer. :rolleyes:

Removing now...
[AT&T Samsung Galaxy Note I717] OkNewMedia:
I cant find the zip files that i saved to my external sd card. Can someone point me in the right direction? If this has already been discussed, please forgive my inability to find it.
[AT&T Samsung Galaxy Note I717] bigbiff:
Please do the following:

1. Go to the Mount page

2. Make sure that the checkbox for External Storage is checked

3. Make sure to press "Using External Storage"

4. The Install page should now show your external SD Card.

If not please use adb and pull /tmp/recovery.log and post the output.
[AT&T Samsung Galaxy Note I717] bigbiff:
New release is out!

Check the OP for more information changelog and more!
[AT&T Samsung Galaxy Note I717] bigbiff:
I will be releasing a small update tonight that will be able to backup the EFS partition using TAR.
[AT&T Samsung Galaxy Note I717] bigbiff:
Dees_Troy is cooking up something awesome for TWRP

http://phota.me/AmnZ.jpg

:D
[AT&T Samsung Galaxy Note I717] cmart4:
Is there a setting to name a backup in TWRP or anything like that?

Is it safe to go into backups and rename the saved backup or will it become corrupted?

I only have 1 backup so far using TWRP and don't want to jack it up
[AT&T Samsung Galaxy Note I717] bigbiff:
You can rename the directory. Just don't use spaces or weird special characters. Don't rename the images however.
[AT&T Samsung Galaxy Note I717] gorillaz1:
Anyone know of any themes that work with the g-note resolution?
[AT&T Samsung Galaxy Note I717] wase4711:
curious as to why you would post this in a dev thread, dealing with recoveries?
[AT&T Samsung Galaxy Note I717] gorillaz1:
TWRP has themes captain. Didn't you know?
[AT&T Samsung Galaxy Note I717] wase4711:
this is true; I just never even considered messing with a theme for recovery..I do it all the time with roms, but, since I am only in recovery to flash, and I am used to the plain jane theme from years of CWM, I've never messed with it..
[AT&T Samsung Galaxy Note I717] gorillaz1:
It was easy on my t989. Just move a file to a folder. Just made it look sexy. But they are made per resolution.

Here is a link to see one.

http://rootzwiki.com/topic/25762-480x800-21-icscyan-system-style-theme/
[AT&T Samsung Galaxy Note I717] wase4711:
looks cool; if you find one that works on the Note, post it here, if you remember..
[AT&T Samsung Galaxy Note I717] gorillaz1:
Course I can't code but I link with the best of them. :-)
[AT&T Samsung Galaxy Note I717] ArborRes:
Thank you very much for the TWRP! It works flawlessly! :D
[AT&T Samsung Galaxy Note I717] bigbiff:
If you are good at resizing pics you could try and find 720x1280 themes and move everything up 80 pixels. We don't have a very common resolution.
[AT&T Samsung Galaxy Note I717] gorillaz1:
Ya there aren't a lot of themes I've found. So finding one for us is a pain.
[AT&T Samsung Galaxy Note I717] bigbiff:
TWRP 2.2 is out on goo manager and on the teamwin homepage. See OP for details!
[AT&T Samsung Galaxy Note I717] iakeco:
Wow, great update..
[AT&T Samsung Galaxy Note I717] iakeco:
Love how you can now create your own backup name
[AT&T Samsung Galaxy Note I717] slaydog:
Ability to give a custom name to backups is the greatest thing ever!

Thanks!
[AT&T Samsung Galaxy Note I717] flappjaxxx:
This 2.2 update right here is the best thing since pockets!

Feature request, next version can have pockets? :D

Great job bigbiff and TeamWin!!!
[AT&T Samsung Galaxy Note I717] MechaGen:
I'm having trouble flashing the official CM9 and got this response from Cyanogen himself.

Don't get me wrong. I love TWRP and it's fantastic integration with goomanager. I'll be back when it gets fixed.

Sent from G-Note