..... WUT? Care to elaborate? A link perhaps? N3DS? O3DS? Region?I got it to work and had the same problem.
You need to rewrite the database for AM service to initiate
..... WUT? Care to elaborate? A link perhaps? N3DS? O3DS? Region?
You've still have me lost mate. I can' find what you're talking about.N3ds 10.3 usa. Downgraded 3 times couldn't get cfw only home brew. Updated back and fixed the database files (dbs trick) and downgraded. Once on 9.2 all was well
Using browserhax to setup CFW also did not work. It really seems to be system specific.No, My downgrade went off with almost no problems, only issue i had was rxtools kicking back out to either HBL or CTRBootManager, however all issues on that base were solved with a Nand unlink and format of the emunand and now everything works great, i haven't booted my sysnand one time since the day the downgrade came out
For anyone having rxtools or other cfw kicking back out, if you are using menuhax to do your initial cfw setup then that is your issue
Still no good. I'm just staying on 10.3 with menuhax setup for now, I'm so exhausted messing with this damn thingUpdate back to 10.3 and access the eshop once then try to downgrade
Still no good. I'm just staying on 10.3 with menuhax setup for now, I'm so exhausted messing with this damn thing
4.2, the latest. Reading through the thread leads me to believe I'll be in the same position. I'm honestly not interested in trying anymore, I'm just going to wait for something better. I've downgraded at least a dozen times now and I would rather not risk bricking on the next go... this is all still very new anyway.What sys updater are you using? Use @julian20 version found here.
https://gbatemp.net/threads/simple-guide-to-downgrading-your-3ds.407888/page-95#post-5923820
4.2, the latest. Reading through the thread leads me to believe I'll be in the same position. I'm honestly not interested in trying anymore, I'm just going to wait for something better. I've downgraded at least a dozen times now and I would rather not risk bricking on the next go... this is all still very new anyway.
We doesnt updated the sysupdater in Tuxsh and steveice10 versions. So 4.2b could also means tuxsh unsafe version4.2, the latest. Reading through the thread leads me to believe I'll be in the same position. I'm honestly not interested in trying anymore, I'm just going to wait for something better. I've downgraded at least a dozen times now and I would rather not risk bricking on the next go... this is all still very new anyway.