• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easycreate your account today.

    Already a member? Log in here to hide this message and start participating.

Beginner 5x5x5, 7x7x7 etc. solution: only 8 algorithms

Joined
Oct 5, 2019
Messages
7
Location
Ohio
I solve mainly for fun and relaxation, not competition, and I enjoy the process more than memorizing algorithms. Not finding much online for beginners/casual cubers with large cubes, I combined techniques from various sources into a method that works for me! (Odd-sized nxnxn puzzles only.)

The goal of this guide: fewest algorithms to memorize. Not speed. (Since some of the 8 algorithms can be mirrored or otherwise adapted in simple ways, there are technically more than 8, but only 8 to memorize.) Disclaimer: I tried to include picture/supercubes, but that step I have not tested as heavily as the rest.

Casual hobbyist solvers of big cubes must be rare indeed, but I hope someone out there finds this helpful!

Here is my one-page PDF how-to, with standard notation, explanatory text, diagrams, and mnemonics. Revised occasionally.
https://adamsimmersive.com/apps/cubing/7x7x7-cube-beginner-solution

Improvement ideas are welcomed!

7x7x7-Cube-Solution-Adams-Immersive.png
 
Hi Morgan,

Well, if the goal is to truly go with the fewest (core) algorithms, in this video, I show how to use variations of the Niklas commutator to solve the entire 3x3x3 (and meddle with pieces of big cubes towards the end). (Orienting the corners and edges requires knowing which "direction" to apply the Nilkas (and to apply 2 Niklas), but it's still just essentially one core alg.)

Also, I am kind of curious how your method would handle a simple edge-pairing case like this. (The generating algorithm is LONG, but that's how to use two applications of the Niklas commutator... from my video.)
 
Cool! Using one algorithm in multiple ways is very appealing.

My method avoids that edge-pairing in step 3 (“If any edges are in place already but flipped, displace those early”) and it’s never come up for me, but I suspect that failing to clear those early would still leave you in a situation you could get out of with the “as needed” second algorithm in step 3, ( U2 xR ) × 5. I won’t swear to it though!
 
Back
Top