Unlocking Bootloader after 2nd RMA (motherboard) not possible - Error 105
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2020 09:17 AM
Model Name: Zenfone 6 (ZS630KL-2A031EU)
Firmware Version: Android 9 (WW-16.1220.1909.194) and Android 10 (WW-17.1810.2007.165 / WW-17.1810.2007.165)
Rooted or not: not (currently)
Frequency of Occurrence: Always
APP Name & APP Version (If your issue relates to the app): UnlockTool_9.2.0.0
In addition to information above, please also provide as much details as you can, e.g., using scenario, what troubleshooting you've already done, screenshot, etc.
========================================
Bought and unlocked Bootloader last year. After the first RMA (camera sensor) unlocking wasn't possible - until Version 9.2.0.0 was released. Unlocked with that like a charm. Sadly, some days later, another RMA (motherboard) was necessary and now the unlocking process is again not working. The lovely, known possible network error (105).
Tried the solution from another post (inserting SD-Card). But it didn't helped.
chapi_73Happens via WiFi and Data. With and without SD-Card / SIM.Please tell us some basic information before asking for help:
- Model Name: Zenfone 6
- Firmware Version: WW_17.1810.2008.171
- Rooted or not: No
- Frequency of Occurrence: Always
- APP Name & APP Version (If your issue relates to the app): UnlockTool_9.2.0.0
In addition to information above, please also provide as much details as you can, e.g., using scenario, what troubleshooting you've already done, screenshot, etc.
========================================
Mother board has been changed on my phone.
UnlockTool doen't unlock bootloader .
It reports a 105 error.
What can I do ?
Can't unlock bootloader with asus UnlockTool

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2020 04:57 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2020 05:39 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2020 11:36 PM
my last information is, that the issue is still under investigation (PMs, this week). They are getting forward in finding and solving the root cause without braking something else, but for the time we some more patience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2020 03:34 AM
After the FOTA-Update to Version WW-17.1810.2009.176 the unlocking went without a flaw. So for me everything is solved now and running as I want.
