Ninebot Max Error Code 27: Difference between revisions
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
To temporarily fix error 27, hold down the brake and throttle on boot up and release once it beeps. | To temporarily fix error 27, hold down the brake and throttle on boot up and release once it beeps. | ||
Changing the serial number twice using a newer dAuth supported serial change method. | Changing the serial number twice using a newer dAuth-supported serial change method. | ||
Ninebot IAP, Ninebot-Flasher, and a ScooterHacking Utility all support this. | Ninebot IAP, Ninebot-Flasher, and a ScooterHacking Utility all support this. | ||
If that doesn't, flashing a CFW using [https://cfw.max. | If that doesn't, flashing a CFW using [https://max.cfw.sh max.cfw.sh] with error suppression 1 or more enabled will also solve the problem. | ||
[[Category: Scooters]][[Category: Ninebot]][[Category: Max]][[Category: Error Code]] | [[Category: Scooters]][[Category: Ninebot]][[Category: Max]][[Category: Error Code]] | ||
Latest revision as of 23:07, 15 June 2022
"Master Control Board Password Error, Please replace the Control Board"
If your Ninebot Max is beeping or has a red wrench icon and flashes this code, read below.
If you clicked the wrong error code, go back to the Error Code Index.
Previous Error Code: Ninebot Max Error Code 26 - Next Error Code: Ninebot Max Error Code 28
Cause
Error 27 occurs when rental vehicles are not properly STLinked or an incomplete firmware dump is used.
It can also be caused by using an old serial change method.
This error is the same across the Ninebot SNSC 1.0, SNSC 1.1, ES1, ES2, ES3, ES4, Ninebot G30/Max, G30P, G30D, G30E, and any other Ninebot G30 series scooter.
Fix
To temporarily fix error 27, hold down the brake and throttle on boot up and release once it beeps.
Changing the serial number twice using a newer dAuth-supported serial change method.
Ninebot IAP, Ninebot-Flasher, and a ScooterHacking Utility all support this.
If that doesn't, flashing a CFW using max.cfw.sh with error suppression 1 or more enabled will also solve the problem.