I'm having some trouble following the troubleshooting steps that are aimed at resolving this AHB_ROT error. Its one of those all consuming ventures that has my focus late into the night when I should be resting on my day off.
The number one frustration I'm experiencing is that this is an error that I've seen before. Not only that but it's a problem that I've resolved before on a prior version that I was able to get running. So retracing my steps I'm like "they had me add a line of text to that one XML" which is pretty much all I can recall. I can't say whether I remember if that was the solution to the problem, but I did leave a small breadcrumb. I saved a mock copy of the xml, probably thinking that I didn't want to add too much to the XML to the point where i didnt recognize what the original system generated XML looked like.
That XML for that revision was r2.182 and this new version is r22. I think what compelled me fix what wasn't broke in downloading this new version was my recent purchase of the Wii u pro controller. Figuring that it would be best to have everything updated for the same of compatibility.
In this revision I noticed that the XML was included in this version, furthermore, the system (app) removes any changes to the code upon startup. If I erase, move, or alter a line code that wasn't in there to begin with, it reverts the xml back to its initial state.
So what gives, well it appears to me that the new package pretty much comes with all thats needed to run the app. So two things stand out. IOS version and internet access. I'm running IOS24.32 updated sometime in December of 2014. Much can change in a few months so I'd like to know if its something that can be updated automatically through the Wii's direct connection to the internet.
I read somewhere in the op that the app can update itself, so I imagine that it would be necessary that homebrew can access the internet.
Main points
-discover which ios updates are necessary
-internet connection as a requirement
-whether something I've overlooked in the XML is causing my problem
-if there are similar cases to my problem that can be found in this thread
-references to other threads that I could read through.
[
http://www.hacksden.com/entry.php/27-A-basic-explanation-of-AHBPROT-and-MEMPROT]