yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] disconnecktie:
I don't think you have to disable the assert checks in the recovery. Just remove the assert get.prop from the build prop. Then it won't check to the recovery to see if it is the correct device or not. I believe that cm builds that way by default.
[AT&T Samsung Galaxy Note I717] Polluti0n:
The assert get.prop is in the updater-script. I can easily remove it, but I want to make a simple way for users to flash s2 roms.

Below is what I'm trying to accomplish:

Users flash s2 rom>flash gapps>flash rom patch>enjoy.

I just don't want the user to have to edit rom package before flash.

-Pollution
[AT&T Samsung Galaxy Note I717] disconnecktie:
I understand your goal which is why I suggested the build prop edit versus building a new recovery. You can change the source to make the build prop work for other devices or you can make a separate prop you throw into the zip after every build. Then the end user never has to touch it. At least then you get the result you want and that is the end user not having to mess with the zip.
[AT&T Samsung Galaxy Note I717] Polluti0n:
Thank you so much for your advice, however I'm not quite sure I understand. I'm not actually building the s2 roms. I just want to make a patch that would allow users to flash any cm11 based s2 rom to there note.
[AT&T Samsung Galaxy Note I717] disconnecktie:
I suppose someone with knowledge of build props, the necessary changes from the s2 to the note, and some scripting knowledge could make a patch that edits the parts of the build prop that need it. If you or someone else knew all the changes needed to be done I'm sure you could find a Dev that knows how to make a script that searches the build prop and makes the changes through a flashable zip.
[AT&T Samsung Galaxy Note I717] Polluti0n:
Well that's what the patches I have already made do. Along with many other fixes, and custom kernels. My patches are all done up in a nice little aroma install that allows the user to pick which kernel and what fixes to apply to 4.4 roms. It also allows users from the tmobile note to install 4.4 att roms. Many users on these forums already use my patch.

The issue is that twrp has a default.prop that I don't know how to edit, unless I build twrp from source. The issue then would be assert checker permanently disabled (dangerous).

The solution: Remove the assert check from updater-script in s2 rom before flash

Problem: Most users don't wanna do that or feel uncomfortable modifying stuff they don't understand.

Idea: flashable zip that changes ro.product.device=SGH-I717 to ro.product.device=SGH-I727 using SED command. The recovery would also have to run an init.d script that GREP/SED ro.product.device=SGH-I717. That way every time TWRP starts it makes sure that ro.product.device=SGH-I717 in default.prop.

This way the user would flash like this prep.zip>rom>gapps>patch.zip. And twrp would be set back to its default default.prop the next time its booted.

At this point this is hypothetical because I don't know if TWRP can run an init.d script, nor do I know if it can run a script to SED the default.prop

-Polluti0n
[AT&T Samsung Galaxy Note I717] disconnecktie:
I know you'll disagree but if people are uncomfortable changing one line in the build prop they probably shouldn't be flashing a recovery capable of allowing them to flash basically any ROM to their phone. This is just asking for people to brick. I understand that you're trying to make it easier but it just sounds like a bad idea to me. I still don't see why a separate build prop or ROM zip couldnt be made and posted in the threads that want to have this option.
[AT&T Samsung Galaxy Note I717] desalesouche:
https://github.com/LiquidSmooth/and...mmit/332d5b1d8fe7eefc5d986d332eedb7198b2620e1

https://github.com/LiquidSmooth/android_system_vold/commit/24e69beef9fbfcfbaa2744d56b136c10a464ba4b
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I have the latest 2.7.0.1 working but I don't see the f2fs options like in my other devices. Also I have not uploaded the file yet since I'm working so much lately.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Twrp with "F2FS" support has been added to the updated OP! This is the latest 2.7.1.0 and everything seems to be working "EXCEPT" that silly ole vibration! Oh well that's fine without it until I can fix her up. Patch_adams & Polluti0n if you're still working with the f2fs kernel then this should work for ya. Still trying to get this official but I'm certain it will be very very soon!
[AT&T Samsung Galaxy Note I717] patch_Adams:
I haven't been working on android in some time :/ I do know that ad5gb has a kernel that is f2fs compatible. Someone would have to build it from source. I feel retirement coming on for me guys.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Ahh man are you moving on to another device or is life just getting in the way for ya? Anyhow, whichever it may be, we will all miss you around these parts. I'll let

