yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
TWRP Themes have changed a bit & if you use a them then you'll want to checkout this link.

THEMING TWRP THE NEW WAY!

What's new in 2.8.7.0

- Initial ground work for software drawn keyboard (_that)

- Fix handling of wiping internal storage on datamedia devices (xuefer)

- Allow DataManager to set and read values from the system properties (xuefer)

- Fix crash when taking screenshots on arm64 devices (xuefer)

- Fix error message after an ORS script completes (Dees_Troy)

- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)

- Add system read only option - more details below (Dees_Troy)

- Add resize2fs and GUI option to run resize2fs (Dees_Troy)

- Fix crash loop caused by empty lines in AOSP recovery command file (_that)

- Prevent duplicate page overlays such as multiple lock screens (mdmower)

System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.

resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.

This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.

THEMING?

USE 1080P THEMES
[AT&T Samsung Galaxy Note I717] patch_Adams:
Yeah!!
[AT&T Samsung Galaxy Note I717] elheffe:
This is working perfect! Damn I missed TWRP. So freaking sweet!!
[AT&T Samsung Galaxy Note I717] Liwais:
Works well except mount memory
[AT&T Samsung Galaxy Note I717] disconnecktie:
Mounting which partition? Anyone that finds an error or a bug should try posting the recovery log after said error. Don't post the entire log in a post but put it on pastebin or something similar. Having the logs greatly increases the likely hood the issue will be fixed. Thanks.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
What do you mean by mount memory? Where you add something from the pc to the sd card & it shows up on the internal when in twrp? The internal sd card mounts when connected to the pc, not the external sd. I don't know if that's how it's suppose to work or not. This is my first twrp attempt and I had to build it from scratch basically. Like Disconnecktie stated, a log may be helpful.
[AT&T Samsung Galaxy Note I717] developweb:
Great work. Missed TWRP. Just had to tick off my internal sd. Panicked when my partition wasn't visible with my ROMs to flash. LOL.
[AT&T Samsung Galaxy Note I717] Liwais:
I had in mind when're in rekaveri not mount the memory to your PC

