|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source | Mark Forums Read |
| LinkBack | Thread Tools | Display Modes |
02-07-2019, 13:37 | #1 (permalink) |
No Life Poster Join Date: Dec 2002 Location: Kazakhstan
Posts: 1,043
Member: 19032 Status: Offline Thanks Meter: 158 | Honor 6A DLI-AL10 Code: Model: DLI-AL10 IMEI: 866250********** Firmware ver.: MSM8937C00B127_AMSS May 18 201816:36:41 Firmware model: DLI-AL10 SN: BWN9X17805W02121 PCB SN: 8H731A3351027231 WiFi MAC: 04:4F:4C:45:26:A1 BlueTooth MAC: 04:4F:4C:45:26:A2 Vendor: all Country: cn RAM: 3GB eMMC: 32GB eMMC ID: 150100525831424D420652D5D20A5400 HUN: 0000000000000000 IMEI 1 Sim Lock status: NET: unknown NETSUB: unknown SP: unknown Code: Sending 2ed time Auth Data to Server... verification data success.... boot Version: AMSS Info: MSM8937C00B127_AMSS May 18 201816:36:41 EFS Version: DLIC00B042_ATO_EFS HL1DLIM-AL10 Sboot Version: KERNEL Version: System Version: System 5.1.0.78(0X0B) Recovery Version: CPU Info: MSM8937 Software Modle Info: DLI-AL10 Modle Info: DLI-AL10 PCB SN: 8H731A3351027231 Mobile SN: BWN9X17805W02121 MEID: A0000******** IMEI: 8662500******** IMEI2: 8662500******* carrier operator: all Country: cn Flash ID: 150100525831424d420652d5d20a5400 |
02-08-2019, 10:04 | #3 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | According to info on our side, firmware does not provide this info, which may indicate there is a problem with it. For more info we would need to take log file. Also this may be caused by not logging first before doing detection as well. Last edited by Namelocked; 02-08-2019 at 10:21. |
02-13-2019, 09:06 | #7 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,891 | Please do this: 1. Restart HCU software. 2. Login with your account on software. 3. Right click on memo area make sure "enable debug logging" has a check mark. 4. Detect your device. 5. Right click on memo area and save "debug log file". 6. Send that file to me, please. |
Bookmarks |
Thread Tools | |
Display Modes | |
| |
|