AD5GB know about his if he has a kernel compiled already. Thanks for the heads up.
[AT&T Samsung Galaxy Note I717] patch_Adams:
Just life. I'm always busy and don't have the time. I used to come on here everyday now I'm lucky if once a week. I'll continue my roms on a monthly basis for now.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
New build on deck in the OP! Check it out and let me know? I have flashed this & flashed gapps with it but not much else. I do not use this device much any longer.

Edit: vibrator does not work in the latest build and I'm aware of this. I'll try N fix that when I get time but for now I wanted to share the latest.
[AT&T Samsung Galaxy Note I717] Gil81:
Flashed it and it looked good..but won't boot system..keeps going back to recovery..lol
[AT&T Samsung Galaxy Note I717] dzee206:
after flashing 2.8.0.0 turn off the device and back on, I noticed when you reboot after flashing, it ends in a loop going back to recovery...
[AT&T Samsung Galaxy Note I717] disconnecktie:
Try flashing the rom again without wiping anything.
[AT&T Samsung Galaxy Note I717] Gil81:
no go..lol. still stuck in recovery. i dont get it. im going to pull a log and see if i notice errors.

---------- Post added at 03:39 PM ---------- Previous post was at 02:57 PM ----------

Had to Odin twrp 2.7.

Don't know what went wrong...and of course I thought I had another version of twrp on my sdcard...and didn't..lol. Oh well...all is well now.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
The 2.7 twrp is still on my afh account. I'll look into this more. Guess I should have at least tried flashing a rom.
[AT&T Samsung Galaxy Note I717] Gil81:
I had ur 2.7 version on my laptop..just not my device..lol.

All I did was clear cache and dalvik..flash 2.8 and reboot recovery. It just would not boot system back up. Kept going back to 2.8 recovery. I tried shutting off device and a battery pull. Then dirty flashed current ROM over itself and reboot. Still booted back to twrp. But after I odin'd 2.7 it booted right back to current ROM.

Not sure if that helps and I couldn't get a log..sorry.

Thx for the ongoing support you are giving our old beloved note.:good:
[AT&T Samsung Galaxy Note I717] dzee206:
2.8.0.0 flashed for me I just get stuck in a loop when I reboot after flashing a rom... its just that once 2.8.0.0 is flashed and you try to reboot system its sends the device into a loop back to recovery.
[AT&T Samsung Galaxy Note I717] Helios909:
Interestingly I came from version 2.7.1.0 (your version) as TWRP versions since 2.6.1.0 have not worked properly on my device, and I installed without a problem, booted into my OS and all was good. Then I rebooted into recovery and was just checking out the new changes, and when I rebooted again, the phone would not boot into anything but recovery or download mode. I tried a variety of things, but no matter what it would only boot into TWRP. Finally the only thing that worked was flashing to CWM, and then flashing back to TWRP 2.6.1.0 and now it booted back into the OS again. Don't know what's going on with that - but it suddenly ocurred to me that I lost 2.7.1.0 in the process, and I don't have a backup. I'm hesitant to install 2.8.0.0 again - where can I find the last version? Regardless, thank you for your great work as your version of TWRP has been the only thing that has worked for my 4.4.4 versions other than CWM.

Thanks!

---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------

Yup, I had the same problem except I didn't even flash a new ROM. Does anyone have a version of gimmeitorilltell's 2.7.1.0 for quincyatt? I didn't make a backup. But what got me out of the loop was flashing CWM, then flashing TWRP 2.6.1.0.

---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------

Same. Does anyone have a copy of 2.7.1.0 gimmeitorilltell's TWRP still?
[AT&T Samsung Galaxy Note I717] disconnecktie:
Those of you with a boot loop try doing a fastboot erase cache and see if that fixes it. That seems to help for the m7 at least.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Here is TWRP_2.7.1.0 Even better look at the post BELOW!! 2.8 is working now. Sorry for any troubles with my previous build.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Alright folks I fixed booting into the rom after installing twrp 2.8.0.0! I've booted several times into the rom and flashed my Beanstalk 4.4.4065 build from this recovery as well. It's now working minus that silly little vibrator but I think we can all live without that for some TWRP? Link is in the OP & remember the FIRST unusable 2.8 link read "no_vibrate" in the zip file, this one does NOT!! Enjoy :good:

Thank you buddy, the only thing is samsung does not have fastboot. We have to flash recovery with Odin or from a zip file. I know you've been an HTC guy forever & was unaware of this.
[AT&T Samsung Galaxy Note I717] disconnecktie:
I was afraid of that. I couldn't remember if it had fastboot or not.
[AT&T Samsung Galaxy Note I717] Gil81:
Thanks..2.8 working great.
[AT&T Samsung Galaxy Note I717] oscar the grouch:
just flashed this using cmr and phone wont boot to recovery or rom