Maybe this Problem just me, let me know
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
[AT&T Samsung Galaxy Note I717] skearton:
For some reason (most likely that I'm a dummy, or missed reading somewhere)

Recently my SD card took a poo, so I've been saving to internal memory.

I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.

THanks!
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
When you are in TWRP recovery are you selecting "Internal SDcard" or "MicroSD card"

Edit: Latest twrp recovery with vibrations enabled!
[AT&T Samsung Galaxy Note I717] developweb:
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?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
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.
[AT&T Samsung Galaxy Note I717] SgtTeabag:
Newest build is working g sweet gimme. Love how ya added the button vibrate too. So far I've done 3 full wipes/flashes and your twrp has been flawless thanks for bringing this to us gimme. :)
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.

Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
[AT&T Samsung Galaxy Note I717] developweb:
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
[AT&T Samsung Galaxy Note I717] developweb:
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm not sure that I understand what you're saying? The internal sd mounts to the pc once you go into twrp & mount it.

Best of luck to ya! I have restored my nandroid with twrp but not in my latest version. I'll give it a try this evening and see what happens on my end. I have not used the aroma installer because I personally would rather not use it. I just use the camera fix from Pollution since I don't have the screen flicker or any other issues with my phone.
[AT&T Samsung Galaxy Note I717] developweb:
As I suspected, after returning to 2.7 beta, my backup restores without issue. Enhanced wasn't quite ready for primetime I guess.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm not sure if you got an error trying to restore your nandroid our what. I just ran a backup and restored that one and a previous one from a couple days ago without any issues. Did it give you an error?
[AT&T Samsung Galaxy Note I717] developweb:
I'll get back when I can flash again. The error should occur with twrp 2.7 enhanced while restoring a backup made with beta if I'm correct. ( Is there a way pollution's patch can remain after factory reset, dalvik cache wipe, and cache wipe? ) I will not be applying any patch for the next test and I'll be checking that log carefully.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I just got wind that the camera has been fixed upstream so hopefully we don't need any fix. I noticed that this device has been finally brought up to cm11 source. Pollutions patch should remain after a factory reset
[AT&T Samsung Galaxy Note I717] developweb:
Retried without any patches:

http://www.developweb.ca/downloads/logs/recovery-backup-beta.log

http://www.developweb.ca/downloads/logs/recovery-after-restore-enhanced.log

Above resulted in boot loop. Rewiped cache and dalvik and that resulted in com.android.systemui has stopped.

http://www.developweb.ca/downloads/logs/recovery-after-failure.log

Above after reflashing beta version and restoring backup resulting in no errors.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'll post another build as soon as I get a chance to work on this. Hopefully tomorrow after I get the kids to school. I sincerely appreciate all your logs and testing, as it seems the other users are just tickled to be able to flash using twrp again. Lol I really want to get this perfected tho so please bare with me and keep up the testing?
[AT&T Samsung Galaxy Note I717] developweb:
Sure no problem. We need these things so development can move forward/keep up on our device. You and others can develop, I can test when I've got time and others can enjoy the efforts! ( ...it all started again with a certain sweetener pack that would not flash in cwm...... And now it flashes in TWRP)
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Absolutely! OP has latest build and I added a link for the older builds as well. You can also find the latest HERE version 8

And HERE is version 7 to try. I compiled both this morning to see which one worked correctly.
[AT&T Samsung Galaxy Note I717] skearton:
I click Install, then select SD card, and I have nothing there other than a folder titled TWRP. Maybe it flashed weird? If you have time for dumbed down instructions, it would be much appreciated. If my description is too vague, or you're out of time. I understand that too. :victory:
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
When you are mounted to your pc and place the Rom on your phone it actually goes to the internal storage. Give that a try, also let me know which build of twrp you're using? I would suggest trying version 8 first. I made a small storage swap in that one.
[AT&T Samsung Galaxy Note I717] skearton:
My USB port is goofy and doesnt like to sync to the PC, I bought a replacement but it causes ear piece issues... Lame, I know.

Anyways... I typically use my mobile browser to download, and then go to recovery to install zips with recovery. In recovery I am unable to see my downloads folder where I typically store my flashable zips.

Thanks again for your response.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Twrp should still find your download but I think you need to look in the internal storage section to find it. Maybe even move it to the root of your storage after you download it. Either way should work but I feel it is best to place flashables on the root part.
[AT&T Samsung Galaxy Note I717] Demmonnixx:
I end up with the same result and have ever since I first started using TWRP, maybe it's me but it will only locate root and external sd not internal storage etc... Not really a big issue as I download everything via pc and then move it over to my external sd and flash it.
[AT&T Samsung Galaxy Note I717] developweb:
Did you click on mount tab in TWRP and check the missing partition? Only two were checked off, so I just tick off the remaining one, touch back and voila, bobs your uncle.

---------- Post added at 03:28 PM ---------- Previous post was at 03:22 PM ----------

The TWRP on SD is the folder where you put your theme folder containing the ui.zip in your custom setup (optional). TWRP will create another folder wherever you save a backup to as well. So you could have multiple TWRP folders.
[AT&T Samsung Galaxy Note I717] developweb:
Version 8 backed up and restored with no issue, themes and button vibrate work, android secure is available for backup now. I thought there was an append date option to backup name before and that appears to be gone now though this is not an issue for me.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Hmm I thought the append date was there as well? I'll look into it again. I never done anything that should have removed it. I guess there's always that chance.
[AT&T Samsung Galaxy Note I717] developweb:
Is there a point in trying version 7? It would have to be later as I'm down to 30% battery and haven't received my power bank yet.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
No point in trying version 7 if 8 is working fine except the append date :good:
[AT&T Samsung Galaxy Note I717] Liwais:
As far as I understand there are no errors? Memory rekaveri mount to your PC right?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
It's working perfect for myself and others yes.
[AT&T Samsung Galaxy Note I717] developweb:
I haven't tested everything yet. One can only flash so much in a day, but what I have tried has worked perfect.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
That is totally understandable and I believe that we are very close to getting the official thread updated too. From my testing of Bigbiffs recovery, it seems that everything except the vibrations is working. This was sent privately so there are no links for his build yet.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
OP updated

I have posted twrp 2.7.0.0 v10 and this seems to have the twrp settings & backup locations in place. This will most likely be the last update for a while from me here as I feel it has been perfected! Enjoy this folks. HERE is the link as in the OP....
[AT&T Samsung Galaxy Note I717] Liwais:
Everything is good but as in the first version does not mount to the PC memory in rekaveri.

Maybe it's just me?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I have googled rekaveri and read about it but I still have no idea what it is? Basically I read that it's recovery that can mount usb otg to use a mouse? If I'm way off can you explain more about what it is & what it's purpose is so maybe I can try to make it work for users? Have you tried all my versions? I doubt any will work since I have no clue what we're talking about. HERE is version 8 if you didn't get a chance to try it.

EDIT: I think that's the way you're spelling "recovery"? "rekaveri"! You have to reboot into recovery & select "mount" & then select "Mount USB Storage" to make it mount to your pc. If you might be using USB 3.0 try a USB 2.0 maybe.
[AT&T Samsung Galaxy Note I717] Liwais:
That "Mount USB Storage" I did not mount the memory to your PC .(version 10)

Sorry for my bad english)
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
It mounts the internal storage partition to your pc when plugged into a USB cable. Have you checked to see if you are using a USB 3.0 plug? That's all I can think of which may not let twrp mount. What firmware are you running, can you show me a copy of your recovery log and pull the mounts from your phone? This will tell alot about what's going on with it.

To pull the mounts, plug your phone into the usb cable with adb debugging enabled and type:

adb pull /proc/mounts

You can copy & paste the output HERE, save it & send me the link. You can do the same thing with your mounts using a different hastebin.
[AT&T Samsung Galaxy Note I717] patch_Adams:
Gimme...will this support f2fs file systems? I am hoping to implement f2fs into a build soon.....
[AT&T Samsung Galaxy Note I717] disconnecktie:
A separate versions would probably have to be made to support that file system. Have you seen benchmarks for that file system? It isn't any better than ext4 from what I can tell.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm pretty sure f2fs is supported by twrp but I have no idea how to compile it to work. I would guess you would have to set the build up to make it run with the f2fs enabled. If you can find out more about it, I'd be glad to help get a build going that supported it sir.

This was all I found so far:

2.6.1.0

Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)

