really? guess i'm not gonna update then. just for safety.Heard a9lh v1 was better for the nand. All these reports of nand going faulty started with a9lh v2
Well it's not confirmed just some stuff that some other random people on here were trying to piece together ....
Those in the know strictly deny it has anything to do with it.
I don't have any problem with A9LH v.2 XD It even better than before![]()
Yeah, but it better Idk why, A9LH v1 was alway crashing with me (maybe because my crazy rom hack was to much) but with A9LH v2 Idk why, it stopped to crashWhat exactly is the difference between v2 and v1? Just bigger payloads?
you mean "people can't read instructions", because that makes no sense whatsoever.Heard a9lh v1 was better for the nand. All these reports of nand going faulty started with a9lh v2
It gives more space for payloads, so CFW in your NAND can be a thing, for example.What's v2 do?
Those were always a thing; V2 has nothing to do with itHeard a9lh v1 was better for the nand. All these reports of nand going faulty started with a9lh v2
Faulty NAND's are extremely unlikely and all cases are results of hardware failure unrelated to A9LH. There's also cases where other bits of hardware not related to the NAND fail, causing issues as well.Heard a9lh v1 was better for the nand. All these reports of nand going faulty started with a9lh v2
Don't do that unless you want to brick.And you should just be able to re-run SafeA9LHInstaller with the files from A9LH1 to downgrade safely. .
If you want to go back to v1 use this version:WARNING: the stage1 binaries which can be used with 2.0 are mutually incompatible with the ones usable with 1.x. Using old stage1s with 2.0, or new stage1s with 1.x WILL LEAD TO AN UNRECOVERABLE BRICK. As of now, both delebile's and my own fork of A9LH have been updated for this. DON'T USE pre-made stage payload bins found randomly on the internet (Plailect's guide will be updated for this).