---------- Post added at 07:27 PM ---------- Previous post was at 06:52 PM ----------

i flashed 2.7.1.0 after installing cmr via odin again and that worked.

Then i Flashed 2.8 on top of that. and i can get it back to the os but i cant boot into recovery the screen stays blank.

weird.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'm not sure what cmr is? cwm recovery?
[AT&T Samsung Galaxy Note I717] Gil81:
Make sure you are getting a good download. I can confirm that 2.8 is working fine on my device. I've flashed 4 or 5 Roms with it since yesturday
[AT&T Samsung Galaxy Note I717] oscar the grouch:
downloading a new copy now.

and cwmr is what i meant earlier.

EDIT:

Checked my MD5 sum this time and now its working. I must have gotten a bad download like you said. I think my home tower is a cause of a lot of my issues actually.
[AT&T Samsung Galaxy Note I717] Gil81:
Glad you have it working.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
2.8.1.0 Now Live

OP has been updated to 2.8.1.0, Enjoy!
[AT&T Samsung Galaxy Note I717] dzee206:
Coming from your TWRP_f2fs_2.7.0.0_test_v1 I get caught in a loop into recovery. If I flash cwm 6.0.4.7 and flash your 2.8.1.0 build things are fine up until i boot back into the new recovery, I get stuck in the loop again. Anyone else run into this issue as well?

Sent from my SGH-I717 powered by AOKP
[AT&T Samsung Galaxy Note I717] developweb:
I'm running on 2.8.0.0. I'll give 2.8.1.0 a try and get back tomorrow (I'm in the middle of a download ATM).

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] dzee206:
Thanks man but I just tried that as well and no dice, got the same results. I was only able to boot into the OS once and once back in 2.8.1.0 recovery it started looping again no matter what i did. I'll attach the recovery log in a bit since i can't on the xda mobile app, really hate that lol. Remove the ".txt" from the end hopefully it'll suffice as i can't get a log via adb since i never got around to replacing the one I have now that's damaged.

Sent from my SGH-I717 powered by AOKP
[AT&T Samsung Galaxy Note I717] dzee206:
Anybody try 2.8.1.0 and get different results from mine?

Sent from my Half Baked SGH-I717
[AT&T Samsung Galaxy Note I717] developweb:
Nope. Won't boot to system. Just loops back to recovery. Also theme directory is not working. ( or at least not the same ). My chosen theme does not display. This is a mute point as this recovery does not work either. 2.8.0.0 still works so back I go.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Thanks for the feedback folks. I found the same issue booting back into recovery time after time and not booting into the system. I'll look into this more and test better before I release again. 2.8.0.0 should be the best to use currently until I fix this issue. I'm trying to get things worked out for bigbiff to make it official so I really appreciate the help.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Alright folks I have been working on this some more & can boot into the system every time. I have NOT tried to flash any roms yet. Been really busy with life itself but this should be working, unlike the last release. Here ya are!
[AT&T Samsung Galaxy Note I717] dzee206:
Thanks man. Everything works now, no issues making/restoring a nand or flashing ROMs or even bootlooping. Haven't tried messing with the theme yet...

Sent from my SGH-I717 powered by AOKP
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Awesome! Thank you for the feedback. As I said I have not flashed any new builds with it. I'm gonna try to get this officialized with bigbiff but would love to have the vibrator working before that happens.
[AT&T Samsung Galaxy Note I717] Madmanguruman:
I wasn't able to get ADB going with this build. My old 2.7b1 build enumerates the ADB interface at VID 18d1, PID d001. This build was enumerating it at VID 18d1, PID d002 and I couldn't find a driver that would work. I'm also on Win8.1 so modifying .inf files won't work.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
TWRP_UNOFFICIAL_quincyatt_2.8.3.0

OP has been updated to the latest TWRP source recovery. I have flashed roms & ran nandroids. This DOES boot into the system unlike my last fail.

EDIT: You DO NOT HAVE TO USE THIS FOR 5.0!! So far I am able to flash 5.0 roms with my older twrp recoveries and I'm not 100% sure but I don't believe this is a MUST? Once we get a booting build for our device you will not have to flash superSU if it is not installed in the rom.zip. TWRP will advise & install if it is not present.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
2.8.4.0 in op

An update for TWRP to version 2.8.4.0
[AT&T Samsung Galaxy Note I717] Dannoid:
2.7.0.0 is able to restore.

