Edit: Check this whole first post, because I have made some additional entries concerning failures and potential cures to things. I will update when my current encryption test is complete.
For the short version see the tldr at the bottom.
I have been trying different combinations of things all day in my last ditch attempt to get encryption working without needing to flash my original firmware back on from odin, since I hate the thought of how long it takes and what could go wrong.
The secret that I have worked out today is I install TWRP, wipe everything out, factory reset, wipe etc. Then install the rom, in my case it was my TWRP backup of my original firmware installed and then later CM11 M12, then immediately after flashing, reboot to download mode and flash the stock recovery image (I had to get a guide and use my linux VPS to turn the extracted recovery.img into a .tar.md5 and use that for flashing my original recovery. Then boot to recovery (now the genuine original recovery) and perform a factory reset. Then boot the phone up and the encryption works. Right now CM11 is at 38% encryption! Just before I started this off, I also had 100% success with encryption using my TWRP backup of a stock firmware install, using this same method. Once it is encrypted I will flash TWRP back on here as I did before and it should be good.
My theory (I am too burned out to test it at this point, I just want my phone working...) is that the issue is not whether you have TWRP installed, but whether the final factory reset (before booting up phone for usage) is performed by an official recovery or a third party recovery. So I bet it would work if you perform the factory reset and then immediately flash TWRP back on there and then boot up and perform the encryption.
Plus, in theory since I am using CM11 encryption, TWRP should be able to access /data which means I can keep this encryption and flash what ever rom I want using TWRP and upon booting it "should" just work. I tested this once before when I lucked out and got encryption working on some rom (I forget now which it was) but I was able to do a wipe with TWRP and install a different rom and the encryption still worked, still booted up fine.
Do you have any thoughts on this topic? Maybe I am reinventing the wheel...? I have not seen any of this referenced in any of the text or video guides I have been checking out. So I thought I would share this just in case. It might work for other samsung phones too.
STAND BY. The encryption did not work and I am trying a slight modification that is also proceeding. I am 19% on encrypting CM10.2. This time I did the usual TWRP wipes and then once wiped, Immediate flash of the original stock recovery (no OS install yet), then perform a factory reset and then flash TWRP again. Then I installed CM10.2 and skipped through the setup wizard and went straight to setting up encryption. Where usually it fails, it is actually performing the encryption. I have hopes that since the factory reset from the stock firmware's recovery was performed BEFORE the OS install, that it should... should work this time. I have a feeling the prior one failed because of doing a factory reset from one rom's recovery on a different rom's OS. So doing the factory reset before the OS install might be what will make it work. I will update soon.
Edit: It worked flawlessly... Booted up, authenticated, everything is fine. I am now running the same test with CM11 (M12) Also, I am not sure if this will work, but once I performed the final factory reset via the stock recovery (before re-flashing TWRP to begin OS install) I made a backup. My hope is that instead of reflashing and re-flashing back and forth, that the backup I made will have everything ready as if I had done a stock recovery based factory reset. If I decide to ditch CM11 I will test this theory out. I should also mention that the last test I mentioned with CM10.2 worked even though TWRP was presently still installed. So the presence of the stock recovery is not required, rather it is the factory reset from a stock rom being the final step required before the OS ROM install process.
Edit: There seems to be an issue with CM11. Twice now it has failed to work on CM11. I will try CM12 next, using my backup of a freshly official factory reset. If it fails I will do the whole process on 12 and see if it works and report back.
Edit: CM12 encryption by using the TWRP backup of a freshly factory reset (via stock recovery) failed. I am in the process of waiting for the first initial boot and setup wizard to complete of my second attempt at CM12 encryption via the full final step of actual stock recovery factory reset before CM12 installation via TWRP that is flashed after the stock recovery factory reset. I will update if this works. If it works and boots up correctly while encrypted, then it means a TWRP of a stock recovery factory reset is not adequate to replicate a true factory reset and the developers of TWRP should be made aware of this so they can enhance their own factory reset feature to allow encryption to work. If it doesn't work then there is something definitely wrong with CM11 and CM12 since both the stock firmware and CM10.2 encrypt using this full factory reset method. Stay tuned, wizard just came on screen...
Edit: Ok, weird... this time the encryption process has begun, whereas using my TWRP backup that was made after doing the stock factory reset did not get to this point, although the percentage counter started from 100% and counting... Right now the encryption is at 146% completed. That is very odd... I will report back if the encryption process actually ends up with a successfully booting phone or not, since CM11 failed at the booting phase. Before I save this edit, ne thing I am noticing is the progress percentage is going up rather fast compared to any other ROM. Right now it is at 177% and right now it is 179%, now it is 183% and I type fast... Stay tuned.
Edit: The encryption process worked and rebooted, asked for authentication and came up, however upon unlocking verious apps like CM bug reporter and whisper and others crash sometimes resulting in a OS loading screen and a fresh unlock needing to be performed.
tldr: When installing ANY rom, you need to wipe the file systems with TWRP or other similar recovery, then flash your stock firmware's recovery image (not the whole firmware, just the recovery, which means you need to extract the recovery.img from your flash file using 7zip and then follow these instructions: http://www.w0lfdroid.com/2013/04/android-how-to-convert-img-recovery-to.html to create a .tar.md5 file that odin can use to flash your recovery rom. (load odin, click AP or PDA and set your recovery tar.md5 and untick the two boxes that are always on by default. I use Odin v3.09). Then after you have wiped the file systems with TWRP (format data, then wipe the other mount points) then with your stock recovery perform a factory reset. Then flash TWRP or what ever custom recovery you use and just install your ROM, no other formatting or anything else, just install (not restore). Then the encryption will work, assuming there are no bugs in the rom that prevent it working on your handset, as seen on my handset with CM11 and the weird bugs with apps crashing on CM12.
So my recommendation is that the developer(s) of TWRP change the way they perform the factory reset, to emulate the actual process that a stock recovery uses, so that you do not need to keep reflashing your recovery images over and over when you need a fresh install.
Notes: CM11 M12 fails to boot, post successful encryption process, while CM12 nightly (18th March 2015) has bugs with apps crashing after successful bootup post encryption.
I have verified all this twice since. It is the stock recovery factory format that is needed before you install your ROM. I hope this helps the other people that I have seen having encryption problems.
Related
Hello all,
My S3 currently has TWRP 2.7.0.1 recovery and CM11 installed. It was also previously encrypted.
Recently the gapps on my S3 have completely stopped working. New accounts cannot be added and the programs immediately crash upon starting. Deleting the app-data for these has had no effect.
While I can decrypt the phone for regular use, I cannot do the same in recovery to reinstall gapps. Consequentially, it appears that the best option would be to wipe out everything to get rid of the encryption. Unfortunately, it seems that you cannot flash a new ROM over an encrypted partition via recovery. I have reached the conclusion that Odin should be used to reformat everything.
Is this a correct understanding? And how would I go about doing this safely?
First, backup everything you can. Then try a factory reset. If this doesnt help, choose format data from recovery. (Formatting /data will wipe the internal sd card).
If all else fails, then go for the odin flash. From what I have seen though the factory reset or format should be sufficient.
Be very careful using Odin of you have a 4.3 or newer bootloader. You don't want to flash an incorrect modern or bootloader which can brick your phone.
Very true, always be careful of this. I dont usually mention it for Odin flashes though because Odin will recognize the versions and will refuse to flash. Its usually flashing via recovery that is the most dangerous in my experience. (But I have seen odin flashes go bad too, its kind of rare, but always be careful with what youre doing.)
Some how I have screwed up my partitions. I was able to Odin to stock lollipop and I can get into download and recovery. However I cannot flash anything at all at this point. In TWRP when I try to flash a custom ROM, Kernel or even the lastest TWRP version, all that happens is recovery restarts. This all started when I tried to flash SlimLP ROM. It flashed fine but would only bootloop when I tried to start phone. So I wiped everything and reflashed lollipop AllianceROM. The phone started okay but I got some error message about the UID. I noticed right away that ALL my text messages which should have been wiped were intact. The phone was running really, really slow and I had continual issues installing apps from the Playstore and TiBu. I decided to try another ROM and again wiped everything, flashed and rebooted. Again text messages were intact. I believe it's my system and/or data partition that is messed up but I am not sure. I'm not knowledgable about any of this so I really need some help here.
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
tx_dbs_tx said:
From the sound of things you don't need a pit file to repartition your phone. Don't attempt to mess with that. I would do what was suggested above. Just make sure you do the "factory reset" several times then wipe data several times. also go into advanced wipe and wipe everything EXCEPT your external micro-sd card several times as well. then odin flash the stock BOB7 rom tar. That should do it.
Click to expand...
Click to collapse
samep said:
Factory reset in TWRP a few times and power down. Pull the battery, reinstall and Odin stock OB7 again. Watch the auto boot, it should go into stock recovery noted only by a android with wavy antennas and small progress bar that may not even fill before booting the ROM.
If you don't see that, factory reset, power down and try again. Make sure stock is OK before trying another flash. Also, use internal memory to flash from. Almost sounds like your sdcard is encrypted?
BTW, I don't know of any available PIT file for our phone. I thought it may be included in the stock tar but who knows for sure? One thing I learned a while back on the older phones going from CM to stock, flash twice to correct the partitions. Maybe it still works? -different recoveries; flash, reboot recovery, flash again. Those ROMs included recovery.
Before going to Alliance, factory reset.
Click to expand...
Click to collapse
Thank you both. I did just what you guys suggested and it worked out! Thank you again!
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.
jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....
Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.
same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again
Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!
this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair
I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...
Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!
People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.
zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups
neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me
neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)
I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.
Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.
Hey guys, could one of you please tell me how to do a complete wipe?
I'm having so many problems with TWRP at the moment, and so I want to nuke the partitions in hope that it'll fix it. I've tried using the fastboot format commands for system, data & cache. I've also tried to wipe the recovery, but it gives me the error "Formatting is not supported for filesystem with type ' ' ". So for that I just use format erase and flash the recovery again.
The only other partitions I know of are the boot and bootloader, but I don't want to touch them if at all possible.
The problem I'm having and why I want to wipe sotrage is that if I install sultan's LinageOS (haven't tested with other ROMs yet), TWRP ****s the bed and will make the device undetectable from ADB, (while TWRP is still running though), and if I then try to go into TWRP again, it'll hang, crash, and somehow make the ROM think its just been freshly installed again (data partition corruption?), and it'll do that every time I reboot from then on. The only way to fix this is to wipe the phone as I mentioned earlier, but it will always get stuck again when I re-flash the ROM.
Also, another unusual thing is that when I boot the phone, it has the old boot splash from my previous ROM when loading recovery or for the first few seconds when loading a ROM. So that might be having an effect on the problems I'm having, and what makes me believe that wiping will help.
Any help would be greatly appreciated. (Sorry if it's a bit incoherent)
TL;DR: Flash TWRP, load TWRP, flash ROM, flash Gapps, load ROM, restart, load TWRP, TWRP hangs, crashes, and breaks ROM. ROM will keep being broken until full wipe. Also weird thing where I have old boot splash from old ROM.
Edit: Ended up bricking my phone, and using the unbrick tool to fix that. It seems that it was what I was looking for, where it wiped the phone completely. I'll have to see if that actually fixes my problem.
TWRP 3.1.xx is having this problem, believe the fix is to use the blue_spark 3.1.xx version or the nethunter 3.0.4-1 version, both found here on the forums somewhere
I tried Factory Reseting my phone earlier today through Recovery, It said everything was reset so I restarted my phone. My phone is now in a bootloop, it vibrates, shows the "erasing" screen, then the hidden LED light turns on and the screen goes black, then the phone does that forever. It's on the erasing screen for about 3 seconds before restarting. Trying to enter Recovery Mode just sends me back to the "erasing" screen.
Any help would be wonderful!
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
victorhbm15 said:
Were you completely stock? On a ROM? With custom recovery?
What steps did you use? Wipe data and factory reset? Did you wipe the cache partition?
If you were on stock, I would suggest you tried to wipe again. You could try to do it with ADB and fastboot if you are not able to access the recovery (which I don't think would happen if you're completely stock).
If you were not on stock or with a custom recovery, the easiest way to solve this would be to reinstall the ROM you were using.
Click to expand...
Click to collapse
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Dubstepwolf123 said:
I was Stock ROM with root, I edited the build.prop file and rebooted the device, that’s when the issues began. I had TWRP installed and restored my backup of my phone from before I made any changed, this didn’t help anything (I was stuck on the “Your device is unlocked” screen). I restored the stock recovery and I now have the original recovery installed. Finally after some well timed button presses I am no able to access the Stock Recover, however if I try to side load a working ROM onto my phone it shows the percentage of the side load but then fails this:”
E:footer is wrong
I:verify_file returned 1
E:Signature verification failed
E:error 21
W:failed to read uncrypt status: No such file or directory
“
It’s a little late now, so I’ll be back tomorrow to do some more research.
Click to expand...
Click to collapse
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
victorhbm15 said:
Did you factory reset already?
I don't think you can sideload a ROM with stock recovery.
Don't try to flash anything with stock recovery, better go back to TWRP.
PD: If when going to TWRP you slid the "swipe to allow modifications", that's what caused the bootloop, as it made modifications to the partitions. Or so I read on a guide here.
Click to expand...
Click to collapse
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Dubstepwolf123 said:
Thinking back again I guess it didn’t make much sense trying to flash a rom through Stock Recovery. Yes I did Wipe the Cache partition and then I Wiped data/factory reset through Stock recovery, all I did in TWRP was restore everything from the backup.
*An hour later*
So I was able to get TWRP installed again. Unfortunately when I try to restore from a backup I made with TWRP before messing with anything it restores with no errors or warnings, but when I reboot the system it gets stuck on the "Your device is unlocked and cannot be trusted" screen. Probably sounding stupid saying this, but shouldn't a restore of a backup be straight forward?
*Another hour later*
I was able to get ToxycOS 3.0 installed and running, but personally I don't like it and want to go to Motorola's Software... now I just need to fix whats wrong with my restore.
Click to expand...
Click to collapse
Why not fastboot install stock firmware?
Isn't that available, here?
pizza_pablo said:
Why not fastboot install stock firmware?
Isn't that available, here?
Click to expand...
Click to collapse
In the end I was able to install the Stock Moto Z2 Play firmware... I hate when people don't include the fix in their answers for other people, but currently I am unable to post any links because they are on a different device. I'll get back later with the links.