Submitter Tester Themer Veteran
  • Content count

  • Joined

  • Last visited

Everything posted by vec1phyr

  1. 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!
  2. 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
  3. 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 :/
  4. Widget

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

  6. 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.
  7. 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
  8. Here's my finalized build. I plan to put a smallish M2 NVMe as Rype suggested. Or at least a Samsung 960 EVO 250GB
  9. 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.
  10. 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.
  11. 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 😉

  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.
  16. UPDATE 2.1: Fixed the images. UPDATE 2: N-Muenich has included Xenial (16.04) packages on his repository. A note has been included on Step 2 of the BURG chapter. The rest of the tutorial should still be followed. UPDATE 1: Fixed the sed command code since the old code no longer works. NOTE: Ubuntu 16.10 fails to recognize the filesystem with BURG. If you can get it to run, please inform me with instructions as I'm unable to work. Hello everyone! Today I'd like to share my knowledge on how to properly install BURG for Ubuntu 15.10. Now, normally this is a VERY simple process but with this tutorial I shall provide corresponding pieces of information that should allow you to install without error and pack it in so it DOESN'T fail like it did with me after upgrading. Common questions I'm expecting: Why is it any different on 15.10 compared to; let's say 14.04 or even 15.04? To be fair, it really isn't THAT much different. The problem being is setting up the repositories and also making sure BURG is locked in since most people are likely to skip VERY important steps that may cause some booting issues and you'll find yourself in grub rescue mode. This tutorial is being made to make sure your experience with installing BURG on Ubuntu 15.10 is secure and thorough. What do you need? - Ubuntu 15.10 x Windows/Mac/Whatever other OS you have. (if you have anything below 15.04, this tutorial is NOT necessary.) - Root privileges - Patience with Terminal. - Backups of your information (in-case things go awry) WARNING: I am not responsible if you can no longer boot your computer after following this tutorial, with these instructions; you SHOULD have your bootloader properly installed. However, the bootloader may not install very properly (which is why I have you install it under TWO instances to be certain) so if you can no longer boot. I will include a rescue method on how to return to GRUB2, if the damage is deeper than that. You may need to run another method of fixing your disk (the only other inlaying cause) **If you see this, screenshots are STILL pending. For I am writing this off a bit fast** If you are not on Ubuntu, boot into it now. BURG Step 1) Open Terminal and enter in the following commands to add in the repositories we'll be using: sudo add-apt-repository ppa:n-muench/burg -y && sudo add-apt-repository ppa:danielrichter2007/grub-customizer -y && sudo add-apt-repository ppa:ingalex/super-boot-manager -y Step 2) Before you run apt-get update, We need to fix some 404 errors. Go to Settings > Software & Updates and go to "Other Software". Step 3) From there, find the repository that has "n-muench" in it's name. Select it and press Edit. Change the Distribution to trusty as seen below NOTE: This step can be skipped if you're on 16.04, I don't believe they are backported on 15.10 and lower. NOTE 2: If you're on 16.10, instead of 'trusty', use 'xenial' (Yes, I know this is the ingalex repo I'm modifying. I accidently screenshotted the wrong one. HOWEVER, the result is the same for n-muench) Step 4) Next is the ingalex repo. Open your Terminal and run this command: 15.10 sudo sh -c "sed -i 's/wily/raring/g' /etc/apt/sources.list.d/ingalex-ubuntu-super-boot-manager-wily.list" 16.04 sudo sh -c "sed -i 's/xenial/raring/g' /etc/apt/sources.list.d/ingalex-ubuntu-super-boot-manager-xenial.list" Step 5) Once complete, now run these commands to install our needed software: sudo apt-get update -qq && sudo apt-get install burg burg-themes grub-customizer super-boot-manager && sudo apt-get install -f During the install, you'll be prompted many times with some bootloader stuff. It's mostly important but the default settings should do fine so simply press Enter through it all (unless you're concerned, then read carefully) Step 6) We now have BURG on our system, time to do the fun stuff. Run these commands below: sudo burg-install "/dev/sda" sudo update-burg NOTE: The first command's "/dev/sda" value can vary depending on your computer. It may also be (hd0) or even /dev/sdb, The best way to find out is through GParted or through this command: sudo fdisk -l The drive you're aiming for is your primary boot drive. It will normally ask you to install it into your Ubuntu installation (mine being /dev/sda5) but you should DEFINITELY install it directly onto your drive rather than your Ubuntu partition, in order to alleviate any data failures that can render your computer unbootable without recovery disks. Step 7) Now we may test to see if your computer has installed BURG properly by running this command: sudo burg-emu You should see a nice GUI listing all of your installed OS (don't worry, if you're not a fan of how it looks, just wait until the later steps when we get to themes.) If you see some sort of command-line, this means that something did not install correctly and you should reattempt the installation process. If this isn't alleviated, skip to the next step. This step will include our double-check to make sure it's installed DIRECTLY into your computer. NOTE: If you see error: unknown command `vmenu'. This isn't a fatal error it seems. I haven't had an issue every time I install BURG, if any issues arise regarding this. Please note in a response. Congratulations! You've installed BURG! Now onto the customization. GRUB-CUSTOMIZER Step 1) Now we will use grub-customizer to customize, clean up old-kernels for Ubuntu and make sure the bootloader is properly installed. Run this command: sudo grub-customizer It will prompt you saying "BURG found! Do you want to configure BURG instead of grub2?". Select Yes. Step 2) It will scan for your installed OS and boot up the tool. Feel free to remove anything off of this list as you see fit. Step 3) To make sure it's 100% installed, go to File > Install to MBR... Now it will come up with a prompt with the primary drive already listed. Select Ok and it should prompt saying "Installation successful." NOTE: In the "General Settings", you can use this tab to change the timeout before it boots the default entry as well as change the default entry upon starting your computer. I recommend leaving the Appearance Settings alone, for this tab has caused nothing but problems with the bootloader. I also recommend to not remove the Recovery Mode/Rescue Mode entries if you expect any future issues SUPER-BOOT-MANAGER Step 1) Run this command in Terminal: sudo super-boot-manager A window with a few managers will pop up (you can use these to further the customization of your computer. We only need one for this tutorial.) Select "burg-manager" Step 2) From here, you can install themes, install BURG with ease just like grub-customizer, as well as other little things to make BURG much better. I don't recommend messing with anything you don't understand. If you want to know what something does, don't be afraid to ask below! RESTORING GRUB2 So, what happens if you cannot boot? Well damn. That's a shame, but don't fret! Usually this is solvable by doing the following. What you'll need: - A copy of Ubuntu burned to a disk or extracted onto a USB. - Some moar patience. Step 1) Put in your USB/Disc and boot up your computer. Step 2) **THIS PART VARIES PER USER** Press F2, F1 or Esc to access your BIOS settings. (OR any of the F1-F15 keys that may allow you to access your boot devices/boot order, if you're able to do this. Boot off of whatever medium you're using to boot the Live disk.) Step 3) Set your boot-order so your HDD comes AFTER your disc and USB. (Set this back to normal after you restore grub2), save your BIOS settings and continue booting with a purple screen. Please wait until you're greeted with an Ubuntu splash screen. Step 4) Once Ubuntu boots up, a pop-up will appear saying "Try Ubuntu" and "Install Ubuntu". Select "Try Ubuntu". Step 5) You'll now be booted onto a temporary copy of Ubuntu. Open Terminal and run sudo fdisk -l Step 6) This will list all of your partitions, look for anything that would resemble your copy of Linux. Now run these commands below: NOTE: sdX means sda, sdb, sdc and onward. sdXY resembles sda1, sda2, sda4 and onward. sudo mount /dev/sdXY /mnt sudo mount --bind /dev /mnt/dev && sudo mount --bind /dev/pts /mnt/dev/pts && sudo mount --bind /proc /mnt/proc && sudo mount --bind /sys /mnt/sys sudo chroot /mnt This will bind your directories to your mounted drive and set root to your mounted drive. Step 7) Now we can reinstall grub2. Run these commands: grub-install /dev/sdX && grub-install --recheck /dev/sdX update-grub Step 8) GRUB should have installed without any error. Now run these commands: exit && sudo umount /mnt/sys && sudo umount /mnt/proc && sudo umount /mnt/dev/pts && sudo umount /mnt/dev && sudo umount /mnt reboot You're computer will have rebooted and you should have been greeted with GRUB2 once again! That's all folks! If you have any questions, comments, feedback or anything for me. Reply below! Thanks for reading! ~v
  17. If you're fully updated to 9.3.3 and if you have Sprint like me, this one should work great, otherwise you need to find someone with your specific carrier who is willing to send you a system file of theirs, or restore. Not sure why you were playing around in the root partition anyways with your hands near the Delete key Always be extraordinarily careful in there.
  18. I'll send over my Unknown.bundle in a second. I'm almost certain it's carrier based but it's worth a shot.
  19. I'm planning to continue theming again probably upon iOS10 jailbreak. I'm sort of dry on ideas but by then, I'll have something :)

    1. iHomer


      why did you stop?

      Your themes are @Boss

    2. vec1phyr


      Lack of time, ideas, motivation and audience. I'm returning to it soon but for now, I'm working strictly on OS right now lol.

  20. I really try to in-order to use my computer for all of my needs which brews down to graphics, video-creation, music, gaming, and coding (for 3DS, iOS and Android) so I basically need all three OS for my preferred setup
  21. I'll end up on Sierra with my next machine. Current laptop most likely cannot handle it so my next desktop will most likely have it's parts set for a HacPro triple-boot setup. (Gaming desktop with the ability to run Mac? Hell yeah)
  22. Description: This is Solux9. A theme crafted on the best platform for iOS theming to bring you an exquisite set of icons, complete UI, wallpapers and plenty more. While a very simple theme, this theme took plenty of time to make in-order to perfect each and every piece to match each other with more room to add even more changes to make this theme better, perfection may not exist but a community's voice can help this theme get pretty close. I'm very open to icon requests and feedback. Please email me or tweet to me at @vec1phyr or Thank you very much for supporting this theme! Screenshots by a dedicated beta tester, E-rwinn. Thanks! Special thanks to the beta testers: TheHuskinator E-rwinn iHomer afyRanger Changelog: 1.0: - Initial Release Special Note: Please consider a small donation to me if you like the them or at least buy it in the future, all proceeds go straight to my son's expenses Thanks! Download: Icons com.vec1phyr.solux9.deb UI com.vec1phyr.solux9-ui.deb Wallpapers com.vec1phyr.solux9-iphonewp.deb Screenshots:
  23. Solux9 has been released! :) Get it while it's hot.

  24. This is very true. I've jailbroken/tether booted well over a hundred times using DFU/Pwned DFU. WITH A BROKEN BUTTON. It's a matter of mastering the process. The best way to do it is to hold home and power at Apple logo until the screen goes black, hold home and power for 3 seconds and then release the power button until iTunes recognizes the device
  25. Welcome to insanelyi!