Submitter Tester Themer Veteran
  • Content count

  • Joined

  • Last visited

Community Reputation

390 Excellent

About vec1phyr

  • Rank
    The Vaudevillian Veteran
  • Birthday 11/24/95

Profile Information

  • Gender
  • Location
  • Interests
    Certified IT/CyberSecurity || iOS Theme designer || System Adminstrator of Linux-based systems
  • iDevice
    iPhone 6
  • Firmware
  • OS
    OS X El Capitan

Contact Methods

  • Website URL

Recent Profile Visitors

10.7k profile views
  1. Latest versions of iTunes have broken 25PP as well as quite a few other jailbreaking tools. I'd recommend looking for an alternative form of jailbreaking
  2. As Tyler said, try kicking out of recovery. If iTunes is returning that it needs a restore, it means it detected an unrecoverable booting error so you will have to restore unfortunately :/
  3. Widget

    Working good on this end, using Xen HTML set as a BG Widget
  4. I haven't done much hackish lately but I can write you up a kickass Microsoft Access database :D

  5. I'm not sure if you intentionally made a WinPE USB or anything, but what I'd do is rebuild your USB if you can. As for the filesystem question, most USBs and some DVDs will just show the filesystem instead of having a proper autorun execution. I find disabling autorun to be more secure anyways, give you a chance to see what you're about to execute.
  6. This has only ever happened to me when flashing a copy of Windows 7 installer that uses a custom Windows 8.1/10 Setup from someone who modified it for cracked use. Is that a possible thing that could've occurred on the device before? Also, I'd roll 64 like Erwinn said. Especially if the CPU has that instruction set available. Run this command via cmd.exe (as admin) except point the filepath to the boot.wim on the DVD/USB and reply with the output please dism /Get-WimInfo /WimFile:E:\sources\install.wim /index:1
  7. Here's my finalized build. I plan to put a smallish M2 NVMe as Rype suggested. Or at least a Samsung 960 EVO 250GB
  8. Hey guys! I just wanted to touch base on a subject that's been circulating due to some very upsetting events. I'm not sure if you're aware at the time of reading this but insanelyi's days are numbered. Sull no longer has the time, passion or energy to continue working/maintaining this site anymore as life has caught up with him. I cannot be upset with him as you shouldn't be either. This was very much bound to happen as it will with all of us, with that being said, it's time for us to step up. We currently have TWO OPTIONS with what we can do right now. 1) Try and get a price out of Boss I may have left this out earlier but he mentioned selling insanelyi and we'd like to keep that within our inner circle. Normally we'd keep this private but he hasn't given us a proper price and it's most likely gonna be an admin, platinum member or a staff. All other potential buyers could risk how the site is run and if they even bother keeping the site. 2) Begin migration now. This is a WORST CASE SCENARIO. This would be if Boss sets a number too high for anyone, we would be left with no other choice but to move into other websites that could potentially work as a substitute. We're working hard to make sure this doesn't happen but if this does happen, we're planning to create a new site for everyone to migrate to that should be at least be mostly similar to what you're used to here at insanelyi. This new site would take place at PLEASE hold onto that link until further notice. This will be most likely where we end up. I understand it'll definitely not be the same, or if it even works out, but it's what we have to work with if things go south. Again, we're doing our best to avoid this. If you have any questions, feedback, thoughts or simply something to say regarding everything, leave a reply. I really hope we don't lose insanelyi, we have such a wonderful community built up here and I really hope we can continue this legacy. Thank you for reading.
  9. Getting the password for Windows after the drive has been written zeros throughout would be redundant. I'm not jabbing at you (not on purpose at least) but usually I'd figure all pass recov tools would be needed on a drive that isn't wiped.
  10. Currently doing some bts designing and setups so will be ready for the worst-case scenario. If you find insanelyi is permanently down one day, you may find us here (depending on if anyone actually reads or sees this.)

    1. TylerDurden


      I read it 😉

  11. Hello ladies and gentlemen. I'm posting this in regards to my PC build I'm currently getting together. First off is that my budget is locked to $1,200 (and that's pushing my boundary right now) and I already have everything together besides the SSD. My question is that I have about $100 to spend on SSDs and I don't want one that's gonna fail out on me quickly. Should I bother getting one now? Or should I wait until I have more to spend on SSD (I can roll M.2 NVMe PCI) Current specs: Intel Core i7 6700K Cooler Master 212 Evo CPU Cooling Gigabyte Z270-Gaming K7 LGA1151 DDR4 Motherboard 16GB DDR4-3000 EVGA GeForce GTX 1060 SC 3GB Phanteks Eclipse P400S TG WD Blue 1TB 7200RPM (or Seagate Barracuda 2TB 7200RPM based on a Newegg sale today) Feel free to give me any solid advice on the parts I also chose. Thanks!
  12. Offline Windows 7 Password Changer doesn't always work though. Utilman.exe method is the best since you get system level privileges.
  13. Give my old tutorial a try. Should allow you to wipe all of your tweaks, removing their preferences is a manual task but can also be done via iCleaner
  14. NOTE: I will be fixing up this tutorial in a few minutes to add corresponding colors and some images. A fix for conditional hard-loops on semi-tethered jailbreaks, this will NOT work with all boot-loops and is considered a risky process. There is about a 25% chance your device will freeze during the erase process. If so, you must update to the latest iTunes First off: How do you know you're hard boot-looped? Well, it's simply put for semi-untethered jailbreaks. You're unable to reboot into an unjailbroken state. Typically this leads to an infinite Apple logo on your screen. So, you managed to hard boot-loop your device. It's a rather challenging task to accomplish in today's world of jail breaking. However, tweak developers who often create bootstraps and other system-level essentials often don't collaborate before releasing or their work simply doesn't work together until the damage is done. Next thing you know, you're looped. Now, when I say conditional. I mean A LOT must be considered and must be determined before following through with this: 1. Is the latest firmware or a current firmware that's signed still jailbreakable? If so, restore using iTunes and this guide is no longer relevant to you. 2. While you are hard-looped, can the device communicate via SSH, FTP, iTunes (without DFU/Recovery mode)? If so, attempt to repair using SSH, FTP and then skip this guide. (If you cannot use those and are able to access iTunes. MAKE A BACKUP and then continue) 3. While you are hard-looped, can you load Substrateless (Booting without Cydia Substrate by holding Volume Up during the jailbreak process.) successfully? If so, it's tweak related and does not need a reset of any kind. Remove the affecting tweak. 4. If all else fails, futurerestore is often not an option as all eligible firmwares for that utility require to be jailbroken during it's process and all of said firmwares must be able to boot and be jailbroken. This cannot be done on these firmwares. 5. While you are hard-looped, does the device respond to plugging and unplugging an active USB connection? (Vibration from connection), this should also result in messages and other notifications showing up. This is essential to the process. 6. Was FindMyiPhone setup with this device? If so, you may continue below This leaves you with a VERY RISKY but effective option that can leave you in one or two statuses. Safe or Sorry. I CANNOT STRESS THIS ENOUGH. THIS IS A LAST CASE OPTION. I CLAIM ZERO RESPONSIBILITY IN A FROZEN RESTORE LOADING SCREEN. IF THIS OCCURS, YOU MUST RESTORE WITH ITUNES. PERFORMING THIS TASK CLAIMS THAT YOU ACCEPT THESE RISKS AND YOUR JAILBREAK CAN BE LOST AS WELL AS YOUR DATA BEING TOTALLY WIPED USING THIS METHOD. All you need: - A computer - USB cable - iFunbox, iExplorer, or iTools (any utility that grants access to userland file system) - iFile.ipa - Cydia Now, with that out of the way. Let's get started! 1. Log into and select Find iPhone 2. If your device meets all of these conditions above. Your device should show up. If not. Refer to conditions above again. 3. Select your device and press "Erase iPhone" (yes, that does EXACTLY what it says.) 4. Follow the prompts it provides. If successful, your device should reboot into what looks like an upgrade screen. 5. DURING THIS PROCESS, you should make sure it's plugged in to avoid power-loss. If the screen remains unresponsive for over 30 minutes. You must restore via iTunes. 6. If everything goes well, you will see the setup screen for iPhone. Set it up like you've done before. 7. You'll be greeted to your home screen which seems to still include all of your jailbroken applications (none of them will open at this point) 8. Reinstall your jailbreak entry point for your device. (Yalu102, Pangu9.3.3) 9. Rejailbreak. You'll notice afterwards that Cydia opens but is still broken. 10. Side load iFile.ipa using a Cydia Impactor. (Plug in your iPhone, drag the IPA onto Cydia Impactor, sign in, wait.) 11. Open iFile to make sure it works. 12. Open iFunbox/iExplorer/iTools. 13. Navigate to the "User File System" and open "Books". Drop the "lib" folder into "Books" 14. In iFile. Navigate to /var/mobile/Media/Books. Copy/Cut the lib folder 15. Navigate to /var and paste lib into that folder. 16. Force close Cydia and reopen it. 17. Upgrade EVERYTHING it prompts, you'll receive errors but this is normal. DONE. Your jailbreak is now functional again. All of your apps and tweaks should be able to be installed once again. If you have any questions, comments, feedback or concerns. Please voice them below with a reply! Thanks! ~V
  15. To my current understanding, 16.10 changes the way it reads the operating system. I haven't had the time to actually attempt to look into this but seeing this is an issue with the binary files used to read the operating systems so I must say that we have to wait for an update (unlikely, last update was 14.04). If BURG is VERY important to you, downgrade to 16.04.