2.8.4.0 shows no files on the internal SDcard.
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I believe that happened to me once and I had to pull the sdcard and reinsert it. You may not be able to use it tho, I'm not saying that you're wrong. I believe the build is going to be a little out of kilter until I get the sepolicies brought up to android 5.0
[AT&T Samsung Galaxy Note I717] tekweezle:
n/m
[AT&T Samsung Galaxy Note I717] bibo979:
Im trying to install this on my I717r and I keep getting the message E: signature verification failed

how do I install CWM img file in order to make this work?

EDIT:

GOT IT WORKING!!! Had to first flash CWM using odin 3.04 (odin 3.09 refused to make the recovery stick) and the tar file from http://theunlockr.com/2012/12/04/how-to-install-clockworkmod-recovery-on-the-att-galaxy-note-i717/

Then once I had CWM, I flashed twrp 2.8.4 from sd card with success! WOOT!

Now I got SlimFast (slimkat) 8.4 Rom and Twrp on my Canadian i717r! This is pretty sweet!
[AT&T Samsung Galaxy Note I717] bibo979:
twrp 2.8.4 recovery loop

It looks like I am stuck in a recovery loop as others have experienced on older versions of twrp.

I am on twrp version 2.8.4 using slimfast rom v8.4. The loop occurred right after I restarted into recovery using the power menu.

Now, no matter how I reboot phone it comes back to twrp.

Is there a temporary fix that can help me boot into my os?

EDIT:

whiping system and dlvik - no change

factory reset - no change

flashing new rom - no change

the only thing that got me out of the loop was flashing CWM recovery using odin

its a shame this recovery loop occurs... twrp is (in my oppinion) the best recovery... unfortunately I must use CWM until this issue gets fixed
[AT&T Samsung Galaxy Note I717] tekweezle:
Does reflashing the OS do anything? Wiping system and dalvik cache? Factory reset?

Sent from a Freedompop HTC Evo 4G
[AT&T Samsung Galaxy Note I717] developweb:
Could you use unofficial TWRP 2.8.0.0? I've had no problems with it. But really for the time you spend in recovery does it really matter? Latest TWRP didn't put me in a recovery loop however it wouldn't recognize my backup as a flashable zip (not very useful lol).

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
The 2.8.3.0 I believe it's my latest that works correctly. It may be 2.8.0.0 as [MENTION=5209903]developweb[/MENTION] mentioned.
[AT&T Samsung Galaxy Note I717] tekweezle:
similar thing happened to me on my Samsung Fascinate. Actually the bootloop caused me not to be able to get into any sort of recovery. Had to Odin back to Gingerbread and start again.
[AT&T Samsung Galaxy Note I717] TeamAndroid14:
If you cant get back into recovery, go into download mode, flash the twrp 2.6.0.0 img.tar ( https://goo.im/devs/OpenRecovery/sgh-i717/?page=1 )through ODIN, it will automatically go into recovery and then flash TWRP 2.8.3.0.

Hope this helps :)

-Cheers :good:
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
TWRP 2.8.7.0 Live in OP!!!

Folks we have the latest TWRP & we will have F2FS as soon as I build my next candy5 rom! HUGE thanks to [MENTION=5795145]javelinanddart[/MENTION] for throwing a hand in at getting these things working!!! Please find him and click on thanks at least once, he deserves it. F2FS has been compiled into this recovery but I'll rebuild it again since I forgot to add it into my kernel defconfig. Look for new & exciting things to come!
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
This is my latest build with F2FS fully enabled! TWRP_quincyatt_2.8.7.0
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
TWRP has changed a few things so if you use themes then try using "1920x1080" themes. This commit should explain it better. TWRP Commit
[AT&T Samsung Galaxy Note I717] developweb:
Well, I tried about a dozen themes in different sizes. The slider and slider-touch images do not appear to scale correctly in the old themes. This makes swipe to flash or unlock impossible. Until a custom theme is found that is not broken by the new scaling, I'll Just use the default theme. No problem.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I'll double check that I have that TW_THEME set in my source. If I didn't set it, then that would be the issue. I'll let ya know.

EDIT: I just checked & I do NOT have the new twrp theme flag in my source. I doubt it will help but I'll compile it with the flag set. I will link you the build to try since I have never themed twrp or any recovery as far as that goes. lol

And here ya go TWRP_quincyatt_TW_THEMES_flag_test.zip

ATTENTION: I have NOT flashed this myself but I am certain that [MENTION=5209903]developweb[/MENTION] can fix any issues if they arise. This is a TEST build ONLY!! Please let me know the outcome & if I need to try a different flag? I used