Initial support for f2fs file system formatting (Moto X)
[AT&T Samsung Galaxy Note I717] patch_Adams:
see this one maybe?? I am not real sure either...if this doesn't do the trick I can look into it farther...if I wait, I'll forget....

http://xdaforums.com/showpost.php?p=51680698&postcount=5297
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Haha I just found the same thing on another thread. It looks like that flag needs to be set is all. I'll compile one up for you to test out. I assume you'll need the rom to test it as well.
[AT&T Samsung Galaxy Note I717] patch_Adams:
Hey thanks! And yeah, it could be a week or better before I have a rom ready, so no rush.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
No problem! It's a boring rainy day here so the build is almost finished. I'll go ahead and uploaded it and link it in the op. You or anyone can test out at will.

EDIT: OP updated with f2fs support in the small link below main twrp link.
[AT&T Samsung Galaxy Note I717] Meurdar:
thank's for this gimmeitorilltell !! work's great have flashed a few KK rom's with it now and flawless
[AT&T Samsung Galaxy Note I717] patch_Adams:
Thanks for the special version! I have flashed it and it works just fine. F2fs it's proving to be a pain though I am getting closer (I think?)....lol
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Any time sir! Let me know if that version works once you get the kernel ready. I don't see any visible difference with the recoveries, only flashing a kernel with f2fs support will tell I guess.
[AT&T Samsung Galaxy Note I717] patch_Adams:
[MENTION=4779996]gimmeitorilltell[/MENTION] Good sir:

Will you check this package and see what I would need to do to make it work with i717?? Please and thanks!

http://d-h.st/xt2

NOBODY FLASH THIS FILE PLEASE
[AT&T Samsung Galaxy Note I717] rruleford:
Can I be nosey and ask what it is?
[AT&T Samsung Galaxy Note I717] desalesouche:
hi sir. it seem in your f2fs recovery there is no f2fs references in fstab.qcom.

is that normal ?