TW_THEME := portrait_hdpi

And the selections are as close as I could come I believe.

* watch_mdpi: 320x320
* portrait_mdpi: 480x800
* portrait_hdpi: 1080x1920
* landscape_mdpi: 800x480
* landscape_hdpi: 1920x1200
[AT&T Samsung Galaxy Note I717] developweb:
Solved:

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

Fixed all my theme issues. Thanks to all.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] TeamAndroid14:
I used this and it worked, download the "286X_v1_1080_play.zip"

https://s.basketbuild.com/devs/z31s1g/1080/TWRP 286X_v1

Make sure when you download it, go into your twrp folder and make a folder called "THEMES" transfer it to TWRP THEME folder and change it to "ui.zip " and boot into recovery. I.E "286X_v1_1080_play.zip" change it to "ui.zip"
[AT&T Samsung Galaxy Note I717] javelinanddart:
Looks like you guys resolved this while I was sleeping :)

Honestly portrait_mdpi is a batter scale, but the problem is it has to scale up, so everything would look blurry.

If you take a look here: https://github.com/omnirom/android_...ee32#diff-769f1f73894d78b973f294516db16861R88

https://github.com/CandyDevices/device_samsung_quincy-common/blob/c5.1/BoardConfigCommon.mk#L63

We're using the right flag as it is according to [MENTION=912474]Dees_Troy[/MENTION] with that commit

Anyone using a theme from now on just has to use a 1080p theme from now on so it'll scale the same way.
[MENTION=4779996]gimmeitorilltell[/MENTION], you might want to add this to the OP just to avoid questions like this in the future ;)
[AT&T Samsung Galaxy Note I717] tekweezle:
Can this be installed straight from TWRP 2.83? I tried but got a sysmap error message.
[AT&T Samsung Galaxy Note I717] developweb:
I flashed from 2.8.0.0 without issue.

Sent from my SAMSUNG-SGH-I717
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
Use the link in my OP. The one listed above is a test link ONLY. You can flash it from recovery yes.
[AT&T Samsung Galaxy Note I717] tekweezle:
Never mind, it was a user error caused by a bad download. I got it installed correctly.
[AT&T Samsung Galaxy Note I717] princewilson0410:
Will this work on the T-Mobile Galaxy Note?
[AT&T Samsung Galaxy Note I717] gimmeitorilltell:
I don't know for sure if it will or not. I know that it won't flash because it's set to validate your device first. If it doesn't find the sgh-I717 the flash will fail.
[AT&T Samsung Galaxy Note I717] jayinc11:
I want to flash this to my SG Note i717 ATT, it has CWM currently. But this version comes as a zip while Odin requires a different extension. How do I flash this ZIP format?
[AT&T Samsung Galaxy Note I717] vrpg:
Download twrp 2.8.7.0 quincyat. Zip
[8125, K-JAM, P4300, MDA Vario General] shantzg001:
I was told that arm_ce3 cab is to be installed on wizard, but there is no such cab available for 0.72RC1. I've downloaded all the files available for the same but could not find it. Please tell me which cab to use..
[8125, K-JAM, P4300, MDA Vario General] kei118:
If you have activesync, just use the exe installer

http://corecodec.org/frs/download.php/434/tcpmp.pocketpc.0.72RC1.exe

Otherwise for wizard I suggest you try the pocketpc.RCxxx.cab first
[Nexus 4 Q&A, Help & Troubleshooting] pulli23:
Well when I look at the advanced radio settings I keep getting "imei: unknown" status at my nexus 4. Together with baseband unkown and all mobile connectivity seems wrong. I am currently running the stock run and not updated anything or done anything (heck I took great effort to "relock" it when I unlocked it to FIX this. (On top of this: loading takes ages, sometimes refusing to load till battery level drops below 10%).

I've tried flashing android 4.4 (but this creates the soft-brick looping while starting android).

I've tried factory reset,

I've tried hard reset

And I've tried the manual resets by flashing 4.2.2 back on.

In all combinations

What can be done, and how can I start using my mobile phone as a PHONE again? Anything but asking for a warranty (as I sadly void It when I had to downgrade from 4.3 to 4.2 to fix a bug introduced in 4.3 that prevented deep sleep)
[Nexus 4 Q&A, Help & Troubleshooting] audit13:
From what I have read, you cannot run any rom that is newer than 4.2.2 if your phone has imei problems. The only way to fix the imei issue is to send it to LG.