/dev/block/mmcblk0p26 /cache ext4 nosuid,nodev,barrier=1 wait,check

/dev/block/mmcblk0p25 /data ext4 nosuid,nodev,noatime,noauto_da_alloc,errors=panic wait,check,encryptable=footer,length=-16384

---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------

another f2fs twrp opened with kernel-tools kitchen.

for comparison purpose.
[AT&T Samsung Galaxy Note I717] patch_Adams:
hang on
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I am not really familiar with the f2fs but I would assume that you need to replace the mounts in your script with the ones for the I717. Will dig a bit more to see what I can find out for ya.

Can you link me an fstab that shows f2fs? All I done was add the script to the make file, I'm not aware of anything having to be added to the fstab. Maybe find something on github & I'd be glad to check it out & incorporate that into this build.
[AT&T Samsung Galaxy Note I717] desalesouche:
see here... https://github.com/PimpedKernel/and...mmit/d9dddc5e69f73c8b9538cf36b0d5952627ea31b5

and you can see here also it is helpfull i believe...

http://xdaforums.com/showpost.php?p=52020770&postcount=5560

my friend Broodplank manage thanks to that how to and adapting ...
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Thanks! I'm pretty sure that you will need everything that is currently ext4 changed over to f2fs except the recovery itself. I currently have the efs, system, cache, & data set to ext4. I'll compile twrp with everything as f2fs & another build with only the cache & data set. If you're compiling a rom with f2fs then the complete recovery needs the same support. Links will be posted as the builds complete. Are you all getting close to ready for flashing?

EDIT: TWRP with f2fs support in cache & data ONLY!!! I am also compiling one with FULL f2fs support.

NOTE: This is a TEST recovery for supporting F2FS ONLY!!! DO NOT attempt to flash just any rom with these types of recovery!!!

patch_Adams

desalesouche

I am assuming recovery or the kernel HAS to be built FIRST, hopefully it's the recovery? Lol
[AT&T Samsung Galaxy Note I717] patch_Adams:
HUGE Thanks for your contained work here sir!! I am sitting down to build now so I'll grab what you've got here and give this all a go...

:good:
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Sounds good just let me know &, by the way, HERE is twrp with FULL f2fs support as far as system, cache, data, & efs.

NOTICE: This is f2fs ONLY! It is for testing purpose for now!
[AT&T Samsung Galaxy Note I717] Polluti0n:
[MENTION=4779996]gimmeitorilltell[/MENTION]

Is it at all possible to disable the assert checker in twrp? I am trying to put something together that would let us flash s2 roms, and let s2 users flash note1 roms. The only issue im having is the assert checker in twrp/cwm. Of course I can delete the assert check in the updater-script, but I wanted to make something easier for the users that are uncomfortable with all that stuff.

Anyways let me know if thats possible, and thank you for everything you do for this community.

-Polluti0n
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I would assume it can be disabled but it would be problematic long term for users, allowing to flash "any" Rom that was on the sd card. I certainly don't want to be the cause of another's bricking of their phone. Let me look at the mount system on the s2 because that would be cause for a brick if the Rom was looking for different mounts than the recovery has set. What I'd the xda name for the s2 or a link to the device files please?
[AT&T Samsung Galaxy Note I717] rruleford:
I believe the s2 is hercules or the model is t989. You and pollution rock. I wish I had tge brains to do these type of things. Thanks again friends

---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------

That would be the tmobile version. Att is skyrocket not sure of model number
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Yeah it's hard to keep up with all the different variants sometimes. Lol
[AT&T Samsung Galaxy Note I717] Polluti0n:
Ya its the skyrocket(att) or Hercules (tmo). I already have gotten s2 roms running on my note, I just wanted to simplify it for the average user. As for the risks, I agreement it should not be something that's disabled all the time. I wonder of it's possible to make a script to temp turn off assert check. I know that a Dev named philz built a custom cwm that you can toggle assert checker (it's outdated).

Is there an assert check flag?

I think that twrp caches a copy of the phones build.prop on boot. If that is true, it would be easy to make a script to sed the ro.device entry.

Any help is greatly appreciated.

-Polluti0n

P.s. happy Easter